Troubleshoot slow server or website connection

Slow connection problems can originate from many places-your own internet, your ISP, a routing issue between you and the server, the server being overloaded, or the website itself being unoptimized. Isolating which one is causing the issue is the first step.

Identify where the slowness is

Ask yourself:

• Is the site slow for everyone, or just you?
• Is it slow from multiple locations/devices, or only one?
• Is it slow consistently, or only at certain times?
• Is it slow on all pages, or specific ones?

If the site loads fast for others but slow for you, the issue is likely local (your internet, ISP routing, or DNS cache). If it's slow for everyone, the server or website is the issue.

Step 1: Test your internet connection

1. Run a speed test at speedtest.net
2. Compare your results against your subscribed speeds
3. Restart your router/modem and test again
4. Try a different device on the same network

If your speed test results are normal, the issue is not your internet connection.

Step 2: Run traceroute

Traceroute identifies where in the network path the delay is occurring. See How to run a traceroute.

Look for hops where latency suddenly jumps-that hop's router or the link to the next hop is the bottleneck. If latency is fine until the last 2–3 hops, the issue is on the server side.

Step 3: Check server load

Shared hosting: Log in to cPanel → Metrics → Resource Usage. Check if CPU, RAM, or Entry Processes are consistently at or near 100%.

VPS/Dedicated: SSH to the server and run top or htop to check CPU and RAM. Run uptime to see the load average-compare against your CPU core count. A load average above your core count indicates overload.

Step 4: Website performance analysis

Use Google PageSpeed Insights or GTmetrix to analyze your website's performance from an external perspective:

• Large unoptimized images are the most common cause of slow page loads
• Excessive JavaScript or CSS blocking page rendering
• No caching-every page requires full server processing
• Too many external requests (ads, analytics, social widgets)

For WordPress: see WordPress performance optimization.

Step 5: DNS and cache

Slow initial page loads (but fast subsequent loads in the same session) can indicate DNS resolution delays. Test by connecting directly via IP address instead of domain name-if the IP connection is faster, DNS lookup latency is a factor.

Clear your DNS cache and browser cache, then test again. See DNS troubleshooting guide for flush commands.

If you've gone through all steps and the issue persists, open a support ticket with your traceroute results, server IP, and a description of the slowness (when it happens, from which location).

Related: My website is loading slowly-what to check | How to run a traceroute (tracert) for network diagnostics | Server monitoring | My website is down-what to check first

Related articles