perf: optimize Lighthouse score to 90+ across Core Web Vitals (LCP, C… - #574
Merged
Merged
Conversation
|
@Unclebaffa Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
ayshadogo
approved these changes
Aug 27, 2026
ayshadogo
left a comment
Contributor
There was a problem hiding this comment.
Please remove the github folder
Contributor
Author
Okay |
…LS, FID, and TBT)
Unclebaffa
force-pushed
the
perf/lighthouse-score
branch
from
August 27, 2026 14:42
eb5441b to
10196ae
Compare
Contributor
Author
Removed |
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.
PR: [Performance] Lighthouse Score Optimization (Target: 90+)
Summary of Changes
This pull request addresses frontend performance bottlenecks affecting Core Web Vitals (Largest Contentful Paint, Cumulative Layout Shift, Total Blocking Time, and First Input Delay/Interaction to Next Paint) to elevate the Lighthouse audit score from ~45 to 90+.
Key Improvements
1. Largest Contentful Paint (LCP)
Interfont loader in app/layout.tsx withdisplay: 'swap',preload: true, andvariable: '--font-inter'.images.unsplash.com).setTimeout 80ms+opacity-0), allowing the primary<h1>headline to paint immediately on SSR and initial load.image/avif,image/webp) withminimumCacheTTL: 60in next.config.js.2. Cumulative Layout Shift (CLS)
CategoriesShowcase,FeaturedArtists,HowItWorks).3. Total Blocking Time (TBT) & FID / INP
next/dynamicto reduce initial JS payload and optimize main thread execution.experimental.optimizePackageImportsin next.config.js for heavy libraries (lucide-react,framer-motion,@reduxjs/toolkit,date-fns).{ passive: true }to window scroll listeners in app/components/layout/Header.tsx to prevent scroll-blocking penalties.4. Accessibility & IDE Code Quality
type="button"attributes across Header.tsx, ExploreProjects.tsx, and artists/[id]/page.tsx.Readonly<Props>to Hero.tsx, ExploreProjects.tsx, RootLayout, and FallbackImage.tsx.getErrorMessage).File Changes Summary
Verification Results
npm run type-checktsc --noEmitexited with code 0 (0 errors)npm run lintnext lintexited with code 0 (0 errors)npm run format:checkprettier --checkverified all matched filesnpm testnpm run buildCloses #530