Performance SEO Cheat Sheet

Core Web Vitals -
Poor URLs

Google is grading your client's speed and user experience. Here's exactly how to secure passing scores.

Where to find it: Experience > Core Web Vitals > 'Poor URLs' (Check Mobile & Desktop)

What It Is

Google measures three critical speed and stability metrics directly from real-user field data: LCP (Largest Contentful Paint, target < 2.5s), INP (Interaction to Next Paint, target < 200ms), and CLS (Cumulative Layout Shift, target < 0.1). Pages flagged as "Poor" fail to meet the passing threshold in at least one of these departments.

Why It Matters

Core Web Vitals are a confirmed search ranking signal. Pages marked "Poor" sit at an immediate ranking disadvantage in competitive markets. Beyond rankings, clean Vitals drive direct revenue: LCP under 2.5s correlates with 15–25% higher conversions, while bad layout shifts trigger massive shopping cart and form abandonment rates.

Root Diagnostics

Core Failure Categories

Google breaks down speed bottlenecks into three core metric targets plus mobile device constraints.

LCP (Loading)

Triggered by unoptimized hero images, slow server response times, absence of a CDN, or render-blocking CSS/JS files.

INP (Responsiveness)

Caused by heavy main-thread JavaScript execution, excessive third-party scripts, bloated DOM size, or unoptimized event handlers.

CLS (Stability)

Spurred by media assets lacking width and height parameters, dynamically injected late-loading ads, or late-swapping web fonts.

Mobile Constraints

Failures specific to mobile connections due to heavy stylesheets or media payloads loading over slower CPU/data networks.

Interactive Standard Operating Procedure

The Fix Blueprint (Interactive SOP)

Check off each diagnostic step to monitor your implementation progress live!

Implementation Progress: 0% Completed (0/7)

1. Export and Isolate Failures

Go to the Search Console Core Web Vitals report and download the lists of "Poor URLs" for both Mobile and Desktop. Group URLs by failed metric (LCP, INP, or CLS).

2. Optimize LCP Hero Images

Compress your LCP hero images, convert them to WebP/AVIF, and integrate <link rel="preload" as="image" href="..."> inside the page head to tell the browser to download them immediately.

3. Implement CDN Delivery (LCP)

Serve your static assets from an optimized CDN (e.g., Cloudflare) to deliver assets from proxy servers physically closest to each visitor. This drops Time-to-First-Byte (TTFB) significantly.

4. Prune JS & Defer Scripts (INP)

Audit all third-party tracking scripts. Defer or remove scripts not essential to core page function to prevent them from blocking the browser's main thread during click interactions.

5. Optimize Thread Tasks (INP)

Use the Chrome DevTools Performance panel to find long scripts blocking interactions. Optimize slow event handlers, break up long-running tasks, and minimize heavy CSS transitions.

6. Enforce Explicit Media Dimensions (CLS)

Always append explicit width and height attributes to all HTML image elements and ad banners to reserve the correct aspect ratio layout space before they load.

7. Stabilize Web Font Swapping (CLS)

Utilize font-display: optional inside your custom @font-face CSS definitions to completely avoid abrupt layout jumps during font loading sequences.

Tools

Google Search Console
Free | Core Web Vitals report with real-user field datasets
PageSpeed Insights
Free (pagespeed.web.dev) | Lab metrics vs real-user field summaries
Chrome DevTools
Free browser package | Performance panel + lighthouse audits

Time to Fix

1-2 hours

To Run Diagnostics & Audits

Hours to Days

Easy image fixes (hours) | Heavy JS updates (days)

Pro Tip

Always focus on the FIELD data in GSC, not just lab scores in PageSpeed Insights.

A page can achieve a score of 90+ in a controlled lab test but still fail field tests due to real-user device variances. Field data is what Google actively measures and uses as a direct ranking factor!

Core Web Vitals - Poor URLs