This article explains how Web60 automatically handles server scaling when your website experiences increased traffic or resource demands.
What Happens During Traffic Spikes
When your website receives more visitors than usual, Web60's system automatically detects the increased load. The scaling process begins within 30 seconds of detecting higher resource usage.
Our monitoring system checks your website's performance every 10 seconds. If your site uses more than 80% of its current resources for over 60 seconds, additional server capacity is automatically allocated.
How Resources Are Added
Web60 scales three main resources based on your website's needs:
CPU Power: Additional processing power is added when your website handles complex tasks or multiple simultaneous visitors.
Memory (RAM): Extra memory is allocated when your WordPress site needs to load larger pages or process more data.
Storage Speed: Faster disk access is provided during periods when your database receives many queries.
These resources are added gradually. The system starts with a 25% increase, then monitors performance. If needed, resources continue scaling up to 400% of your base allocation.
What You'll Notice During Scaling
Your website will maintain its normal loading speed even during busy periods. You won't see any downtime or service interruptions during the scaling process.
The Web60 portal shows a "High Traffic Detected" notification when scaling is active. This appears in the performance section of your dashboard.
If scaling occurs frequently, you'll receive an email summary within 24 hours explaining the traffic patterns and any recommendations.
When Resources Scale Back Down
Once traffic returns to normal levels, resources automatically scale back down. This process is more gradual than scaling up - it happens over 15-30 minutes to avoid any performance drops.
The system waits for resource usage to stay below 50% for at least 10 minutes before beginning the scale-down process.
For websites with predictable traffic patterns (like lunch-time rushes for restaurants), Web60 learns these patterns and pre-scales resources to prevent any slowdowns.
Monitoring Scaling Activity
You can view scaling activity in your Web60 portal under "Performance Reports". This section shows when scaling occurred, how much additional resources were used, and the duration.
The system also tracks which pages or features triggered the scaling. This information helps identify if specific plugins or content types are causing higher resource usage.
If you notice frequent scaling due to plugin conflicts or performance issues, these reports help pinpoint the cause.
If you're experiencing issues that seem related to server performance or have questions about your scaling reports, contact Web60 support through your portal dashboard.
FAQ
Q: Does server scaling cost extra money?
A: No, automatic scaling is included in your Web60 service. You're not charged extra when resources temporarily increase during traffic spikes.
Q: How long does it take for scaling to start working?
A: Scaling begins within 30 seconds of detecting high resource usage and is fully active within 2 minutes.
Q: What's the maximum my site can scale to?
A: Web60 can scale your resources up to 400% of your base allocation during traffic spikes. This handles most traffic increases without issues.
Q: Will I know when my site is being scaled?
A: Yes, you'll see a "High Traffic Detected" notification in your Web60 portal, and you'll receive an email summary if scaling happens frequently.
Q: Can I turn off automatic scaling?
A: Automatic scaling cannot be disabled as it's essential for maintaining your website's performance during traffic increases.
Q: What happens if my site needs more resources than the maximum scaling allows?
A: In rare cases where scaling reaches maximum capacity, Web60 support is automatically notified and will contact you to discuss options.
Q: Does scaling work for all types of websites?
A: Yes, scaling works for all WordPress websites on Web60, whether they're blogs, business sites, or online shops.
Last updated: 1 March 2026