LCP
Largest Contentful Paint
9.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused CSS and JavaScript
How to optimize hexbytes.in
Reduce Unused CSS and JavaScript
High Impact+18 points estimated
Why It Matters
94% of your CSS (107KB) and 198KB of JavaScript are unused, causing 1.2 second delay in FCP and LCP.
How to Fix
Use Next.js dynamic imports to code-split unused page components like about-43053e657f5c6c8c.js. Remove unused Tailwind CSS classes with PurgeCSS configuration in next.config.js. Defer third-party scripts like Google Analytics and Facebook Pixel until after page load.
0Poor
What This Score Means
A score of 37 falls in the "Poor" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.
This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.
Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.
Core Web Vitals Analysis
INP
Interaction to Next Paint
386ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js/React site has poor performance with a score of 37/100, indicating significant user experience issues. The biggest problem is massive image optimization failures - three testimonial images are consuming over 4MB while displaying at tiny 140x80 pixel sizes, creating enormous waste and severely impacting load times. Your Largest Contentful Paint takes a painful 9.5 seconds, and users can't interact with the page for over 14 seconds due to excessive JavaScript blocking the main thread. Converting images to modern formats (WebP/AVIF), properly sizing them for display dimensions, and reducing unused JavaScript could easily improve your score by 30+ points and dramatically speed up the site.
Other Optimization Recommendations
Fix Redirect and Optimize Images
High Impact+25 points estimatedWhy It Matters:
The redirect from hexbytes.in to www.hexbytes.in delays LCP by 800ms, while oversized testimonial images waste 4MB of bandwidth.
How to Fix:
Update all internal links to use https://www.hexbytes.in directly to eliminate the redirect. Convert testimonial images to WebP format and resize from 800x800 to 140x140 using Next.js Image component with proper width/height props. Add fetchpriority='high' to the LCP image.
Optimize JavaScript Build Configuration
Medium Impact+12 points estimatedWhy It Matters:
Legacy JavaScript polyfills and forced reflows block the main thread for 435ms, degrading user interaction responsiveness.
How to Fix:
Update Next.js target to 'es2020' in next.config.js to remove unnecessary polyfills for modern browsers. Optimize React components causing forced reflows by batching DOM reads/writes and using CSS transforms instead of layout-triggering properties. Consider removing Facebook Pixel or loading it asynchronously.
Keep Your Site Fast After Optimization
Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Next.js Speed Tests
Next.js Performance Resources
Reduce JavaScript Bundle Size
1.3MB of unused JavaScript blocks the main thread for 1.7 seconds, preventing user interactions.
Fix Image Layout Shifts
Unsized images cause 0.295 CLS score, creating jarring content jumps that harm user experience.
Eliminate Render Blocking CSS
CSS files are blocking initial page render for 750ms, significantly delaying LCP and FCP.
Optimize JavaScript Build Configuration
Legacy JavaScript polyfills and forced reflows block the main thread for 435ms, degrading user interaction responsiveness.