Cross-signal

Striking Distance × Slow Pages

The shortest list of fixes that help twice: ranking and speed. Striking-distance queries (positions 10–20) whose landing page also scores poor on mobile PageSpeed — one fix helps both ranking and visitors.

Why it matters

Google's Page Experience signal favours faster pages on close ranking calls. A query sitting at position 12 with a slow landing page is being held back by two compounding problems. Fix the speed and you usually nudge the rank — and even if you don't, you've already won UX. Two birds.

How it's built

  1. Pull every query with an average position between 10 and 20 and enough impressions for a site your size in the selected window (the same rule as the Striking Distance report).
  2. Join each query to its top landing URL using the 90-day query × page snapshot.
  3. Join that URL to its latest mobile PSI run.
  4. Keep only rows where the page scores below 50 on mobile (or where we don't yet have a PSI run for that URL).

Estimated upside

For each row, "Estimated upside" shows the extra clicks you'd gain if that query reached position 8, calculated as $\max(0, \text{impressions} \times 0.06 - \text{current clicks})$. The 6% CTR is a conservative position-8 proxy used when the site's full CTR curve isn't loaded into this view.

How to action it

  • Sort by Estimated Upside descending. The top rows are your sprint backlog.
  • Click the URL — it deep-links to PageSpeed Insights with the mobile profile preselected.
  • Cross-reference the same URL in PSI Opportunities to see exactly which audits are costing the most milliseconds.
  • "Missing PSI" rows mean we haven't tested that URL yet — schedule a PSI run before triaging.

Data requirements

  • Search Console data for your searches and the pages that rank for them.
  • PSI runs (mobile) for at least some of the landing URLs.