On this page
What happens on every visit
On a standard WordPress site every page is built the moment someone requests it. The server starts PHP, pulls the content from the database, loads the theme and every plugin, and only then sends the page. On a static site the page is ready and goes out at once. The gap disappears when the server is fast and a cache keeps the built page; it grows on cheap hosting without a cache, with a page builder and twenty plugins.
WordPress.org names the same four levers: hosting, the number of plugins, caching and the PHP version. A fifth has nothing to do with WordPress and comes back almost every time: images that are too heavy. The step-by-step approach is in our guide to improve website speed. Picking a new host? Read moving a website to a new host first. How we build WordPress sites that stay fast is on WordPress website development.
Measure before you buy
Faster hosting only helps when the server is the brake. First measure how long the first byte takes and how heavy the page is; often the images are the cause, and they move along with you.
How many sites pass Google's speed thresholds
Passes Google's speed thresholds, 2025Share of sites, on mobile
- Duda85%
- Wix74%
- WordPress45%
Downloading the Villa Lidia home pageOn a phone at 5 megabits a second
- Before the rebuild, 8.4 MB13 seconds
- After the rebuild, 1.4 MB2 seconds
Which metric drops because of which part of WordPress
Google measures your site's speed with three Core Web Vitals. In 2024, 40 percent of WordPress sites passed all three on mobile; in 2025 it was 45 percent. What in WordPress most often causes a fail:
| Metric | Good when | What weighs most in WordPress |
|---|---|---|
| Largest image or text on screen (LCP) | within 2.5 seconds | a slow server without cache, a hero image of several megabytes |
| Response to a tap or click (INP) | within 200 milliseconds | JavaScript from page builders, sliders and chat plugins |
| Layout shift (CLS) | at most 0.1 | late-loading fonts, images without fixed size, banners |
Check your own site in a minute with the website speed test. What the three metrics mean is in the glossary entry on Core Web Vitals.
What a slow site costs you
A visitor who waits thirteen seconds on a phone is usually gone before seeing anything. For a store it shows in revenue, as why is my online store not selling explains. Sending ad traffic to a slow page means paying for clicks that never see a page; that is why we build landing pages that appear at once on a phone. Google uses the Core Web Vitals as one of its signals, though good content and a page per question weigh more; see is SEO dead. Since version 6.8 WordPress preloads the next page when a visitor is about to click, but that too only helps when the server answers fast.
A site that leans on many plugins is usually harder to keep safe as well. If you clean up, combine it with what is in is WordPress safe. A site that turns slow without any change on your side may also be hacked: the signs are in website hacked, what to do.
Caching and switching
Which cache plugin should I use?
Ask your host first: many good hosts have a server-level cache built in. A cache plugin on top of a server cache can do more harm than good.
Is switching to another build the only fix?
No. Caching, better hosting and fewer plugins often get you most of the way. Switching pays when the site needs a rebuild anyway, or when upkeep takes too much of your time.