PageSpeed

Slow + Popular Pages

Slow + Popular Pages answers the question that pure performance reports can’t: “Which slow pages matter most to real users?” It plots every tracked URL at the intersection of popularity (click volume from Search Console) and PageSpeed score, so the pages that deserve engineering time the most — high traffic, poor performance — stand out immediately.

The key column: Speed priority

Each row carries a Speed priority: its clicks, weighted by how far its mobile PageSpeed score is below 100. A busy page with a poor score ranks above a quiet page with the same score. It is a way to order the work, not a count of visitors who had a slow visit: a PageSpeed score is a lab measurement, not a share of real visits.

The scatter chart

Each URL is plotted with clicks on the y-axis and mobile PageSpeed score on the x-axis. The four quadrants:

Top-left: Fix these first

High clicks, low score. Maximum user impact. A single engineering sprint here is worth more than ten fixes on low-traffic pages.

Top-right: Healthy stars

High clicks, good score. Protect these pages — monitor them in PSI History to catch regressions early.

Bottom-left: Fix eventually

Low clicks, low score. Performance problems exist but few users are affected. Fix as part of platform-wide work, not as a priority sprint.

Bottom-right: Monitor only

Low clicks, good score. No action needed unless clicks grow.

Table columns

  • URL — links to the live page.
  • Clicks — total organic clicks in the selected window from Search Console.
  • Mobile score — the latest Lighthouse performance score on mobile. Colour-coded good / needs improvement / poor.
  • Desktop score — the latest Lighthouse performance score on desktop.
  • Speed priority — clicks weighted by how far the mobile score is below 100. The column to sort by.
  • LCP / CLS / INP — the three Core Web Vitals, colour-coded.

What to do with it

  1. Sort by Speed priority, highest first. Take the top 5 as this quarter’s performance sprint backlog.
  2. For each URL, open the PSI Diagnostics and PSI Opportunities reports to understand the root cause before writing any code.
  3. After fixing, track progress in PSI History and re-sort this report monthly to refresh the backlog.
  4. Cross-reference the top rows with Striking Distance: if a slow page also has high-value queries sitting at positions 11–20, performance work can unlock both UX and ranking improvements simultaneously.

Related reports