Does page speed affect Google rankings?

Yes, but not the way headlines suggest. Google says Core Web Vitals are used by its ranking systems, and also says there is no single signal that decides everything. Relevance still comes first: Google says Search will show the most relevant content even when the page experience is poor.

So a fast page will not outrank a better answer. But when many pages answer the question equally well, a good page experience can be what tips it, and a slow page loses visitors long before any ranking matters.

What Google says

From Google’s page experience documentation:

• Core Web Vitals are used by Google’s ranking systems.
• There is no single signal. The ranking systems look at many signals that line up with overall page experience.
• Other page experience factors do not directly help you rank higher, but improving them helps users, which is what ranking systems try to reward.
• Page experience matters most where there is lots of helpful content to choose from.

The three numbers

Core Web Vitals are three measures of real visits. The targets below come from web.dev, and a page passes when it meets all three for at least 75% of visits.

Measure	What it tells you	Good
Largest Contentful Paint (LCP)	How fast the main content appears	2.5 seconds or less
Interaction to Next Paint (INP)	How quickly the page responds to a tap or click	200 milliseconds or less
Cumulative Layout Shift (CLS)	How much the layout jumps while loading	0.1 or less

How to measure

1. Search Console, Core Web Vitals report. It uses data from real visitors and groups pages with the same problem. Start here.
2. PageSpeed Insights. Paste a URL to see field data (real visits) and lab data (a test run) side by side.
3. Chrome DevTools, Lighthouse. Useful for finding what to fix on a page, but a lab score is not the same as real visitor data.

Test on a mid-range phone and a normal mobile connection. Most of your visitors are not on your office Wi-Fi.

Fixes that help most on WordPress sites

Images

Large images are the most common cause of a slow LCP. Resize them to the size shown, use modern formats such as WebP, and lazy-load images below the first screen. Do not lazy-load the main image at the top, since that delays LCP.

Scripts and plugins

Every plugin and third-party script (chat widgets, trackers, social feeds) adds weight. Remove what you do not use, and load the rest after the page is usable. Most INP problems come from too much JavaScript running at once.

Layout shifts

Give images, videos and ad slots a fixed width and height so the page does not jump when they load. Load fonts in a way that does not reflow the text.

Hosting and caching

A slow server slows everything else. Use page caching, a CDN, and a current PHP version. Check these before spending days on smaller fixes.

Page builders

Builders such as Elementor are fine when the template is lean. Keep sections simple, avoid heavy animation above the fold, and test the real page, not the demo.

A sensible order

1. Check the Core Web Vitals report and pick the group of pages with the biggest problem.
2. Fix the main image and the heaviest scripts on that template.
3. Re-test after a few days. Field data takes time to update, so do not expect the report to change overnight.
4. Move to the next template.

What not to do

• Chasing a perfect 100 in Lighthouse. Passing the three targets for real visitors is the goal.
• Removing content that helps people to save a few milliseconds.
• Treating speed as a replacement for a useful page.

Our Website Design and WordPress Development work builds speed into the template from the start. If you have an existing site that feels slow, send us the URL and we will tell you where we would begin.