You click your own website and watch it think. Every extra second is a visitor deciding whether to wait. Most slow WordPress sites are slow for one of nine reasons, and you can find yours in about a minute.
Short version
A slow site is usually heavy images, slow hosting, no caching, too many plugins, scripts that block the first view, web fonts, third-party widgets, auto-playing video or redirect hops. Run the free Website Health Check to see which ones apply, then fix them in order of impact. Google’s “good” targets are LCP 2.5 seconds or less, INP 200 ms or less and CLS 0.1 or less.
How to tell what is slowing your site down
Guessing wastes money. Test the page first. Google’s PageSpeed Insights runs Lighthouse and lists the specific files and scripts costing you time. Test the phone result, not only desktop, because phones are slower and most visitors use them. If you want the short version in plain English, our free speed test shows your scores and the top three problems.
One thing to know before you start: Lighthouse is a lab test. Scores move a few points between runs. Look for the same problems showing up every time, not a single number.
The 9 usual causes of a slow website
1. Oversized images. A 4 MB photo shown in a 400-pixel box is the most common problem we see on small-business sites. Resize images to the size they are shown, save them as WebP or AVIF, and lazy-load the ones below the first screen.
2. Slow hosting. If the server takes a long time to start sending the page, nothing else can fix that. PageSpeed Insights reports it as a slow server response (the “root document”). Cheap shared hosting with hundreds of sites on one machine is the usual cause.
3. No page caching. WordPress builds each page from the database on every visit unless you cache it. A caching plugin or server cache serves a ready-made copy instead.
4. Too many plugins and heavy themes. Each plugin can add its own scripts and styles to every page, even pages that do not use them. Remove what you do not need and check what loads where.
5. Files that block the first view. Large CSS and JavaScript files that must load before anything is drawn delay the main content. Lighthouse calls these render-blocking resources.
6. Web fonts. Several font families and weights mean several extra downloads. Use fewer, host them yourself, and let text show right away while the font loads.
7. Third-party scripts. Chat widgets, trackers, ad tags and review badges each load code from another company. Keep the ones that earn their place and load the rest after the page is usable.
8. Auto-playing video and embeds. A background video or an embedded map at the top of the page can weigh more than the rest of the page together. Use a still image and load the video when someone taps it.
9. Redirect hops. http to https to www to the final page is three requests before anything loads. Link straight to the final address and keep redirects to one step.
What to fix first
- Images and caching first. They are quick and the gains are large.
- Then scripts and plugins. Remove, delay or replace what is not needed.
- Then hosting. If the server is slow after everything else is tidy, move.
- Re-test on the phone after each change, so you know what worked.
Be careful with the plugins that promise one-click speed. Aggressive “combine and defer everything” settings can break menus, forms and sliders. Change one setting at a time, and test your contact form after each change.
What Core Web Vitals say about “slow”
Google measures three things: Largest Contentful Paint (how fast the main content appears), Interaction to Next Paint (how fast the page reacts when someone taps) and Cumulative Layout Shift (whether things jump around). “Good” means LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured for at least 75% of real visits. Lighthouse cannot measure INP in a lab, so it reports Total Blocking Time as a stand-in. Read more in our guide to a good PageSpeed score.
Will a faster site get me more customers?
A fast site removes a reason to leave. It does not by itself bring customers: you still need to be found and to say something worth reading. Speed is one of several signals Google uses, so treat it as the base layer and then work on being found on Google.
Frequently asked questions
Why is my WordPress site slow only on mobile?
Phones have slower processors and often slower networks, so heavy scripts and large images hurt more. Lighthouse also simulates a mid-range phone on a throttled connection for the mobile score, which is stricter than desktop.
Does a slow website hurt SEO?
Core Web Vitals are one of the signals Google uses, but relevance and content matter more. The bigger cost is people leaving before the page appears.
Can you fix my website speed?
Yes. Our website care plans are $99, $199 and $399 a month and cover updates, backups, security checks and fixes; bigger speed work is quoted upfront. See web maintenance.
Next step
Run the free test on your own address: Website Health Check. Fast but not found? See what Google, Bing and AI can read on your site with the AI & Search Visibility check.
Sources: Google: Core Web Vitals (web.dev), Google: PageSpeed Insights.
Related service
Want help with this? See our Web Design page for plans and pricing, or get a free quote.









