Page Speed SEO: 3 Core Web Vitals Metrics That Rank You
Page speed quietly decides whether your site ranks. The three Core Web Vitals metrics that matter — and how to fix the big one in a fortnight.
Page speed SEO is the most consistently neglected lever in Australian digital marketing. Every week we audit a site that is losing ground to slower competitors, not because its content is weaker, but because the technical foundations are holding it back.
This is a field where the gap between “good enough” and “actually fast” is both measurable and fixable — often within a few weeks of focused work.
Why Speed Is Still a Site Speed Ranking Factor
Google has used page speed as a site speed ranking factor since 2010 for desktop and 2018 for mobile. Since 2021, the signal has become more specific: Google now measures real-user experience through Core Web Vitals, a set of metrics reported in its Chrome User Experience Report (CrUX).
This is the important nuance. Google is not measuring your PageSpeed Insights score in isolation. It is measuring how real users — specifically Chrome users — actually experience your pages. A lab score of 90 means nothing if your real-user data tells a different story.
That distinction matters for how you diagnose and fix problems.
The 3 Core Web Vitals Metrics for Core Web Vitals 2026
There are three metrics that Google currently uses as Core Web Vitals 2026 ranking signals. Each measures something different about how a user perceives your page.
LCP — Largest Contentful Paint
LCP measures how long it takes for the largest visible element on the page to load. This is usually a hero image, a large heading block, or a featured image in a blog post.
Target: Under 2.5 seconds (real-user P75).
LCP is the metric that matters most for most Australian business websites. It is also the most consistently broken. The most common culprits: an unoptimised hero image served at full resolution, a render-blocking font load that delays the largest text element, or a slow server response time (TTFB) that delays everything downstream.
INP — Interaction to Next Paint
INP replaced FID (First Input Delay) as a Core Web Vital in March 2024. Where FID measured the delay before the browser could begin responding to a user interaction, INP measures the actual visual response time — how long until the page visually updates after a tap or click.
Target: Under 200ms (real-user P75).
INP problems are most common on JavaScript-heavy pages. If your site is loading large React bundles, running heavy analytics scripts on the main thread, or deferring layout calculations to interaction time, INP will suffer. Most static content sites pass easily. Single-page applications and interactive tools often fail.
CLS — Cumulative Layout Shift
CLS measures how much the visible content shifts unexpectedly during page load. A banner image that loads without reserved space and pushes the headline down. An ad slot that appears and moves the “Book a call” button. A font that swaps from fallback to custom and causes text reflow.
Target: Under 0.1 (real-user P75).
CLS is often the easiest Core Web Vital to fix. Reserve explicit dimensions for every image and video element. Use font-display: swap on custom fonts. Avoid injecting content above existing content unless it is in response to a user action.
LCP Optimisation: Fixing the One That Moves Rankings
LCP optimisation is where most Australian sites have the most room to improve. Here is the order in which we work through it.
Step 1: Identify what the LCP element actually is. Open Chrome DevTools, run a Lighthouse audit, and look at what element is flagged as the LCP. On most sites it is the hero image. On text-heavy pages it may be the main heading.
Step 2: Serve the image at the right size. A hero image does not need to be 3,000px wide. Serve it at the largest size it will actually render — typically 1,440px for desktop. Use WebP format. Use srcset and sizes attributes so mobile devices receive a smaller version.
Step 3: Preload the LCP image. Add a <link rel="preload" as="image"> tag in the document head for the hero image. This tells the browser to fetch it as soon as possible, before it encounters the image tag in the body.
Step 4: Reduce Time to First Byte (TTFB). If your server response is slow, everything is slow. TTFB under 800ms is the target. If you are on shared hosting and your TTFB is 1.5 seconds, your LCP cannot be fixed by image optimisation alone. Consider a CDN or better hosting.
Step 5: Eliminate render-blocking resources. Fonts loaded without font-display: swap, stylesheets loaded synchronously, and large JavaScript bundles in the <head> all delay the LCP element. Defer non-critical resources and preconnect to any third-party font hosts.
A 14-Day Fix Plan for Australian Businesses
Most websites can make meaningful LCP improvements in two weeks without a full rebuild. Here is a realistic sprint structure.
Days 1–2: Diagnosis. Run PageSpeed Insights on five key pages. Export the CrUX field data. Identify the LCP element on each page. Check your server TTFB with webpagetest.org.
Days 3–5: Images. Re-export and compress every hero image. Switch to WebP. Add explicit width and height attributes. Add preload tags to LCP images.
Days 6–8: Fonts. Audit how your fonts are loading. Add font-display: swap to custom font declarations. Consider self-hosting Google Fonts to remove the third-party DNS lookup.
Days 9–11: JavaScript. Identify scripts loading in the <head> that are not critical for initial render. Move them to defer or async. Identify any third-party scripts (analytics, chat widgets, heatmaps) adding significant weight and defer them.
Days 12–14: Verify and monitor. Re-run PageSpeed Insights. Check CrUX data if your site has sufficient traffic. Submit to Google Search Console and monitor Core Web Vitals under the Experience report.
Real-user Core Web Vitals data takes 28 days to update in Search Console after changes are deployed. Make your changes, verify with lab data, and then allow a month to see the field data improve.
Want NikoSEO to apply this thinking to your business?
Book a strategy call