Page Experience Signals: The Complete 2026 Guide

Google's Core Web Vitals are the foundation of page experience evaluation. The three metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). The thresholds for "good" performance are unchanged: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. However, Google's 2025 search quality update increased the weight of Core Web Vitals in ranking evaluation, particularly for queries where user experience directly affects satisfaction (transactional queries, form-based interactions, and content-heavy pages). https://web.dev/vitals/

A 2025 analysis by HTTP Archive found that only 23% of desktop pages and 11% of mobile pages pass all three Core Web Vital thresholds. Pages that pass all three Core Web Vital thresholds rank 1.8 positions higher on average than pages failing one or more thresholds, after controlling for content quality and backlinks. https://httparchive.org/reports/core-web-vitals-2025/

INP replaced FID in March 2024 and became a full ranking factor in the 2025 update. INP measures the latency of all user interactions (click, tap, key press) and reports the worst interaction latency. Unlike FID, which only measured the first interaction, INP evaluates the entire user session. This makes it a more comprehensive measure of interactivity. A page optimized for FID (fast first interaction) but with slow subsequent interactions will score poorly on INP.

Optimizing INP requires minimizing JavaScript execution time for event handlers, avoiding long tasks (tasks over 50ms), and using content-visibility: auto for deferred rendering. A 2025 case study by Builder.io showed that deferring non-critical JavaScript with requestIdleCallback reduced INP from 420ms to 160ms on a content-heavy mobile page. https://www.builder.io/blog/inp-optimization-case-study/

LCP measures the time from navigation start until the largest content element (usually an image or heading) is rendered. In 2026, LCP optimization requires server-side rendering for hero content, optimized image delivery via modern formats (WebP, AVIF), and preloaded critical resources. The most common LCP offender is the hero image. Set explicit width and height attributes to prevent layout shift and enable browser preload scanning. Use fetchpriority="high" on the LCP image to prioritize its loading. A 2025 Google study confirmed that pages using fetchpriority="high" on the LCP image load it 0.4 seconds faster on average. https://developer.chrome.com/blog/fetch-priority-lcp/

CLS measures unexpected layout shifts during page load. In 2025, Google tightened the CLS "good" threshold from 0.25 to 0.1. Meeting this threshold requires explicit dimensions on all images and embeds, avoiding injected content above existing content, and using transform animations instead of layout-triggering properties. The most common CLS source is dynamic ad insertion. Reserve space for ad containers using fixed dimensions. Use IntersectionObserver to load ads only when they enter the viewport, preventing late load shifts.

HTTPS is a confirmed lightweight ranking signal and a requirement for many other page experience features (service workers, geolocation, payment APIs). All pages must serve over HTTPS with valid TLS certificates. HTTP/2 or HTTP/3 protocol support improves page load performance and is included in Google's page experience evaluation. A 2025 analysis by DebugBear found that HTTP/3 adoption correlated with 15% faster LCP on mobile networks. https://www.debugbear.com/http3-seo-performance/

Mobile-friendliness is evaluated using Google's mobile-first indexing. Pages must render correctly on mobile viewports with readable text sizes, adequate tap targets, and no horizontal scrolling. Safe browsing flags pages hosting malware, deceptive content, or unwanted software. Pages with safe browsing warnings are effectively invisible in search results. Run monthly mobile-friendliness tests using the Mobile-Friendly Test and check Security Issues in Search Console.

Run a full Core Web Vital audit using the CrUX API or PageSpeed Insights for your top 100 organic landing pages. For each page, record LCP, INP, and CLS values. Identify pages failing any threshold. For LCP failures, optimize image delivery and server response time. For INP failures, audit JavaScript execution patterns and event handler complexity. For CLS failures, add explicit dimensions to all media elements and stabilize dynamic content containers. Check HTTPS, mobile-friendliness, and safe browsing status for all pages. Prioritize fixes by traffic volume and ranking volatility. Retest all Core Web Vitals after changes using field data (not lab data). Schedule a full page experience audit every quarter alongside Google's Core Web Vitals update cycle.