A slow website is rarely one bug. It is a chain of delays, and each link has its own test. Work from the first byte backwards so you fix the biggest cause first, and stop when the page is fast enough for your visitors.
How to read the timeline
Open the browser developer tools, go to the Network tab and reload the page with the cache disabled. Click the first request, the page itself, and read its timing. The stages appear in this order: DNS lookup, connection, TLS handshake, waiting for the server, then download.
| Stage | High value means | Where to look |
|---|---|---|
| DNS lookup | Slow or distant nameservers | DNS provider and record setup |
| Connection and TLS | Long distance to the server, old TLS setup | Server location, HTTP/2, certificate chain |
| Waiting for server | The application is slow | Caching, database, PHP, plan limits |
| Download | Heavy page | Images, fonts, scripts |
The checklist in order
- Waiting for the server above about 600 ms. Enable a page cache, review slow database queries and check PHP version and plugins.
- Images over a few hundred KB. Resize and convert to WebP or AVIF, and lazy-load below the fold.
- Many third-party requests. Remove unused tags, chat widgets and fonts.
- No compression or cache headers. Enable Brotli or gzip and long cache lifetimes for static files.
- Layout jumps. Give images and embeds fixed dimensions.
- Slowness only at busy times. That points to CPU, memory or process limits on the plan.
Location and plan
A server far from visitors adds delay to every uncached request. A Sofia origin suits visitors in Bulgaria, the Balkans and Turkey, and a CDN covers static files elsewhere. When a trimmed site still slows down under load, the plan is the limit. What happens with the wrong hosting package lists the symptoms, and cloud servers give resources of your own, while web hosting suits lighter sites.
After the fix
Re-test on a mid-range phone over mobile data and check the field data in PageSpeed Insights a few weeks later. Website performance explains the longer-term habit, and why customers leave after three seconds covers the visitor side.
Frequently asked questions
Where should I start on a slow site?
With the server wait time in the Network tab. If it is high, fix the application before touching images.
Will a CDN fix a slow server?
Only for static files. Slow dynamic pages need caching or a stronger server.
How do I know the plan is too small?
Pages are fast at quiet hours and slow during peaks, or the panel reports resource limit errors.
