Guide
Why Is My Website Slow?
5 min read

Usually oversized images, too many plugins, cheap hosting, heavy page builders or third-party scripts. Test yours free with Google's PageSpeed Insights, then fix the images and hosting first.
Already have a site? Run our free website audit for a score on speed, Google and design.
Where these numbers come from
The speed thresholds below come from Google's own web.dev documentation, and the testing details from Google's PageSpeed Insights documentation, both read on 21 October 2026. The figures on page weight and third-party code come from the HTTP Archive's Web Almanac 2024, which measures millions of real websites. The fix order at the end is our own, from the sites we've rebuilt and sped up.
Test your site free in two minutes
- 1
Open PageSpeed Insights
Go to pagespeed.web.dev, Google's free speed test, paste your homepage address and press Analyse. No sign-up needed.
- 2
Read the top box first
If your site gets enough visitors, the top section shows real data from Chrome users over the previous 28 days. That's what Google actually sees. The score underneath is a lab test on a simulated phone.
- 3
Check the mobile tab
Mobile results are almost always worse than desktop. A score of 90 to 100 is good, 50 to 89 needs work, and under 50 is poor.
- 4
Scroll to the diagnostics
Google lists what's slowing the page, biggest saving first. Note the top three; they're usually images, scripts or server response time.
Google's three speed numbers
| Core Web Vital | What it measures | Good | Needs work | Poor |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main image or heading shows | 2.5 seconds or less | 2.5–4 seconds | Over 4 seconds |
| Interaction to Next Paint (INP) | How fast the page responds to a tap or click | 200 ms or less | 200–500 ms | Over 500 ms |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less | 0.1–0.25 | Over 0.25 |
The five usual causes
In rough order of how often they're to blame on small business sites:
- Oversized images. A photo straight off a phone can be several megabytes, shown in a box a few hundred pixels wide. The Web Almanac found the median mobile homepage loads 900 KB of images, out of a median page weight of 2,311 KB.
- Too many plugins. Each WordPress plugin can add its own code and stylesheets to every page, whether that page uses it or not. Twenty plugins is twenty sets of files.
- Cheap or overloaded hosting. On a crowded shared server, the first byte of your page can take a second or more to arrive, before anything else starts loading. Google's own guidance says slow server response makes a 2.5-second LCP hard to reach.
- Page builders. Drag-and-drop builders and multipurpose themes load code for every layout and effect they offer. You pay the loading cost for features you never switched on.
- Third-party scripts. Chat widgets, booking embeds, review carousels, tracking pixels and video players each load code from someone else's server. The Web Almanac found 92% of pages use at least one third party.
What to fix first
| Fix | Effort | Usually helps |
|---|---|---|
| Resize and compress images, use WebP or AVIF | Low | LCP, page weight |
| Make sure the main hero image is not lazy-loaded | Low | LCP |
| Remove plugins and scripts you no longer use | Low to medium | All three |
| Give images and embeds a fixed size so nothing jumps | Low to medium | CLS |
| Move to better hosting or add a CDN | Medium | LCP, server response |
| Load chat widgets and trackers after the page | Medium | INP, LCP |
| Rebuild without the page builder | High | All three |
Why speed matters beyond the score
Google says Core Web Vitals are used by its ranking systems, but a fast page mostly matters because people leave slow ones. A visitor on mobile data at a job site won't wait four seconds for your phone number. Treat the PageSpeed score as a diagnostic, not a goal. A site that loads its main content in under 2.5 seconds on a phone and doesn't jump around is fast enough for almost any small business.
When it's time to rebuild instead
If you've compressed the images, removed the spare plugins and moved hosts, and mobile is still in the red, the page builder or theme is usually what's left. That's when a rebuild costs less than continuing to patch. Our guide on redesigning versus fixing walks through how to decide. Every site we build is custom-coded with no page builder and no plugin layer, so it loads only what each page uses.
Sources
- PageSpeed Insightshttps://pagespeed.web.dev/
Google's free speed test.
- Google: About PageSpeed Insightshttps://developers.google.com/speed/docs/insights/v5/about
Field data from the previous 28 days, lab scores of 90+ good, 50–89 needs improvement.
- web.dev: Web Vitalshttps://web.dev/articles/vitals
LCP 2.5 s, INP 200 ms, CLS 0.1, measured at the 75th percentile.
- web.dev: Defining the Core Web Vitals thresholdshttps://web.dev/articles/defining-core-web-vitals-thresholds
The needs-improvement and poor bands.
- web.dev: Optimise LCPhttps://web.dev/articles/optimize-lcp
Slow server response and never lazy-loading the LCP image.
- HTTP Archive Web Almanac 2024: Page Weighthttps://almanac.httparchive.org/en/2024/page-weight
Median mobile page 2,311 KB, mobile homepage images 900 KB.
- Google Search Central: Page experiencehttps://developers.google.com/search/docs/appearance/page-experience
Core Web Vitals are used by Google's ranking systems.
- HTTP Archive Web Almanac 2024: Third Partieshttps://almanac.httparchive.org/en/2024/third-parties
92% of pages use at least one third party.
Where to next
- Test your site's speed with the free audit
Times your homepage on a phone over 4G and shows how much smaller your images could be.
- How we build for speed
What goes into a site that loads fast on a phone.
- Should you redesign or fix what you have?
How to decide when the fixes stop working.
Get a plain-English speed check
Send us your site. We'll run it through the same tests, tell you the three things slowing it down most, and whether they're worth fixing or the site is worth rebuilding.
Common Questions
Some of the sites we've built
All projects


