Understanding your plan's resource allocations and what happens when you approach limits.
| Resource |
Starter |
Professional |
Business |
| Disk Space |
10 GB |
25 GB |
50 GB |
| Bandwidth |
100 GB/mo |
500 GB/mo |
2 TB/mo |
| Memory |
512 MB |
1 GB |
2 GB |
| CPU |
0.5 cores |
1 core |
2 cores |
| Staging Environments |
1 |
2 |
3 |
Go to Dashboard → Resource Usage to see:
- Current usage for each resource
- Usage graphs over time
- Percentage of allocation used
- WordPress/Magento files
- Uploaded media (images, videos, documents)
- Theme and plugin files
- Database size
- Logs and temporary files
| Level |
Threshold |
Effect |
| Notice |
70% |
Dashboard notification |
| Warning |
80% |
Email alert |
| Critical |
90% |
Email + dashboard alert |
| Limit |
100% |
Uploads blocked |
- File uploads are rejected
- Database writes may fail
- Your store remains accessible
- Reduce usage or upgrade plan to restore functionality
- Remove unused plugins/themes - Delete, don't just deactivate
- Optimize images - Use compression plugins like Smush or ShortPixel
- Clean up revisions - WordPress stores post revisions; limit or delete old ones
- Delete old logs - Many plugins create logs that grow over time
- Use external media - Consider CDN or cloud storage for large media libraries
¶ Bandwidth
¶ What Counts as Bandwidth
- Page loads and assets (HTML, CSS, JS)
- Image and media downloads
- API requests
- File downloads
- Admin panel usage
- Staging environments
- Backups
| Level |
Threshold |
Effect |
| Notice |
70% |
Dashboard notification |
| Warning |
80% |
Email alert |
| Critical |
90% |
Email + auto-upgrade offer |
| Limit |
100% |
Plan-dependent (throttle or suspend) |
Depending on your plan:
- Starter: Store may be suspended until next billing cycle
- Professional/Business: Overage charges may apply
¶ Reducing Bandwidth
- Enable caching - Use built-in caching or WP Super Cache
- Compress images - Smaller images = less bandwidth
- Use a CDN - Offload static assets to CloudFlare or similar
- Optimize pages - Combine CSS/JS, enable GZIP
- Lazy load images - Don't load below-fold images immediately
- PHP processes handling requests
- Database queries
- Cache operations
- Plugin operations
- Slow page loads
- Random 500 errors
- "Memory exhausted" errors
- Container restarts
When your container exceeds its memory limit:
- Container is automatically restarted
- Brief downtime (10-30 seconds)
- Logged for monitoring
Repeated restarts trigger an alert for our team to investigate.
- Disable unused plugins - Each plugin consumes memory
- Use efficient themes - Lightweight themes use less memory
- Optimize queries - Use Query Monitor plugin to find slow queries
- Enable object caching - Uses Redis (included) to reduce DB load
- Increase PHP memory - Contact support to adjust limits within your plan
If your container exceeds CPU allocation:
- Processes are slowed down (throttled)
- Your store remains accessible but slower
- No restarts or downtime
- Image processing
- Large imports/exports
- Complex database queries
- Malware scanning plugins
- Cron jobs
- Optimize images before upload - Don't rely on on-the-fly resizing
- Limit cron jobs - Disable heartbeat API or reduce frequency
- Use fewer dynamic plugins - Static content uses less CPU
- Schedule heavy operations - Run imports during low-traffic hours
If you consistently hit limits:
- Go to Account Settings → Billing
- Click Change Plan
- Select a higher tier
- Confirm the change
Changes take effect immediately:
- Prorated billing for the current period
- New limits apply instantly
- No downtime or data migration required
Yes, Dashboard → Resource Usage shows graphs for the past 30 days.
No, backups are stored separately and don't count against your quota.
We don't immediately suspend stores for short spikes. Extended overages may result in throttling or suspension depending on your plan.
Currently, resources are tied to plans. Contact support if you need a custom configuration.
Usage data is updated every 15 minutes. For real-time data, use the refresh button on the Resource Usage page.