Performance

Why Is My Website Loading Slow? A Practical Diagnostic Guide

A slow website usually has one of four causes: DNS latency, server bottlenecks, network routing, or front-end bloat. Use the checks below to isolate the culprit in under five minutes.

The four-layer model of website speed

Every page request passes through four distinct layers, and a delay in any one of them looks the same to your visitor: a slow page. Diagnosing properly means measuring each layer independently rather than guessing.

DNS resolution — translating your domain into an IP address. Should complete in under 100 ms.
Network path — the round-trip between visitor and server. Anything over 150 ms degrades perceived speed.
Server response (TTFB) — how long your host takes to start sending bytes. Target is under 500 ms.
Front-end render — downloading and painting HTML, CSS, JS, images. Heavy media or render-blocking scripts dominate here.

Common server and hosting bottlenecks

If your TTFB is high but everything else is normal, the issue is your origin server. Typical causes:

Shared hosting saturated by other tenants during peak hours
Database queries without indexes — N+1 patterns scale catastrophically
Missing or misconfigured caching layer (no Redis, no CDN, no HTTP cache headers)
PHP/Node workers exhausted — every request queues
Geographic distance from visitors with no edge cache

Run a server status check from multiple regions. Consistent slowness everywhere means origin work; only-some-regions slowness means missing CDN coverage.

Front-end issues that quietly add seconds

Even a perfectly tuned backend can feel slow if the browser has to do too much. Audit these first:

Unoptimized images (PNG screenshots used as hero banners, no WebP/AVIF, no responsive sizes)
Render-blocking JavaScript in the <head> — defer or async non-critical bundles
Third-party tags (chat widgets, analytics, ads) loaded synchronously on first paint
Custom fonts without font-display: swap, causing invisible text flash
Layout shift from late-loading content, which the browser counts as a poor experience

Recommended next steps

Diagnostic workflow

1
Confirm the site responds at all
Use the Server Status check above to verify reachability and measure round-trip time.
Open Server Status
2
Measure raw network latency
Run a Ping Test to your domain. Sustained latency above 150 ms or jitter above 30 ms means the network path is the issue.
Run Ping Test
3
Check DNS resolution speed
A slow or misconfigured resolver can add half a second before the first byte. Verify your A record and TTL.
Lookup DNS
4
Run a full Speed Test
Once the path is clean, measure end-user download/upload to rule out the visitor's connection.
Speed Test
5
Set up monitoring
Slowness that comes and goes needs continuous observation. Configure uptime + latency alerts so you catch it next time.
Configure monitoring

Frequently asked questions

What's a 'slow' website, technically?

Most modern users perceive a site as slow when Largest Contentful Paint exceeds 2.5 seconds or Time to First Byte exceeds 800 ms. Anything past 4 seconds drives measurable bounce.

How do I tell if it's my hosting or my code?

Run a Ping and Server Status check first. High ping or unstable server response means the bottleneck is upstream (host/network). Fast TTFB but slow page render points to front-end weight — large images, render-blocking JS, or third-party scripts.

Could DNS make my site slow?

Yes — slow or misconfigured DNS adds 100–500 ms before any request even starts. A DNS Lookup will show resolver latency and whether records are returning what you expect.

Why is my site fast for me but slow for visitors?

Browser cache, ISP route, and geographic proximity to your server all matter. Test from a different network or use a globally distributed monitoring tool to see real-user latency.

Does HTTPS slow down a site?

Modern TLS 1.3 adds only a few milliseconds. If TLS handshake time is high in your trace, the issue is usually a misconfigured certificate chain or an outdated server, not encryption itself.