Repository navigation
Finish bounded homepage rendering and deployment integrity checks - #109
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The low-end mobile retest still showed costly decorative rendering. Keep the same animation and colors with a smaller artwork buffer, while retaining full-resolution HTML text and controls. The existing slow-frame adjustment remains bounded and keeps the animation running. Browser review confirmed the background still renders and animates.
The new production integrity check also needs to compare the component’s actual served HTML: the Worker deliberately adds the shared analytics and newsletter scripts to its head. Include that exact transformation in the expected bytes rather than weakening or skipping the hash comparison. The repaired verifier passed against the already deployed version before this rendering-budget change.
Validation: all 139 website tests, public-release validation and Gitleaks passed. No iOS code changed; the completed generic iOS build and diagnostics host checks remain applicable. The normal deployment workflow must pass all content, resource, crawler and document checks, followed by a fresh mobile performance report.
Published as a2736b0. Deploy website passed: 337 live pages, 347 resources, 233 public documents, no page/resource or duplicate-sitemap issues. The exact served renderer/component/poster checks passed. The final mobile PageSpeed report measured performance 80, LCP 3.8s, TBT 40ms and CLS 0. These are lab measurements; field data remains unavailable.