Coder Legion - Recent posts tagged client-reports

Site-Level Guidance: AI Actionable Insights Leave Beta

Mon, 26 Oct 2026 07:52:55 +0000

Agencies already know how to read a single PageSpeed Insights run. The harder job is turning twenty URLs on one host into a fix order a developer can ship without reopening every Lighthouse tab. Domain report Summary gave us a deterministic triage layer earlier this year: attention-free score, top pages, and merged opportunities. What was still missing was an optional synthesis step that names shared problems and ranks what to change first across the property.

That step is out of beta. AI actionable insights now generate from a domain-report snapshot in Apogee Watcher: one site-level evaluation grounded in stored PageSpeed / Lighthouse evidence, not a one-off chat about a single homepage run. We also refreshed the site view so tests, pages, discovery, and reports stay in one workspace when you prepare that snapshot.

What site-level AI insights do with PageSpeed evidence

AI insights answer a different question from a single-URL Lighthouse chat. Tools that paste one PageSpeed Insights JSON into a language model explain that URL. Watcher starts from a domain report: up to about twenty pages already tested on mobile and desktop, with scores and opportunities already grouped. The model sees a bounded summary of site problems built from that snapshot. It returns a short narrative, a prioritised how-to-fix list, and evidence that points at shared templates, third parties, or headers when those patterns repeat.

Lighthouse remains the source of truth for scores and audits. The insight does not re-score the site or invent metrics that were not in the stored runs. It synthesises what the deterministic report already shows, so an account lead can hand a developer an ordered checklist instead of a screenshot dump. That site-level default is deliberate: calling a model on every completed page test would use quota quickly and mostly rewrite audit text you already have.

Approach	Input	Typical output	Fit
Single-URL AI + Lighthouse	One page, one strategy	Explain this run	Spot check or homepage deep dive
Watcher AI insights	Domain-report snapshot (multi-page)	Prioritised site fix plan	Agency portfolio triage after scheduled tests

If you only need “what is red on this URL right now,” PageSpeed Insights or the Mobile / Desktop tabs on the domain report are enough. AI insights fit when the brief is “what should we change across this property first?” The distinction matters in client emails: one explains a spot check, the other briefs a template or third-party change that shows up across many URLs. Agencies usually need both over a quarter; they just should not confuse them on the same call.

How AI insights sit next to the domain report Summary

Attention-Free Score: How Domain Reports Show Which Pages Need Work remains the always-on layer. Summary is free with the report: attention-free percentage, dimensions needing attention, top pages, and merged opportunities. No language-model credit is spent to open it.

AI insights are the optional layer on the same snapshot. Generate when you want natural-language prioritisation and a fix checklist grounded in recurring audits. Skip generate when Summary already answers the client call. Public share links show the insight body only after someone with access has generated a completed insight; visitors never see an empty AI box or a Generate button on the public URL.

That split keeps lab triage honest. Deterministic Summary is the scoreboard. AI is the briefing note you write when the portfolio needs a narrative, not a replacement for budgets, alerts, or scheduled monitoring. For the broader monitoring loop, see What Is Automated Web Performance Monitoring? and PageSpeed Insights vs Automated Monitoring.

Where to generate AI insights in Watcher

Generation starts from evidence that already exists. After scheduled or manual tests finish, a Manager or Admin creates a domain report from the site Reports tab. In the app, the report’s AI insights tab shows either an empty state with Generate AI insights, or the stored insight with Regenerate and Copy markdown. The same generate action is available from the site Reports list.

Live example: apogeewatcher.com domain report AI insights — site-level summary, priority fixes, and quick wins on the public share URL.

Each generate or regenerate uses one AI credit for the organisation’s current monthly period. Caps and remaining usage appear in the topbar Plan & usage panel next to sites, organisations, and tests. Step-by-step detail is in Domain performance reports and Understand plan limits.

On the public domain report URL, recipients see the insight only when a completed one exists. That keeps prospect and client links tidy: you decide when synthesis is ready to share, then send the same token you already use for Summary. Until you generate, the public page stays a clean lab readout without an empty AI placeholder.

AI insights quota and which plans include them

Default paid tiers from Personal upward include AI insights. Free does not. Pricing and My Account show whether the feature is on before you promise synthesis in a retainer scope. Monthly AI credit limits sit beside test volume on purpose: synthesis is meant for site evaluations, not one model call per scheduled page run.

When the meter is empty, Generate and Regenerate stay blocked until the period resets or the plan changes. Site-level evaluation is the default we ship; per-run AI deep dives remain a future path if customers ask for them. Portfolio roll-ups across many client sites are also later work. For weekly organisation PDFs and white-label branding already live, see Weekly Organisation Reports and White-Label Branding Options Are Live.

Updated site view: tests, pages, discovery, and reports together

Alongside AI insights leaving beta, we refreshed the site view in the app so day-to-day monitoring work does not scatter across unrelated screens. From Setup → Sites, a property opens as one record: pages and discovery for the URL pool, test history for what already ran, statistics for recent lab movement, and Reports for domain-report generation and AI actions. Fewer switches between “find URLs,” “see what ran,” and “share what it means” means fewer stale snapshots.

Insights are only as good as the evidence behind them. Discovery and page lists decide which URLs enter the report pool. Scheduled tests fill that pool. Reports turn the results into a shareable Summary and, when you choose, an AI briefing. Keeping those steps on one site record lowers the chance that someone generates synthesis from an incomplete page set.

Client-ready reporting habits still apply: budgets and schedules first, then shared links. Client-Ready Core Web Vitals Report Outline remains useful when Summary plus an insight becomes a retainer narrative. The insight works as the ordered checklist inside that outline, not as a substitute for the scoreboard.

What AI insights do not claim

We are explicit about scope so contracts stay clean:

Insights do not replace Lighthouse scores, audit lists, or Attention-Free gates.
Insights do not guarantee rankings, Core Web Vitals field improvements, or pass/fail after a deploy. You still re-test and compare stored runs.
Insights are not generated on every completed PageSpeed run by default.
Public visitors cannot spend your AI credits.
Free plans cannot generate insights.

The useful promise is narrower: faster time from multi-page red metrics to a concrete, evidence-backed checklist your team can implement and then verify with scheduled lab tests.

FAQ

Do I need AI insights to use domain reports?

No. Summary, Mobile, Desktop, and Tested pages work without generating an insight. AI is optional synthesis on Personal and higher plans that include the feature.

No. The public URL shows a completed insight when one exists. Generate and Regenerate stay in the signed-in app for roles that can manage reports, so visitors cannot spend your monthly AI credits.

Is this the same as pasting PageSpeed Insights into ChatGPT?

No. Watcher builds a bounded site summary from a multi-page domain-report snapshot already stored for your organisation. Single-URL chat tools explain one run; they do not see your scheduled portfolio context or recurring audits across templates.

Will AI insights appear on weekly organisation PDFs?

Not in this release. Organisation weekly reports and white-label PDFs remain the portfolio pack described in the September ship note. Domain-report AI is site-level synthesis on the HTML report path first.

What should I do after I apply a recommended fix?

Re-run tests on the affected pages, regenerate the domain report when you want a fresh snapshot, and compare Attention-Free and opportunity lists. Treat the insight as guidance before the fix, not as a certificate after deploy. Pass or fail still comes from the next stored lab runs, the same way budgets and alerts already work.

If you want site-level guidance on top of the monitoring loop you already run, open a site with completed tests, generate a domain report, then use Generate AI insights when the plan includes the feature. A trial starts at sign-up; a free domain check shows Summary without AI first. Changelog #14 at the end of October will cover the wider product window.

References

Domain performance reports (Apogee Watcher docs)
Understand plan limits (Apogee Watcher docs)
Plan features by tier (Apogee Watcher docs)
Attention-Free Score: How Domain Reports Show Which Pages Need Work
What Is Automated Web Performance Monitoring?
PageSpeed Insights vs Automated Monitoring: When Manual Checks Aren't Enough
Weekly Organisation Reports and White-Label Branding Options Are Live
Client-Ready Core Web Vitals Report Outline
PageSpeed Insights API (Google for Developers)
Lighthouse in Chrome DevTools (Chrome for Developers)

Originally published on Apogee Watcher.

TTFB Is Not Only the Server: The Unattributed Slice Agencies Should Name in Reports

Wed, 07 Oct 2026 07:01:26 +0000

Time to First Byte is often treated as a synonym for back-end time. In the browser it is wider: everything from the start of the navigation until the first byte of the final response arrives. Redirects, DNS, connection setup, TLS inside that connection, network latency, CDN and origin work, and browser overhead can all sit inside the same number. When agencies paste a high Waiting (TTFB) bar into a client slide and write “server response,” they may be describing only the part the waterfall labels clearly.

Unattributed Navigation Overhead (UNO) is the residual after you subtract the phases Navigation Timing can name. Harry Roberts documented the metric and the agency reporting problem in UNO Is Underrated, building on Tim Vereecke’s framing: measure the whole journey to the first byte, subtract every attributed phase, and keep whatever is left. The leftover may be hard to pin on one owner. It is still time users paid for. Naming it stops missing milliseconds from being assigned to origin PHP by default.

What follows is a how-to for agencies who already walk delivery-layer TTFB in Network Performance for Web Teams: DNS, TLS, HTTP, CDN, and Cache Rules. When the attributed server phase is the real bottleneck after the residual is accounted for, hand off to TTFB Won't Go Down? Server-Side Culprits Beyond the Theme.

UNO is not a browser-provided metric. It is a calculated remainder:

UNO = TTFB − redirect − DNS − connection − (request → responseStart)

In Navigation Timing terms, TTFB for this purpose is responseStart − startTime (or the nearest equivalent your RUM tool exposes). Subtract the visible redirect span, DNS lookup, full connection span (TCP plus TLS when the API folds them together), and the span from requestStart to responseStart. What remains, floored at zero, is UNO.

That residual can include browser initialisation, delays while unloading the previous page, disk or cache access, resource contention, and timings hidden by cross-origin restrictions. It is not another name for redirect time. Hidden cross-origin redirects are a common source of UNO, but treating every unexplained millisecond as “a tracking redirect” repeats the same attribution mistake with a different label.

CrUX can tell you field TTFB is poor. It cannot decompose that time into phases, so it also cannot compute UNO. Without a Navigation Timing breakdown from real navigations (or a careful local reproduction), all of TTFB is effectively unattributed in the Google field dataset.

A useful client-facing breakdown starts with the named hops, then shows the residual. Keep the language plain enough for a non-engineer stakeholder, and precise enough that engineers can map it back to DevTools. If the slide only shows total Waiting, every remedy conversation defaults to hosting.

Phase	What it usually covers	Where teams over-blame
Redirect	Visible same-origin (or opted-in) redirects before the final response	Ignoring hidden cross-origin hops that never appear in `redirectCount`
DNS	Domain lookup for the final host	Blaming “DNS” when connection or residual dominates
Connection	TCP + TLS setup for the final host	Calling all Waiting “TLS” when connect is short
Request → first byte	Time from sending the request until `responseStart`	Calling this alone “the server” when UNO is large
UNO	Everything in TTFB not in the rows above	Leaving it unnamed so it inherits the server label

Lighthouse and PageSpeed Insights still surface high first-byte time under diagnostics such as Reduce initial server response time. That audit name is historically server-shaped. It does not prove that PHP, WordPress cron, or database load owns the whole bar. Pair the lab label with a Navigation Timing breakdown before you write the remediation paragraph. PageSpeed Insights versus automated monitoring explains why a single paste also misses hour-of-day and campaign-mix effects that change which phases dominate.

For DNS, TLS, HTTP version, and CDN cache rules that actually move the attributed network phases, stay inside the network performance guide. The focus here is the slice those guides do not name: the unattributed remainder.

Why redirect, DNS, and connection phases still leave a gap

Navigation Timing often fails to add back up to TTFB. Gaps exist between timestamps. Some timings are deliberately hidden. The browser still includes that time in TTFB; it simply will not (or cannot) attribute it in the redirect, DNS, or connection fields.

Cross-origin redirects are the clearest example. When a navigation includes a cross-origin hop, Navigation Timing has traditionally reported redirectStart, redirectEnd, and redirectCount as zero. Overall TTFB still includes the hop. The redirect vanishes from the breakdown and lands in UNO. Common journeys include affiliate or ad tracking wrappers, URL shorteners, social outbound wrappers, and even http:// to https:// on the same hostname. A change of scheme is a change of origin. What looks like a harmless first-party canonicalisation can still hide redirect timing.

Synthetic tests that open the final landing URL never walk that chain. CrUX folds the cost into TTFB. Agencies comparing a clean lab homepage to a paid-search landing path then argue past each other: one chart shows a short Waiting bar, the other shows field TTFB that “must be the server.” Segment by landing page, campaign, and referrer when UNO rises. Reproduce representative journeys in DevTools instead of assuming origin compute.

Chrome has started improving opt-in visibility for some cross-origin redirect timing via Timing-Allow-Origin on redirecting servers. Adoption across shorteners and campaign platforms will be uneven for a long time. Even with better visibility, UNO still matters: not every residual is a redirect, and not every redirect will opt in.

On a page you control, open DevTools Console after a hard navigation and read the navigation entry. The shape matches Harry’s public snippet:

const navigation = performance.getEntriesByType('navigation')[0];
const span = (end, start) => Math.max(0, end - start);

const uno = Math.max(0, Math.round(
  (navigation.responseStart - navigation.startTime) -
  span(navigation.redirectEnd, navigation.redirectStart) -
  span(navigation.domainLookupEnd, navigation.domainLookupStart) -
  span(navigation.connectEnd, navigation.connectStart) -
  span(navigation.responseStart, navigation.requestStart)
));

Do not treat a single Console value as portfolio truth. Cache warmth, device, connection, and previous-page unload all move the residual. For client work, collect UNO as both a duration and an occurrence count in RUM (or in a small beacon you control), then segment. Chart it beside redirect, DNS, connection, attributed server waiting, total TTFB, and Largest Contentful Paint. When LCP is TTFB-sensitive, unexplained first-byte time is not academic; it delays paint. A Quick Way to Fix LCP: Four Changes That Cut Time to Paint still applies after you know whether the early wait is attributed server time or UNO.

For a quick sanity check of hidden redirects, open a shortened URL that lands on a known host, then compare redirectCount (often zero) with a non-zero UNO. Contrast that with a same-origin trailing-slash redirect that does enumerate. The point is not the demo URL; it is that visible redirect count alone is a poor map of real campaign traffic.

What agencies should name in client reports when TTFB looks “server-only”

Client reports need a labelled residual. A practical slide or appendix row looks like this:

Total TTFB (lab on the money URL, plus field TTFB when CrUX exists).
Attributed phases you can defend: redirect (visible), DNS, connection, request→first byte.
UNO as “unexplained navigation time inside TTFB,” with a one-line definition.
Next action by owner: campaign/redirect chain, delivery (DNS/TLS/CDN), or origin application.

Write the sentence that prevents the wrong ticket. Prefer: “Field TTFB is elevated; Navigation Timing leaves X ms unattributed after redirect, DNS, connection, and request timing. We will reproduce campaign landings before we open a hosting upsizing ticket.” Avoid: “Server response is slow” when the only evidence is a total TTFB bar.

Use Performance Budget Thresholds Template so money URLs have explicit first-byte budgets, then annotate whether breaches are attributed server time or UNO-heavy. Schedule lab coverage on priority URLs with PageSpeed monitoring test frequency and priority across a portfolio so you are not inventing the breakdown from a single Friday afternoon paste. Watcher’s multi-tenant schedules keep those lab baselines comparable week to week; they do not replace RUM for UNO segmentation, and you should say that plainly when the residual only appears on campaign landings.

When the attributed server phase is the real bottleneck

Name UNO first. Then look at the request→responseStart span (and any RUM “server” or Waiting attribution your tool exposes after known network phases). If that attributed slice dominates, and DNS/connect/UNO are small, origin work is the honest story.

That is when TTFB Won't Go Down? Server-Side Culprits Beyond the Theme becomes the runbook: WP-Cron storms, cold PHP workers, missing object cache, database load, backup plugins at peak. Do not start there when UNO or hidden redirect chains explain most of the bar. Do not skip there when the residual is already named and still tiny beside a long attributed wait.

Pattern	Likely owner	First move
High UNO on campaign/referrer segments; lab direct URL fine	Redirect / landing path	Reproduce chain; talk to tracking/shortener owners
High DNS or connect; UNO modest	Delivery / network	Network performance checklist
High request→first byte; UNO and connect small	Origin application	Server-side TTFB checklist
Everything elevated after a browser-major mix shift	Population / measurement	Annotate releases; do not only ship origin tickets

TTFB is not a Core Web Vital, but it still gates LCP because HTML must arrive before the largest content can paint. Keep that link explicit in reports so stakeholders do not treat first-byte work as vanity once LCP is the slide title. Naming UNO does not replace LCP fixes; it stops you spending the LCP budget on the wrong first-byte owner.

Why CrUX and one-off lab runs miss the unattributed slice

CrUX reports field TTFB without the Navigation Timing phases needed for UNO. Useful as a population signal; useless as a phase budget. One-off PageSpeed Insights or Lighthouse runs on the final URL skip affiliate and shortener chains, warm different caches, and label the wait with server-shaped language. Neither artefact is wrong for what it measures. Both are incomplete if your clients’ money arrives through wrapped links.

Proper RUM (commercial, open-source, or homegrown) that retains navigation timestamps, page-view context, and dimensions is how UNO becomes actionable. You need duration and occurrence count, not only a p75. You need breakdowns by landing page, campaign, referrer, browser, device, and connection. Synthetic schedules still matter for regression detection on known URLs; they answer a different question. When to use synthetic versus real user monitoring is the pairing guide when a stakeholder asks which chart to trust.

FAQ

What is unattributed navigation overhead?

It is the part of Time to First Byte left after subtracting the redirect, DNS, connection, and request-to-response phases exposed by Navigation Timing. It is a residual metric, not a single browser-reported timer. You calculate it so unexplained time has a label instead of inheriting the server narrative.

Is UNO the same as redirect time?

No. Hidden cross-origin redirects often inflate UNO, but browser work, cache access, unload delays, and other gaps can sit there too. Do not rewrite “unattributed” as “redirects we have not counted yet” without evidence from reproduction and referrer or campaign data.

Why are some redirects missing from Navigation Timing?

For privacy and origin-boundary reasons, cross-origin navigation redirects have traditionally reported zero redirect timing and count even when TTFB includes them. Scheme changes such as HTTP to HTTPS count as cross-origin even on the same hostname. The hop still costs users; only the breakdown loses it.

Can CrUX report UNO?

No. CrUX exposes field TTFB without the phase timestamps required to calculate the residual. Use RUM or a Navigation Timing beacon on your own traffic if you need the split.

How should we talk about this in a client report?

Show total TTFB, the named phases, and a labelled UNO row. State the next owner (campaign path, delivery, or origin) instead of defaulting every elevated first-byte chart to “upgrade hosting.” One honest residual row prevents a week of origin tickets that never touch the real journey.

When do we optimise the server instead?

When the attributed request→first-byte (or tool-equivalent server) phase dominates after UNO and network phases are small. Use the server-side TTFB checklist. That hand-off is intentional: UNO naming first, origin work second.

If your retainers still describe every Waiting bar as server time, add UNO to the next report cycle on two or three campaign-heavy URLs and compare it with a direct lab navigation. Keep scheduled lab baselines on those URLs while you wire RUM (or a small beacon) for the Navigation Timing breakdown clients never see in CrUX alone. Start a free Apogee Watcher trial when you want those lab checks on a multi-tenant schedule without pasting PageSpeed Insights by hand.

References

Unattributed Navigation Overhead (UNO) Is Underrated (Harry Roberts / CSS Wizardry; metric coined by Tim Vereecke)
Web-Perf Wednesday 006 – Faster Browser Releases Change Your RUM Population (CSS Wizardry)
Navigation Timing Level 2 (W3C)
Time to First Byte (TTFB) (web.dev)
Network Performance for Web Teams: DNS, TLS, HTTP, CDN, and Cache Rules
TTFB Won't Go Down? Server-Side Culprits Beyond the Theme
A Quick Way to Fix LCP: Four Changes That Cut Time to Paint
PageSpeed Insights versus automated monitoring
Performance Budget Thresholds Template
PageSpeed monitoring: schedule test frequency and priority across a portfolio
When to use synthetic versus real user monitoring

Originally published on Apogee Watcher.

Weekly Organisation Reports and White-Label Branding Options Are Live

Sat, 03 Oct 2026 06:58:48 +0000

We have shipped the weekly organisation reports agencies keep asking for on retainers: a portfolio PDF built from scheduled PageSpeed Insights history, plus white-label branding options so the file can leave under your agency name instead of ours.

Until now, teams could already schedule tests, set budgets, and share domain-level roll-ups. What was missing was a recurring organisation-level pack that arrives without rebuilding a deck every Sunday night. That pack is live. Branding for it is live too, on plans that include white-label reports. Monthly and custom period types remain reserved for later; we say that plainly below so contracts stay honest.

If you need the full monthly retainer workflow (budgets, narrative, upsell), keep From Scheduled Tests to White-Label CWV Reports: A Monthly Retainer Workflow beside this note. What follows is the product change: what Watcher generates, which branding fields you control, and how to turn the pack on. It is the ship note, not a remake of the five-step retainer guide.

What weekly organisation reports include

Organisation reports are portfolio roll-ups for a workspace. They are not a single-URL share link, and they are not the public multi-page domain report Summary. One organisation can cover many client sites; the weekly report aggregates completed lab tests across those sites for a Monday–Sunday period. That distinction matters in client emails: a domain report answers “which URLs on this host need work after a batch run?” An organisation weekly report answers “how did this portfolio move last week, and which sites should the account lead open first?”

On a typical weekly row you will see:

Period labelled by day range (for example 14-20/Sep/2026), with a · preview marker when the week is still in progress.
Insight summary: a short narrative built from the week’s movers (strongest drop, biggest gain, how many sites improved versus declined, alerts opened versus closed, and similar). It does not restate the KPI cards below it.
KPI cards: average Lighthouse Performance, attention-free share of tests in the period, sites and tests covered, alerts, and API usage where relevant.
Site breakdown and movers: which sites improved or regressed so account leads can open the right client first.
PDF download when the organisation owner’s plan includes PDF reports (typically Professional and above; confirm on Pricing and My Account).
Email to organisation admins when the Sunday job finishes, with the PDF attached when PDF reports are on the plan.

The Sunday job runs at 08:00 in the app timezone for each active organisation that had completed lab tests in the prior week. You do not author the report body in the app; Watcher builds the row from stored test history. If a Preview already exists for that week, the final Sunday run finalises it rather than leaving a duplicate. Full steps are in Organisation reports and PDF.

Scores on the row use the same lab language agencies already know from domain reports. Average performance is the mean Lighthouse Performance score over valid completed tests in the period. Attention-free percentage is the share of those tests that pass the evaluated Attention-Free gates (Performance and Core Web Vitals thresholds; accessibility, best practices, and SEO gates apply when those scores are present on the site test rows). Use those two numbers to skim the portfolio, then open movers to see which sites changed and why.

Here is a public sample PDF for the same demo week (21–26 Sep 2026): markg weekly organisation report PDF.

White-label branding options for agency PDFs

White-label packaging is a separate plan feature from basic PDF export. You can have PDF downloads without agency theming; white-label applies your logo, colour, and font when the plan includes it (typically Professional, Agency, and Enterprise; check My Account for the current flags). Confirm both PDF reports and White-label reports on My Account before you promise branded files in a client scope.

When white-label is available, open Setup → Organisations, edit the organisation, and set:

Field	What it controls
Report logo	Image at the top of the weekly PDF. If empty while white-label is on, Watcher uses the default Apogee Watcher report logo.
Primary colour	Hex accent used in the PDF (for example `#ff6633`).
Font family	Choice from a curated DomPDF-safe list of Google Fonts that embed as TrueType.

On the report view, White-label shows On or Off. New scheduled runs and Preview runs pick up current branding when white-label is on. After you change logo, colour, or font on an existing weekly row, use Regenerate PDF so the stored file matches the organisation settings. That regenerate step matters when you correct a logo the night before a client call: you do not need to wait for next Sunday.

Step-by-step branding setup is in White-label reports. For the broader case for branded packs, see White-Label Performance Reports: What They Are and Why Agencies Need Them. Contracts that promise a “fully self-serve white-label portal” still need a tier check first; the flags live on Pricing and My Account, not in a sales deck alone.

How to preview, download, and regenerate a weekly pack

A practical first week with the new reports looks like this:

Confirm schedules are running on the priority URLs for each site in the organisation.
Set organisation branding if your plan includes white-label reports.
Open Results → Reports and use Preview for a Monday→today look before Sunday. Preview does not send email.
After Sunday (or after Preview), open the row, read the insight summary and site movers, then Download Report when a PDF exists.
If branding changed after the file was built, Regenerate PDF and download again.

The Reports list puts Preview above the table and shows Download on rows that already have a PDF. The sample pack linked above is what that download looks like once generated.

If you administer more than one organisation, Preview offers a dropdown of organisation names so you do not generate the wrong portfolio pack by habit. Quiet organisations with no completed lab tests in the period simply do not produce a weekly row; that is expected, not a silent failure of the scheduler. Run Preview once after branding is saved so you can see the logo and colour on a real PDF before Sunday mail.

Download steps alone are covered in Download organisation reports. Viewers and Managers can download the same finished files Admins can; only Admins edit branding and plan upgrades. When PDF reports are off for the plan, you may still see report rows in the list, but Download appears only when a file exists.

What is live versus still reserved

Honesty here matters more than a glossy cover. Use this table when you brief account leads or write client scopes. It matches the Feature Disclaimer we use elsewhere in Watcher content: say what is live, what is reserved, and what is still coming.

Capability	Status
Weekly organisation report (Sunday schedule)	Live
Preview current week (Mon→today)	Live
PDF download (`pdf_reports`)	Live on plans that include it
White-label logo, colour, font (`white_label_reports`)	Live on plans that include it
Regenerate PDF after branding changes	Live
Monthly organisation report type	Reserved (not self-serve yet)
Custom date-range organisation report type	Reserved (not self-serve yet)
Slack and webhook alert delivery	Coming soon
Organisation-scoped Leads Management with RBAC for every agency seat	Coming soon (prospecting today is largely an internal / sysadmin MVP)

Weekly PDFs are the automated evidence pack. A monthly retainer narrative still benefits from your account lead’s prose (executive summary, work completed, next-period plan) on top of the weekly numbers. That is intentional: the product removes last-minute history gathering and brand packaging; it does not invent a full monthly story editor yet.

How this changes the monthly retainer pack

The retainer workflow post already argued that white-label without a schedule is still a branded last-minute pack. With weekly organisation reports live, Step 4 packaging is no longer “support-assisted branding and hope the deck is ready.” You can pull last week’s PDF (or four weekly PDFs) into the month-end review, keep logo and colour consistent across organisations without rebuilding Canva covers each time, and use Preview mid-week when a release week needs an early look before the Sunday mail. That is the practical change for teams who already sell a monthly performance report retainer.

The client-facing monthly report can remain one narrative PDF or slide pack. Watcher’s job is the dated evidence and the branded weekly attachment. Pair the weekly file with the client-ready Core Web Vitals report outline when you draft the retainer letter. Account leads still own the “work completed” and “next period plan” paragraphs; Watcher owns the dated scores behind those paragraphs.

FAQ

Are white label organisation reports the same as domain reports?
No. Domain reports roll up many URLs on one hostname for a shareable triage page (including attention-free score on Summary). Organisation weekly reports roll up sites inside a workspace for a period, with PDF and optional white-label branding.

Can we send an agency branded PageSpeed PDF today?
Yes, when your plan includes PDF reports and white-label reports. Set logo, colour, and font on the organisation, confirm White-label shows On, then download or regenerate the weekly PDF. Pricing and My Account show the flags before you promise a fully branded portal in a contract.

Is there a hands-off monthly organisation report yet?
Not as a self-serve monthly type. Weekly automation is live. Monthly and custom period badges are reserved for later retainer and ad-hoc packs. Until those ship, build the monthly narrative from weekly evidence plus your own outline.

Do weekly organisation reports replace Search Console?
No. Search Console remains the field and indexing source for many SEO conversations. Organisation reports organise lab-oriented PageSpeed Insights history across the portfolio. Use both layers side by side.

Who receives the Sunday email?
Organisation admins. The PDF attaches when the plan includes PDF reports.

What fonts can we use on white-label PDFs?
A curated DomPDF-safe allowlist of Google Fonts that embed as TrueType (Inter, Roboto, Open Sans, Lato, Montserrat, and similar). Pick the font on the organisation branding form; invalid or missing fonts fall back to a safe default. Full steps are in the white-label docs.

Try it on one organisation first

Pick one retainer client, confirm schedules and budgets, set branding if white-label is on the plan, run Preview, then let the Sunday job finish once. Compare the PDF to last month’s manual pack before you roll the workflow across the portfolio. That single-organisation pilot usually shows logo sizing issues, colour contrast on printed pages, and whether the insight summary matches how your team already talks to the client.

When you are ready to expand, start from sign-up or review features and pricing, then follow Organisation reports and PDF and White-label reports for the click path in the app.

References

Sample weekly organisation report PDF (21–26 Sep 2026) (Apogee Watcher)
Organisation reports and PDF (Apogee Watcher docs)
White-label reports (Apogee Watcher docs)
Download organisation reports (Apogee Watcher docs)
From Scheduled Tests to White-Label CWV Reports: A Monthly Retainer Workflow (Apogee Watcher)
White-Label Performance Reports: What They Are and Why Agencies Need Them (Apogee Watcher)
Client-Ready Core Web Vitals Report Outline (Apogee Watcher)
Attention-Free Score: How Domain Reports Show Which Pages Need Work (Apogee Watcher)
About PageSpeed Insights (Google)
Understanding Core Web Vitals and Google search results (Google Search Central)

Originally published on Apogee Watcher.

From Scheduled Tests to White-Label CWV Reports: A Monthly Retainer Workflow

Tue, 29 Sep 2026 07:40:35 +0000

Agencies sell monthly performance retainers every week. Too many of those months still end the same way: a last-minute PageSpeed Insights run, a folder of screenshots, and a PDF that still shows someone else’s brand chrome. Clients pay for monitoring, yet what they receive is a scramble that is hard to renew and harder to upsell.

White-label Core Web Vitals reports only work when scheduled evidence is already in place. PageSpeed Insights (or equivalent lab) runs collect the history; performance budgets decide what is green or red; a short narrative turns that into action; a branded PDF or share link puts it under your agency name. The retainer conversation then rests on dates, URLs, and agreed thresholds, not on whoever had time to click “Analyse” the night before the call.

What follows is that monthly operating schedule end to end. Steps 1–3 and 5 are agency workflow: they apply whether you monitor in spreadsheets, Lighthouse CI, another portfolio tool, or Apogee Watcher. Step 4 then separates how any agency can brand and send the report from which Watcher report features are live today (weekly organisation PDFs and white-label branding), including what is still reserved. For the broader case for branded reports, see White-Label Performance Reports. For the Watcher ship note alone, see Weekly Organisation Reports and White-Label Branding Options Are Live.

Why the monthly CWV report usually fails

Most agencies already “report on performance.” That month of reporting still fails for the same reasons:

Evidence is ad hoc. Someone runs PageSpeed Insights once, pastes screenshots, and hopes the numbers still match next week.
Lab and field clocks mix. A Lighthouse score and a CrUX window get treated as the same story, so the client gets conflicting answers.
There is no shared budget language. Without thresholds the team agreed in advance, every red number becomes a debate about taste.
Branding is last-minute. The PDF still shows a monitoring vendor’s chrome, or the deck is rebuilt in Canva the night before the call.
The retainer is vague. The client pays for “monitoring” without a calendar of what arrives each month and what triggers extra work.

White-label reporting does not fix that by itself. White-label without a schedule is still a branded scramble. The workflow below fixes the scramble first (any stack), then Step 4 states Apogee Watcher’s report features honestly: what is live today (weekly organisation reports and branding options) versus what is still reserved or coming soon.

Step 1: Scheduled PageSpeed tests as the evidence base

A durable monthly report usually starts with a locked measurement rhythm, before anyone drafts client prose. That rhythm is stack-agnostic: you can run it from PageSpeed Insights by hand on a calendar, from CI, or from a portfolio monitor.

Which URLs? Money paths first (home, pricing, checkout, key landing pages) tend to repay the work; homepage-only vanity rarely does.
How often? Frequency that matches change risk works better than a fixed habit: weekly or denser for active releases; lighter for stable brochure sites. PageSpeed Monitoring: How to Schedule Test Frequency and Priority Across Your Portfolio covers priority versus frequency trade-offs.
Which strategies? Mobile and desktop both matter when the client’s traffic mix needs both; a single strategy rarely supports a full story.
Where does history live? One multi-tenant dashboard per portfolio usually beats a folder of one-off PageSpeed Insights tabs.

Scheduled tests close the “we checked once” loophole. When a client asks why LCP moved, a date range and a URL list answer more clearly than a memory of last month’s workshop. In Apogee Watcher, that layer is automated discovery, scheduled PageSpeed Insights runs, budgets, and alerts across organisations and sites. Watcher layers onto Search Console and any real-user monitoring already in use, rather than forcing a rip-and-replace of tools that answer different questions. For how agencies combine DIY, portfolio monitors, and real-user monitoring, see 3 Agency PageSpeed Stacks for 2026.

Step 2: Performance budgets before the monthly story

Budgets turn numbers into decisions. Without them, every report becomes a tour of charts. With them, the monthly report answers four questions quickly:

What stayed inside budget?
What breached, on which URLs, and since when?
Was the breach lab-only, field-only, or both?
What fits this month (fix, watch, or escalate)?

Budgets that stick are usually agreed with the client once, in writing, in the same LCP / INP / CLS (and supporting metrics) language the report will reuse every month. A shared performance budget thresholds template keeps that language consistent across accounts so account leads are not inventing new bands every quarter. When a release week is hot, those budgets also show when an extra mid-cycle note is worth sending instead of waiting for the retainer report.

For the document shape of the report itself, Client-Ready Core Web Vitals Report Outline sits beside this workflow well. The outline is the document shape, and budgets are the pass/fail rules inside it. Domain-level summaries help account leads scan a portfolio without opening every page, and Attention-Free Score explains how domain reports show which pages need work without forcing a full deep-dive every time.

Step 3: The monthly narrative (not a metric dump)

A useful monthly white-label CWV report is short on decoration and long on decisions. The reports that land with non-engineers are usually a client-ready PageSpeed PDF (or HTML share) readable in about ten minutes, with a shape like this:

One-paragraph executive summary : overall status versus budgets; biggest win; biggest risk.
Trend versus last period : same URLs, same strategies, same clocks (lab versus field labelled).
Top issues with owners : three items maximum for a standard retainer month.
Work completed : what shipped or was verified since last report.
Next period plan : what the team will watch, fix, or quote separately.
Appendix : raw tables or deep links for technical stakeholders.

Concrete wording (“mobile LCP on /checkout breached 2.5 s for seven days”) lands better than motivational lines (“we remain committed to excellence”). Clients renew when the report reduces surprise, not when it flatters. That is also where sell-the-service language from How to Sell Performance Monitoring Services to Your Clients becomes operational: the retainer is already sold, and the monthly narrative is how the promise stays visible.

A concrete month might look like this: executive summary notes mobile LCP on checkout outside budget for nine days after a tag launch; trend table separates lab averages from CrUX categories; top issues list the tag owner, a hero image ticket, and a watch-only CLS note; next period plans a denser schedule on checkout until the breach clears. That report is ready to brand. It does not need fifty Lighthouse screenshots in the main section.

How you brand and send the report is where agencies over-promise. Split the question in two: formats any agency can use for a branded monthly send, and which Apogee Watcher features generate a branded PDF without rebuilding the deck by hand. For the Watcher ship note on weekly organisation reports and branding fields, see Weekly Organisation Reports and White-Label Branding Options Are Live.

How any agency can brand and send the report

Agencies still choose delivery format for the monthly client report:

Delivery	When it fits	Notes
Branded PDF or slide deck	Formal month-end retainer report	Your narrative (Step 3) under agency logo; evidence may come from any monitor
Time-limited share link	Async review before the call	Useful for lead and domain report styles; expiry expectations belong in the send note
Live dashboard walkthrough	Technical stakeholders	Viewer-style access so clients look, not edit
Outline + screenshots (manual)	Early retainers while automation is thin	Scheduled evidence still matters; agency decks can carry brand

That table is product-agnostic. The monthly letter and review call remain yours.

Which Apogee Watcher report features are live today

On Watcher, organisation reports and white-label PDF branding are product features (plan-gated), not a Canva rebuild:

Available today:

Scheduled tests, performance budgets, email alerts, automated page discovery, multi-tenant dashboards, and team roles (Admin / Manager / Viewer).
Weekly organisation reports — Sunday schedule for the prior Mon–Sun week, Preview for Monday→today, insight summary, site movers, and email to organisation admins (Organisation reports and PDF).
PDF download on plans that include PDF reports (typically Professional and above; Pricing and My Account show the current tier flags).
White-label branding options on plans that include white-label reports: organisation logo, primary colour, and a curated font allowlist; White-label On/Off on the report view; Regenerate PDF after branding changes (White-label reports).

Coming soon:

Monthly and custom organisation report period types.
Slack and webhook alert delivery.
Organisation-scoped Leads Management with RBAC for every agency seat (prospecting today is largely an internal / sysadmin MVP; not every tenant role can run leads in-app yet).

How the two layers meet on a Watcher retainer:

Delivery	When it fits	Watcher-shaped notes
Weekly branded PDF download	Numbers for the retainer week	Organisation weekly PDF + white-label on Professional+ when flags are on
Monthly narrative + weekly PDFs	Formal month-end retainer report	Your outline (generic Step 3) plus one or more weekly org PDFs; monthly type not self-serve yet

White-label reports docs and organisation reports docs are the ops brief for the Watcher column. Weekly automation with agency branding is live in Watcher; a hands-off monthly organisation report type is still reserved. White-label PageSpeed reports still sit on top of scheduled evidence; they are not a substitute for Search Console field data.

Step 5: Retainer upsell (and optional prospecting)

A monthly report that only restates scores rarely expands the retainer. Narratives that open commercial paths usually fall into three patterns (again, stack-agnostic):

Stabilisation hours : budget breaches with a clear fix list become a scoped sprint, not an awkward “we noticed something.”
Coverage expansion : more URLs, denser schedules, or a second market or language when discovery shows gaps.
New logos : the same scheduled evidence supports prospecting: a prospect URL analysis, a one-page report, then qualify and outreach. See From Monitoring to Pipeline and The PageSpeed Prospecting Workflow. On Watcher, Feature Disclaimer honesty still applies: org-scoped leads RBAC is coming; every seat is not a full CRM today.

The upsell works when the client already trusts the monthly clock. That trust comes from scheduled tests and budgets, not from a prettier cover page alone. A monthly performance report retainer priced on delivery cadence (report plus review call) is usually easier to renew than a vague “we watch your speed” line item with no report.

A one-month operating calendar

A workable default for a standard retainer client looks like this. Ops columns are generic; the Watcher column is optional if that is your monitor:

Week	Ops (any stack)	If you use Watcher	Client-facing
Week 1	Confirm URL list and budgets; verify schedules running	Confirm org schedules and branding if white-label is on	Kick-off note: what we measure and when the report arrives
Week 2	Triage alerts; fix or ticket critical breaches	Use alert digests and site movers mid-week	Optional mid-cycle note only if budgets demand it
Week 3	Draft narrative from trends; pull PDF / share link	Pull weekly org PDF(s) or Preview; keep Step 3 narrative yours	Internal review with account lead
Week 4	Send branded report; book 20–30 minute review	Attach weekly PDF(s) under white-label when the plan includes it	Upsell or next-month plan in writing

Release-heavy clients often need denser mid-cycle notes. The calendar is the product. White-label branding is how that calendar looks when it leaves your building.

FAQ

Is this a generic agency workflow or an Apogee Watcher guide?
Both, on purpose. Steps 1–3, Step 5, and the calendar’s left columns describe a monthly white-label CWV retainer any agency can run. Step 4’s Watcher subsection, the Watcher calendar column, and the branded-PDF FAQ answer what Watcher generates today (weekly organisation reports and branding) versus what is still reserved.

What belongs in white-label Core Web Vitals reports each month?
Status versus budgets, labelled lab versus field trends, top issues with owners, work completed, and next-period plan. Raw Lighthouse dumps belong in an appendix, not in the executive story. The client-ready outline is a reliable skeleton and does not depend on a specific vendor.

How is a monthly performance report retainer different from a one-off audit?
A retainer assumes continuous scheduled evidence and a recurring narrative. A one-off audit is a point-in-time baseline. Retainers without schedules tend to recreate the screenshot problem every month.

Can we send a client-ready PageSpeed PDF under our brand in Apogee Watcher today?
Yes. On Watcher plans with PDF and white-label features (typically Professional+), set logo, colour, and font on the organisation, then download the weekly organisation PDF (or regenerate after branding changes). A self-serve monthly organisation report type is still reserved; most retainers pair weekly PDFs with a short month-end narrative you write. Pricing and My Account show the current flags before contracts. Agencies not on Watcher still use the branded delivery options table in Step 4.

Do white-label PageSpeed reports replace Search Console?
No. Search Console remains the field and indexing source of truth for many SEO conversations. Watcher (and other lab monitors) organise PageSpeed Insights-style history across the portfolio. Both layers usually sit side by side.

Should every retainer include prospecting reports?
Only when prospecting is in scope. Monitoring retainers and pipeline work share scheduled evidence but different commercial promises. On Watcher, leads RBAC expectations stay accurate until org-scoped access ships.

Where the next retainer cycle usually starts

Agencies that harden this workflow often pick one client first, lock URLs and budgets early in the week, and let schedules run before anyone drafts prose. The narrative then comes from trends, not from a fresh panic test, and the branded PDF or share link matches what your tools (and plan) actually support. The review lands on the calendar before month end.

When that scheduled evidence needs to span many organisations without per-site tool sprawl, a useful next step is to start a Watcher trial or review features and pricing, pair this workflow with the white-label overview, and use the weekly organisation reports ship note when briefing account leads on what is live versus reserved.

References

Weekly Organisation Reports and White-Label Branding Options Are Live (Apogee Watcher)
Organisation reports and PDF (Apogee Watcher docs)
White-Label Performance Reports: What They Are and Why Agencies Need Them (Apogee Watcher)
Client-Ready Core Web Vitals Report Outline (Apogee Watcher)
How to Sell Performance Monitoring Services to Your Clients (Apogee Watcher)
From Monitoring to Pipeline: Why PageSpeed Data Works for Agency Prospecting (Apogee Watcher)
The PageSpeed Prospecting Workflow: Analyze, Report, Qualify, and Reach Out (Apogee Watcher)
Attention-Free Score: How Domain Reports Show Which Pages Need Work (Apogee Watcher)
PageSpeed Monitoring: How to Schedule Test Frequency and Priority Across Your Portfolio (Apogee Watcher)
Performance Budget Thresholds Template (Apogee Watcher)
3 Agency PageSpeed Stacks for 2026 (Apogee Watcher)
White-label reports (Apogee Watcher docs)
Understanding Core Web Vitals and Google search results (Google Search Central)
About PageSpeed Insights (Google)

Originally published on Apogee Watcher.

Coder Legion - Recent posts tagged client-reports

Site-Level Guidance: AI Actionable Insights Leave Beta

What site-level AI insights do with PageSpeed evidence

How AI insights sit next to the domain report Summary

Where to generate AI insights in Watcher

AI insights quota and which plans include them

Updated site view: tests, pages, discovery, and reports together

What AI insights do not claim

FAQ

Do I need AI insights to use domain reports?

Can clients generate insights from a public share link?

Is this the same as pasting PageSpeed Insights into ChatGPT?

Will AI insights appear on weekly organisation PDFs?

What should I do after I apply a recommended fix?

References

TTFB Is Not Only the Server: The Unattributed Slice Agencies Should Name in Reports

What unattributed navigation overhead (UNO) is

Navigation Timing TTFB breakdown: redirect, DNS, connection, request

Why redirect, DNS, and connection phases still leave a gap

How to calculate UNO from Navigation Timing

What agencies should name in client reports when TTFB looks “server-only”

When the attributed server phase is the real bottleneck

Why CrUX and one-off lab runs miss the unattributed slice

FAQ

References

Weekly Organisation Reports and White-Label Branding Options Are Live

What weekly organisation reports include

White-label branding options for agency PDFs

How to preview, download, and regenerate a weekly pack

What is live versus still reserved

How this changes the monthly retainer pack

FAQ

Try it on one organisation first

References

From Scheduled Tests to White-Label CWV Reports: A Monthly Retainer Workflow

Why the monthly CWV report usually fails

Step 1: Scheduled PageSpeed tests as the evidence base

Step 2: Performance budgets before the monthly story

Step 3: The monthly narrative (not a metric dump)

Step 4: Branded PDF or share link

How any agency can brand and send the report

Which Apogee Watcher report features are live today

Step 5: Retainer upsell (and optional prospecting)

A one-month operating calendar

FAQ

Where the next retainer cycle usually starts

References