A slow website usually has one of two problems: the server is slow to start answering, or the page it sends is too heavy. This checklist tells you which one you have and where the fix is.
This page is the short checklist. The complete diagnosis, with worked examples and developer commands, is in My website is slow.
Test the slow page in PageSpeed Insights or WebPageTest and look at the time to first byte (TTFB). If TTFB is over about a second, the delay is on the server side: PHP version, plugins, database queries, slow outside services or your account's resource limits. If TTFB is quick but the page still loads slowly, the page itself is too heavy: images, scripts or missing caching. Fix the cause first and upgrade your plan only if the limits are still being hit.
1. Measure before you change anything
Run the slow page through PageSpeed Insights (pagespeed.web.dev) or WebPageTest (webpagetest.org), or open your browser's DevTools (F12, Network tab). Test the page that is actually slow, run each test two or three times, and note the numbers so you can compare after each fix.
2. Slow server or heavy page?
| What you see | Likely cause | Start with |
|---|---|---|
| Slow TTFB on every page | PHP version, plugins, database, resource limits | Sections 3 and 4 |
| Slow TTFB on some pages only | One slow query, plugin or outside service | Section 4 |
| Fast TTFB, slow full load | Large images, many scripts, no caching | Section 5 |
| Slow only for some visitors | Their network or distance from the server | A CDN such as Cloudflare |
3. Check the server side
- Resource limits. Each shared hosting account has its own share of CPU, memory and processes. In cPanel, open Metrics › Resource Usage and look at the faults. Hitting the entry-process limit (too many requests running at once) shows visitors a 508 "Resource Limit Is Reached" error; memory and process faults show as 500 or 503. See Check hosting resource usage.
- PHP version. Newer PHP 8 versions are faster and still get security fixes. On cPanel, new accounts default to PHP 8.3 and you can choose up to 8.5 in MultiPHP Manager. Take a backup and test your site after switching.
- OPcache. It keeps compiled PHP in memory and is enabled on our cPanel servers. See the PHP OPcache guide.
4. Find slow plugins, queries and outside calls
- Plugins. Deactivate suspects one at a time on a quiet hour and re-test TTFB after each one. The free Query Monitor plugin shows which plugin runs the slowest database queries.
- Database. Clean up old revisions and expired transients, with a backup first. See MySQL performance optimisation.
- Outside services. A payment, SMS or shipping API called without a timeout keeps PHP processes waiting, and the site looks down while the server is idle. Set a timeout of a few seconds on every outbound call.
On our cPanel servers most sites stop a request after about 60 seconds, and the front-end proxy ends any request at 90 seconds with a 504 error. Raising max_execution_time does not change that. Move long imports and exports to a scheduled job instead.
5. Make the page lighter
6. When to upgrade
Upgrade when Resource Usage still shows regular faults after you have fixed plugins, queries and outside calls, or when your traffic has genuinely grown. Use Change plan on your hosting service in the client area; see Can I upgrade my web hosting package at any time?. A site that needs its own CPU and memory, or server software that shared hosting doesn't allow, belongs on a VPS.
- 50 GB NVMe SSD Storage
- 100 GB Monthly Bandwidth
- 5 Websites
- 50 Email Accounts
Prices on the cards exclude 18% GST.
Frequently asked questions
How do I know if my hosting or my website is making it slow?
Look at the time to first byte (TTFB) in PageSpeed Insights or WebPageTest. A TTFB above about one second points to the server side, such as PHP, plugins, the database or resource limits. A fast TTFB with a slow full load points to heavy images, scripts or missing caching.
Which caching plugin should I use on Domain India shared hosting?
Use WP Super Cache or W3 Total Cache. Domain India shared hosting runs the Apache web server, so LiteSpeed Cache is not suitable. Keep only one page-caching plugin active at a time.
What does "Resource Limit Is Reached" mean?
It is a 508 error shown when your account has too many PHP processes running at once. It is often caused by slow plugins or outside services without timeouts, so find and fix those before upgrading.
Still slow after these checks? Read the full guide, My website is slow, then open a support ticket with the page address, your PageSpeed results and what you have already tried.
Send us the slow page, your test results and the fixes you have tried, and we will check your account's usage with you.
Open a ticket