Apogee Watcher

Posted on Aug 31 Originally published at apogeewatcher.com

Attention-Free Score: How Domain Reports Show Which Pages Need Work

#webdev #webperf #seo

We have updated how our domain-level reports work. A lot of users gave us feedback that the multi-page domain reports can list forty Lighthouse runs across mobile and desktop before they can track down the URL that actually needs work. Opening every strategy tab, scanning colour chips, and mentally counting failures does not scale when you run prospect scans, free-check funnels, or portfolio roll-ups for several clients in one week.

Apogee Watcher domain reports now open on a Summary tab by default. The headline answer is an attention-free score: the percentage of completed tests that pass every lab gate we track on that report. 100% means no test on either strategy still needs attention. Everything else on Summary is designed to show where to start before you drill into Mobile, Desktop, or Tested pages.

Why shared domain reports needed a Summary-first view

Domain reports roll up PageSpeed Insights / Lighthouse results from many URLs into one shareable link. That is the right format for agency prospecting, client readouts, and the public free domain scan. It is also easy to overwhelm: two strategies per page, four category scores, lab metrics, and grouped opportunities multiply quickly.

Single-URL PageSpeed Insights answers “how does this URL look right now?” Domain reports answer “which URLs on this host matter most after a batch run?” Those questions need different layouts. We kept the full Mobile and Desktop tabs for auditors who want every score card and opportunity list. We added Summary so you can answer “does anything need work, and where?” without tab hopping.

Summary is lab data only. It reflects the tests that finished on the report, not Chrome UX Report field history. Pair it with CrUX and field-data guidance when you explain trends to clients; use Summary when you need a fast lab triage pass after a scan or scheduled run.

Live example: apogeewatcher.com domain report Summary — 68% attention-free, with LCP as the top gap on blog and category URLs on mobile.

What the attention-free score measures

The attention-free score is the share of completed page tests (mobile and desktop runs counted separately) that pass all of the following gates on that test:

Gate	Threshold
Lighthouse Performance	≥ 90
Accessibility	≥ 80
Best Practices	≥ 80
SEO	≥ 80
Largest Contentful Paint (LCP)	≤ 2.5s
Cumulative Layout Shift (CLS)	≤ 0.1
Interaction to Next Paint (INP)	≤ 0.2s when present
Total Blocking Time (TBT)	≤ 200ms when INP is missing (lab fallback)

A test that fails any gate counts toward “needs attention.” A test that passes every gate counts as attention-free. The percentage is not an average of performance scores across pages. It is a strict pass rate across the full gate set, so a single weak CLS value on a product URL keeps that test out of the attention-free bucket even when Performance looks fine.

The headline beside the score states the same idea in plain numbers, for example “12 of 38 tests need attention.” Site status and top gap labels give a one-line severity read when the data supports it. Average Lighthouse Performance for mobile and desktop may appear under the score when those aggregates are available.

Pages, tests, and metrics on domain reports

Summary uses three terms consistently across the report header and coverage line:

Pages — URLs you selected for the run (or that discovery suggested).
Tests — Lighthouse runs. Each page tested on mobile and desktop counts as two tests when both strategies complete.
Metrics — measurements inside a test: LCP, CLS, INP, category scores, and supporting lab values.

We removed vague “sample” wording so report copy matches what agencies paste into emails and slide decks. The coverage line at the bottom of Summary reads like “19 pages selected · 17 pages with completed tests · 34 tests completed” so you can see whether failures come from missing runs or from real gate breaches.

What you see on the Summary tab

Open any shared domain report at https://apogeewatcher.com/reports/domain/{token} and you land on Summary (#summary). The tab bar still lists Mobile, Desktop, and Tested pages when you need the full strategy view.

On Summary you typically see:

Site status badge (pass, watch, or needs attention) and optional top gap label.
Attention-free score (percentage) with the headline count of tests that need work.
Dimensions needing attention — a fails-only scoreboard with mobile and desktop averages for metrics that are still outside good thresholds, plus how many tests fail each dimension.
What we found — short bullet findings and an optional recommended first action when the builder can infer one.
Top pages requiring attention — up to five rows with a Why column that names the failing metric and value (for example Perf (88%) or LCP (3.45s)), not a generic “poor” label.
Attention by page type — counts grouped by classification (product, content, checkout, and so on) so you can see whether failures cluster on templates.
Top opportunities merged across mobile and desktop — one row per Lighthouse theme with counts like “5 pages on mobile and 7 pages on desktop affected,” linking into both strategy tabs.
Coverage — pages selected, pages with completed tests, and tests completed.

PDF exports follow the same order: Summary first, then stacked mobile, desktop, and tested-pages sections. Tested pages tables use colour coding (red / orange / green) for quick scanning when you do open the full per-URL grids.

How lab gates relate to Core Web Vitals and Lighthouse categories

The gates mirror what many agencies already treat as “good enough for lab” on client reports, aligned with Core Web Vitals thresholds for LCP, CLS, and INP and with Lighthouse category scoring bands readers already see in PageSpeed Insights.

Performance ≥ 90 is deliberately stricter than “green” on some dashboards because domain reports are often used before a sales call or a sprint planning meeting. Accessibility, Best Practices, and SEO at ≥ 80 catch regressions that pure Performance scores hide, especially on content-heavy templates.

INP is evaluated when the lab run records it. When INP is absent (common on some URLs or tool versions), Total Blocking Time ≤ 200ms acts as the interaction proxy so mobile tests still have an input-responsiveness gate. That matches how teams read lab data when field INP is not yet available for a URL.

Summary does not replace performance budgets you configure inside Watcher for monitored sites. Budgets can fire alerts on your schedule. Summary gates are fixed on the report so every shared link speaks the same language.

Page-type breakdown and merged opportunities

When page classification is available, Summary groups attention counts by page type. On a commerce scan you might see product URLs failing LCP while blog posts pass Performance but fail SEO category gates. That pattern is hard to spot when URLs are sorted only by path.

Merged opportunity rows address another multi-tab pain point. The same Lighthouse audit (render-blocking resources, image delivery, unused JavaScript) often appears on both Mobile and Desktop tabs with different affected URL counts. Summary merges those into one theme row and links to both tabs so you do not double-count work when writing a fix brief.

Opportunity lists on Mobile and Desktop still show the full audit text, Chrome documentation links, and related Apogee Watcher how-to posts where we have a match. Summary is the map; the strategy tabs remain the detailed evidence.

Summary links for agency outreach and client reports

Agencies told us they wanted a single link that answers “what should we fix first?” without pasting four screenshots. Summary is built for that workflow.

Share https://apogeewatcher.com/reports/domain/{token}#summary in prospect email, Slack, or a client-ready report outline. Lead with the headline count and top gap, point to the top five pages table for specifics, and mention page-type concentration if the prospect runs a large catalogue site.

For monitored portfolios, generate domain reports from the site Reports tab after scheduled runs, then use Summary to decide whether this week’s deploy needs a full Mobile/Desktop review or can wait until the next scheduled test pass. The same Summary layout appears on free-check reports, lead prospecting runs, and customer site snapshots so your team does not relearn a different report shape per entry point.

We document the full August release in Changelog #12 (domain report Summary, lead classification, and discovery updates).

Where Summary appears in Apogee Watcher

Summary is on every public domain report served at /reports/domain/{token}:

Free domain scan — after /check completes, the emailed link opens on Summary.
Lead prospecting — domain reports you generate from a lead record use the same tab layout and page-type grouping on Tested pages.
Monitored sites — organisation members can generate customer domain reports from the site view; org members and sysadmin users can open expired share links when policy allows.

CrUX and field-history charts are not on Summary today. Phase B work may add field context beside lab gates later. For now, treat Summary as the lab triage layer and pull field series from PageSpeed Insights, CrUX Vis, or your scheduled monitoring history when the client conversation requires both clocks.

FAQ

What counts as one test in the attention-free score?

One completed Lighthouse run for one URL on one strategy (mobile or desktop). Ten pages with both strategies complete count as twenty tests.

Does 100% attention-free mean the site is perfect for users?

It means every completed test on the report passed all lab gates listed above. Lab scores can still differ from field Core Web Vitals on high-traffic URLs. Use field data for search and UX claims; use Summary for fast lab triage after a batch run.

Why might INP use Total Blocking Time instead?

Some lab runs do not emit INP for the tested URL. When INP is missing, we apply the TBT gate so interaction cost is not ignored on mobile tests.

Can I link directly to Summary?

Yes. Append #summary to the report URL. Mobile, Desktop, and Tested pages use #mobile, #desktop, and #pages.

How is this different from a single PageSpeed Insights URL check?

PageSpeed Insights focuses on one URL at a time. Domain reports aggregate many URLs and strategies, and Summary compresses that batch into one attention-free percentage and a short priority list.

Try Summary on your next domain report

Run a free domain scan on a client host, open the live apogeewatcher.com Summary example, or start any recent prospect report at #summary. Note the attention-free percentage, scan the fails-only scoreboard, and check whether failures cluster in one page type. Switch to Mobile or Desktop only when you need the full opportunity text.

If you already monitor sites in Watcher, generate a domain report from the site Reports tab after your next scheduled run and compare Summary against your performance budgets. Sign up free to save scans, schedule tests, and share reports without rebuilding the URL list each time.

DEV Community