Skip to content
This repository was archived by the owner on Sep 28, 2026. It is now read-only.

docs(evidence): close out render-blocking finding b8f6046e942a (already fixed in #20/#23, re-verified on current main + live) #35

Merged
nish3451 merged 1 commit into from
Aug 9, 2026
Merged

docs(evidence): close out render-blocking finding b8f6046e942a (already fixed in #20/#23, re-verified on current main + live) #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions docs/evidence/render-blocking-fonts-2026-08-08.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,3 +140,36 @@ non-blocking on all six live pages, first paint does not wait for it, and fonts
still load and apply under the production CSP. This closes dogfood finding
b8f6046e942a ("Render-blocking resources on home") against the deployed site;
the code-side fix and the CI enforcement were already merged as PRs #20 and #23.

### Closeout re-verification (added 2026-08-09)

Re-verified against the current origin/main head (a163327, "seo: add canonical
URLs to the five public pages", merged 2026-08-09) after the subsequent page
edits (heading hierarchy, apple-touch icon, schema.org, meta descriptions,
canonical URLs, internal-link cleanup, App Store citation) — none of which was
allowed to regress the guarantee. Two fresh measurements:

1. `npm run check:render-blocking` on the current working tree (real Chromium,
production CSP, css2 intercepted and delayed 2500ms, stubbed response): all
six pages PASS — css2 non-blocking, first-contentful-paint never waits for it
(homepage 320ms, audit 84ms, desk 56ms, pricing 52ms, specimen 72ms,
brief-requested 68ms), no render-blocking resources other than the site's
own same-origin stylesheets, promoted sheet applied.
Comment on lines +152 to +157

@coderabbitai coderabbitai Bot Aug 9, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Use the correct page name in the PASS summary.

The summary labels the third page as desk, but the documented six-page scope and live results use agents.html. This makes the 56ms FCP value ambiguous. Replace desk with agents, or state that desk is the display name for agents.html.

Proposed fix 
-   (homepage 320ms, audit 84ms, desk 56ms, pricing 52ms,
+   (homepage 320ms, audit 84ms, agents 56ms, pricing 52ms,
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
1. `npm run check:render-blocking` on the current working tree (real Chromium,
production CSP, css2 intercepted and delayed 2500ms, stubbed response): all
six pages PASS — css2 non-blocking, first-contentful-paint never waits for it
(homepage 320ms, audit 84ms, desk 56ms, pricing 52ms, specimen 72ms,
brief-requested 68ms), no render-blocking resources other than the site's
own same-origin stylesheets, promoted sheet applied.
1. `npm run check:render-blocking` on the current working tree (real Chromium,
production CSP, css2 intercepted and delayed 2500ms, stubbed response): all
six pages PASS — css2 non-blocking, first-contentful-paint never waits for it
(homepage 320ms, audit 84ms, agents 56ms, pricing 52ms, specimen 72ms,
brief-requested 68ms), no render-blocking resources other than the site's
own same-origin stylesheets, promoted sheet applied.
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/evidence/render-blocking-fonts-2026-08-08.md` around lines 152 - 157,
Update the six-page PASS summary to label the third page as agents, matching the
documented agents.html scope and live results; alternatively clarify that desk
is the display name for agents.html while preserving the 56ms FCP value.


2. Live re-measurement of the deployed pages in real Chromium (unthrottled):

| Page | css2 renderBlockingStatus | FCP (ms) | css2 responseEnd (ms) | Render-blocking resources | Fonts load (Karla / Fraunces) | Promoted sheet applied |
|---|---|---|---|---|---|---|
| index.html (home) | non-blocking | 692 | 491 | same-origin index.css only | yes / yes | yes |
| audit.html | non-blocking | 432 | 199 | same-origin audit.css, shared.css | yes / yes | yes |
| agents.html | non-blocking | 356 | 142 | same-origin shared.css, agents.css | yes / yes | yes |
| pricing.html | non-blocking | 360 | 139 | same-origin shared.css, pricing.css | yes / yes | yes |
| specimen.html | non-blocking | 340 | 156 | same-origin shared.css, specimen.css | yes / yes | yes |
| brief-requested.html | non-blocking | 300 | 130 | same-origin shared.css, brief-requested.css | yes / yes | yes |

Same result as the earlier verification passes: no render-blocking scripts, no
render-blocking external resources, first paint never waits for the font
stylesheet, fonts still load and apply. Finding b8f6046e942a ("Render-blocking
resources on home") remains closed on the code side (PRs #20 and #23), in CI
(`npm run check:render-blocking`), and against the deployed site; this lane
(2026-08-09) re-confirmed all three and found nothing further to change.
Loading