Fix hero section performance: eliminate expensive CSS operations and unnecessary re-renders#27
Draft
Fix hero section performance: eliminate expensive CSS operations and unnecessary re-renders#27
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Replace transition-all with specific transition properties to reduce layout/paint recalculations (Hero.js, HeroText.js) - Remove expensive backdrop-blur CSS filters from button container (Hero.js) - Add will-change: transform to InfiniteSlider for GPU-accelerated animation - Memoize HeroText with React.memo to prevent unnecessary re-renders - Debounce window resize handler to prevent rapid cascading state updates (Home.js) - Add explicit duration-200 to transitions that were missing it Co-authored-by: reach2saksham <113931310+reach2saksham@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix performance issues in hero section
Fix hero section performance: eliminate expensive CSS operations and unnecessary re-renders
Feb 26, 2026
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.
Hero section suffers from multiple compounding performance issues:
transition-allon numerous elements,backdrop-blurfilters, un-promoted GPU animations, unmemoized child components, and an un-debounced resize handler.CSS transition specificity
transition-allwith targeted properties (transition-[opacity,filter,transform],transition-transform, etc.) across Hero.js and HeroText.js — avoids the browser monitoring ~50 CSS properties per element per frameRemove
backdrop-blurbackdrop-blurandbackdrop-blur-smfrom the CTA button container — these force per-paint pixel sampling/blurring of underlying contentGPU compositing for InfiniteSlider
willChange: 'transform'to the continuously animated slider element, promoting it to its own compositing layerReact re-render prevention
HeroTextwithReact.memo— no props, so prevents re-renders on every parent state change (e.g., Spline visibility toggling)Debounce resize handler
window.resizelistener in Home.js to prevent rapid cascadingsetIsMobilestate updatesWarning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
fonts.googleapis.com/opt/hostedtoolcache/node/24.13.1/x64/bin/node /opt/hostedtoolcache/node/24.13.1/x64/bin/node /home/REDACTED/work/portfolio/portfolio/portfolio/node_modules/next/dist/compiled/jest-worker/processChild.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.