LCP
Largest Contentful Paint
13.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize hex.tech
Generic SiteScore: 42/100Analyzed January 2026
Remove Unused JavaScript Code
High Impact+10 points estimated
Why It Matters
204KB of unused JavaScript delays page load by 1050ms and wastes bandwidth unnecessarily.
How to Fix
Use webpack-bundle-analyzer to identify unused code in your bundles. Implement code splitting to load only required JavaScript per page. Remove or defer third-party scripts like HubSpot analytics that aren't critical for initial page load. Configure tree-shaking in your build process to eliminate dead code.
0Poor
What This Score Means
A score of 42 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
368ms
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 website has severe performance issues with a score of just 42/100, making it significantly slower than recommended. The biggest problem is extremely slow loading times - it takes 6.8 seconds for users to see any content (First Contentful Paint) and a devastating 13.1 seconds for the main content to fully load (Largest Contentful Paint). The site is bloated with 204 KiB of unused JavaScript code that's unnecessarily slowing down the page, plus an additional 52 KiB of outdated JavaScript polyfills that modern browsers don't need. Removing this excess code, optimizing the large 218 KiB background image, and fixing the render-blocking CSS files could potentially save over 2 seconds of load time and dramatically improve user experience.
Other Optimization Recommendations
Optimize Image Delivery and Compression
High Impact+12 points estimatedWhy It Matters:
The 260KB background texture image severely impacts LCP with an estimated 800ms delay.
How to Fix:
Compress the light-bkg-noise.webp file using tools like Squoosh or ImageOptim to reduce its 216KB waste. Convert the PNG noise texture to WebP format for better compression. Consider using CSS gradients or smaller tiled patterns instead of large background images.
Eliminate Render-Blocking Font Resources
High Impact+15 points estimatedWhy It Matters:
Font CSS files block initial page render for 790ms, severely delaying First Contentful Paint.
How to Fix:
Add preload links for critical fonts in the HTML head: <link rel='preload' href='/fonts/GT-Cinetype-Bold.woff2' as='font' crossorigin>. Inline critical font CSS directly in the HTML. Use font-display: swap for all custom fonts to prevent invisible text during font load.
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Remove Unused JavaScript Code
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
Optimize Video File Caching
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
Defer Render-Blocking JavaScript
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
Remove Unused CSS and JavaScript
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
Frequently Asked Questions
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