Content revised 20 October 2026.
A slow website can have several causes. Check where the time is spent before replacing the hosting plan, adding a plugin or removing content that visitors need.
Separate server delay from page delivery
A long wait before the first response can involve backend work, hosting resources, network conditions or configuration. A quick initial response followed by a slow visual load points to a different investigation. Use the request timeline to narrow the problem instead of calling every delay a server issue.
Inspect images and scripts
Look for images delivered much larger than their display size and scripts that load or execute without a clear purpose. Not every line of CSS creates a new network request; the actual files and their behaviour matter. Review duplicated assets and third-party widgets in context.
Compare situations
- New visit versus a repeat visit with cached files.
- Mobile connection versus a fast desktop connection.
- A plain article versus a page with forms or heavy media.
- Normal traffic versus a known period of high demand.
Test one explanation at a time
If a widget appears responsible, disable it in a test copy and measure the difference. If the delay is backend work, review logs and queries with the host or developer. Do not change several unrelated settings at once and assume the largest-looking change caused the improvement.
Preserve the useful journey
Keep important product details, video and working navigation available while optimising delivery. Recheck the actual interactions after changes to caching or scripts. A diagnostic report should identify the slow step and proposed repair, not just attach a score and promise rankings.
Official guidance: Google’s page experience measurement context.