When a WordPress site feels slow, random optimisation usually creates more confusion. Use this 20-minute diagnosis to identify whether the main delay comes from the server, page assets, plugins or third-party scripts.
Minute 0-3: define the symptom
Write down what is slow:
- The whole public site or one page?
- The first visit or every visit?
- The WordPress dashboard or only the front end?
- Desktop, mobile or both?
- All locations or a particular region?
A precise symptom prevents you from solving the wrong problem.
Minute 3-6: test three representative URLs
Test the homepage, a normal content page and the slowest important page. If only one page is poor, its layout, media or scripts are the likely cause. If everything is poor, check hosting, caching and global assets.
Minute 6-9: inspect the initial server response
If the browser waits a long time before receiving HTML, investigate page caching, database queries, PHP work and hosting resources. If HTML arrives quickly but the screen remains blank, front-end assets are more likely responsible.
Minute 9-12: find the largest visible element
The largest element is often a hero image, banner or large heading. If it is an image, check dimensions, compression, format and whether it is being lazy-loaded incorrectly. If it is text, inspect font loading and render-blocking CSS.
Minute 12-15: identify third-party weight
Chat, video, analytics, advertising and social widgets can create long tasks and network requests. Temporarily remove or delay non-essential scripts in a safe test environment and compare the result.
Minute 15-18: compare cached and uncached behaviour
Repeat the test. A large improvement on the second visit suggests caching is helping but the uncached route remains expensive. No improvement may mean caching is missing, bypassed or ineffective.
Minute 18-20: choose the next action
- Slow server response everywhere: verify caching and evaluate the hosting foundation.
- One page is slow: simplify its layout, images and embeds.
- Dashboard is slow: investigate plugins, database work and background tasks.
- Mobile is much worse: reduce scripts, media and main-thread work.
- Only distant visitors are slow: review CDN and server location.
What not to do
Do not install several optimisation plugins at once, delete database tables without a backup or assume a perfect laboratory score guarantees good business results. Improve the user journey and protect site stability.
When hosting is probably the bottleneck
Hosting deserves attention when server response remains slow across simple pages, caching is correctly configured, resource limits are regularly reached or support cannot explain repeated availability problems.
Use our complete WordPress speed guide for the repair sequence, or see the Fasterr hosting recommendation.
Prefer an integrated WordPress setup?
SiteGround bundles hosting with WordPress caching, CDN and maintenance tooling. Check the current plan details before deciding.
Affiliate disclosure: Fasterr may earn a commission, at no extra cost to you.