docs(evidence): record live-deployment verification of finding b8f6046e942a - #25
Conversation
…6e942a The render-blocking receipt documented a limitation: the live deployment was never measured. This closes that gap by recording a real-Chromium measurement of the six deployed tinystudio.io pages (2026-08-09): the Google Fonts css2 stylesheet is non-blocking everywhere, first paint does not wait for it, the only render-blocking resources are the site's own same-origin stylesheets, and fonts still load and apply. Dogfood finding b8f6046e942a (render-blocking resources on home) is verified resolved on the deployed site; the code fix and CI enforcement were merged as PRs #20 and #23.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 2 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f1782838d0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| (`scripts/check-render-blocking.mjs`) asserts. No render-blocking scripts and no | ||
| render-blocking external resources were observed, including on the homepage the | ||
| original dogfood run flagged. The Google Fonts css2 stylesheet is fetched | ||
| non-blocking on all six live pages, first paint does not wait for it, and fonts |
There was a problem hiding this comment.
The live run is explicitly unthrottled with no artificial CDN delay, and every row shows FCP occurring after the css2 response ended, so these measurements do not demonstrate that first paint would proceed while css2 remained pending. Under the receipt's own fcp >= css2End timing check, all six rows would be classified as having waited; proving this causal claim requires a delayed live response as in the earlier timing pass, otherwise the claim should be limited to the observed renderBlockingStatus.
Useful? React with 👍 / 👎.
1 participant
What
Closes the documentation gap for dogfood finding
b8f6046e942a("Render-blocking resources on home", audit 20260808T074205Z-msk2fl3n).The code fix and CI enforcement for this finding were already merged (PRs #20 and #23). This PR adds the missing piece the evidence receipt itself flagged as a limitation: the live deployment was never measured. The receipt now records a real-Chromium measurement of the six deployed tinystudio.io pages (2026-08-09) — the Google Fonts css2 stylesheet is non-blocking everywhere, first paint does not wait for it, the only render-blocking resources are the site's own same-origin stylesheets, and fonts still load and apply under the production CSP.
Verification
npm test— pass (15/15) on current main.npm run check:render-blocking— real-Chromium check PASS on all six pages under the production CSP with a 2500ms css2 delay (fcp does not wait for css2; only same-origin stylesheets block; preload promoted to a real stylesheet).renderBlockingStatus: non-blocking, FCP 548ms, render-blocking resources =index.cssonly,sheetApplied: true, Karla/Fraunces load, no console/page errors.Files
docs/evidence/render-blocking-fonts-2026-08-08.md— adds the "Live deployment verification (added 2026-08-09)" section.Closes finding b8f6046e942a against the deployed site.