Guide · 12-min read
Fast sites convert more customers and rank higher in search. Slow sites don't. Here is exactly how to diagnose and fix the problems hurting your business.
Run a free audit3 sec
Average user patience limit
7%
Conversion drop per 1s delay
40%
Abandon slow mobile sites
1 to 2 wks
Typical improvement timeline
These six problems account for nearly all slow websites. Fix these and your site runs fast.
Full-size photos (5 MB+) are the most common culprit. Oversized images slow every page they appear on. Proper compression cuts image size by 70% without visible quality loss.
Analytics, chat widgets, tracking pixels, and ad code all execute on load. Each script adds 200 to 500 ms. Ten scripts means 2 to 5 extra seconds per page.
Every visit re-downloads the same CSS, JavaScript, and images. Caching tells browsers to reuse files from their local copy. One-time fix with massive impact.
Shared hosting splits server resources across hundreds of sites. When another site gets traffic spikes, your site slows down. Dedicated or managed hosting eliminates this.
Some CSS and JavaScript must load before the page displays. Large CSS or JavaScript files block the render pipeline and delay time to first content by 1 to 3 seconds.
Pages over 2 MB load slowly on mobile networks. Most problems combine into one huge page. Address images, scripts, and video separately.
Speed matters everywhere
Visitors abandon slow sites. Google knows this. Search engines penalise slow pages. You lose customers to faster competitors, and you also rank lower. Page speed is one of the few ranking factors Google openly rewards. Fix speed and you win twice: more visitors stay, and more visitors find you.
Use an online compressor (TinyPNG, Squoosh) or a plugin (ShortPixel, Smush). Resize images to the exact width they display at. JPEG for photos, PNG for graphics with text. Target: under 100 KB per image. Expected improvement: 0.5 to 2 seconds.
List every script running on your site (Google Tag Manager shows them). Remove analytics tools you do not use. Delay chat widgets until the page loads. Disable auto-play video scripts. Test each removal to confirm the feature still works. Expected improvement: 0.3 to 1.5 seconds.
Most hosting providers and content delivery networks (CDNs) offer one-click caching. Cloudflare, Akamai, or your host's built-in caching can be enabled in minutes. This tells repeat visitors' browsers to reuse files from cache instead of downloading again. Expected improvement: 1 to 3 seconds on repeat visits.
If your current host charges under £2 per month, you are likely on shared hosting. Upgrade to managed WordPress hosting (SiteGround, Kinsta) or a VPS (Linode, DigitalOcean). Test speed on your current host first. If hosting is the bottleneck, you will see an immediate improvement. Expected improvement: 0.5 to 2 seconds.
CSS and JavaScript needed for the initial page view should load first. Everything else can load after the page displays. Use async or defer attributes in your HTML (or ask your developer). This unblocks rendering and speeds up time-to-interactive. Expected improvement: 0.5 to 1 second.
Target total page size under 2 MB (including images, CSS, JavaScript). A content delivery network (CDN) stores copies of your site on servers around the world so visitors download from a location near them instead of your origin server. Expected improvement: 0.3 to 1 second.
Run your website through a free tool. Enter your URL and wait for the report. The report shows load time, time to first content, and the number of elements slowing you down. Run it on your homepage and your most important landing page.
Under 2 seconds is good. Under 1 second is excellent. Mobile connections are slower than desktop, so target under 3 seconds on 4G. Most of your visitors are probably on mobile, so optimize for that.
Start with images (biggest impact, easiest fix). Then audit scripts. These two alone will improve most sites by 1 to 3 seconds. Do caching next. The rest depend on your site.
Image compression and script removal take 1 to 3 hours to implement. You will see the improvement within hours in your measurement tool. Caching takes 15 minutes to enable and hours to fully propagate. Hosting upgrades take a day or two. Defer CSS/JavaScript depends on your site's setup, usually 1 to 2 days for a developer.
Yes. Google uses page speed as a ranking factor. Faster sites see ranking improvements over weeks to months. The bigger win is conversion: visitors are much more likely to stay and buy from a fast site than a slow one.
Image compression, script removal, and caching enablement are doable for non-technical owners. Deferring CSS/JavaScript usually requires a developer. Most hosting providers offer one-click optimizations, so try those first.
Run a free audit on your site to see exactly where your speed problems are. We show you the specific fixes and the order to tackle them.