perf: trim excess preconnect hints after mobile PSI re-check#78
Merged
Conversation
PSI flagged >4 preconnect hints after the earlier preload+swap change made the jsdelivr/cdnjs preconnects redundant (those origins are already deferred, so pre-warming the connection buys little). Down to the two Google Fonts origins that still matter. Also files issue 02: post-fix mobile PSI (Performance 52) shows FCP/LCP now bottlenecked on JS boot time (SPA has no SSR), not render-blocking CSS anymore -- that's an architectural change, not a markup patch. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Small follow-up after PR #74 (already merged) landed and a fresh mobile PageSpeed Insights run was taken against production:
cdn.jsdelivr.net/cdnjs.cloudflare.compreconnect hints — PSI flagged ">4 preconnect hints" as excessive; those two origins are already loaded via preload+swap (non-blocking) so pre-warming the connection buys little now. Keeps the two Google Fonts preconnects, which still matter..scratch/perf-third-party-images/issues/*.mdfollow-up docs to their new GitHub issues (Optimize/proxy oversized third-party event thumbnail images #76, Mobile FCP/LCP stuck ~5s: SPA has no SSR, blank until JS boots #77) filed for the remaining, out-of-scope-for-a-patch performance work (oversized third-party event images, and the SPA/no-SSR mobile FCP bottleneck).Post-#74, mobile PSI: Performance 52, FCP 4.9s, LCP 5.0s, CLS 0.364 (up from 39/11.8s/0.645 pre-fix). Desktop: 80 (up from 66). The remaining mobile gap is JS-boot-bound (see #77), not something addressed here.
Test plan
npm run buildsucceedsindex.htmlonly has the two Google Fonts preconnects left🤖 Generated with Claude Code