perf: Inline CSS, remove polyfills, optimize chunks & FM imports#107
Merged
vibemarketerpromax merged 1 commit intomainfrom Feb 19, 2026
Merged
perf: Inline CSS, remove polyfills, optimize chunks & FM imports#107vibemarketerpromax merged 1 commit intomainfrom
vibemarketerpromax merged 1 commit intomainfrom
Conversation
- Replace optimizeCss (no-op) with inlineCss to eliminate render-blocking CSS - Alias Next.js hardcoded polyfill-module to false (saves ~14-20 KiB) - Bump Safari target 16.4→17 so all polyfilled features are natively supported - Fix splitChunks to merge with Next.js defaults instead of replacing them - Lower maxSize 244KB→128KB for more aggressive chunk splitting - Remove catch-all vendor cacheGroup that absorbed modules Next.js splits better - Convert all 17 expertise components from full motion to lightweight m (they render inside LazyMotion context, so m works identically)
Deploying website with
|
| Latest commit: |
55887dc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0d55bf76.website-yiq.pages.dev |
| Branch Preview URL: | https://perf-lighthouse-optimization-xion.website-yiq.pages.dev |
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
experimental.inlineCss: true): Eliminates the 21.4 KiB render-blocking CSS request (est 620ms savings). The previousoptimizeCsswas a no-op (requirescritterspackage + Pages Router only).polyfill-modulebundle (Array.at, Array.flat, Object.fromEntries, Object.hasOwn, etc.) — all natively supported by our browser targets. Saves ~14-20 KiB.URL.canParseis natively available, making full polyfill removal safe. Safari 17 released Sept 2023.vendorgroup that was absorbing modules Next.js would split more granularly. LowersmaxSizefrom 244KB to 128KB for more aggressive splitting on mobile.components/expertise/*.tsxfiles converted from fullmotionto lightweightm(they render insideLazyMotioncontext). Reduces per-chunk FM overhead.Expected impact
motionbundlemproxyTest plan
/technologies/react— check LCP, TBT improvements🤖 Generated with Claude Code