LCP
Largest Contentful Paint
19.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Bundle
How to optimize natum.framer.website
Reduce Unused JavaScript Bundle
High Impact+15 points estimated
Why It Matters
121KB of unused JavaScript delays LCP by 600ms and blocks page interactivity for over 20 seconds.
How to Fix
Review Framer components and remove unused interactions or animations. Split large components into smaller, lazily-loaded modules. Use Framer's code splitting features to defer non-critical JavaScript until needed. Consider removing complex motion libraries if animations aren't essential.
0Needs Improvement
What This Score Means
A score of 62 falls in the "Needs Improvement" 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
67ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.02
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website has poor performance with a score of 62/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 19.2 seconds, caused primarily by oversized and unoptimized images that waste 698 KB of bandwidth - images are being served at much higher resolutions than needed for their display size. Additionally, the site is loading 118 KB of unused JavaScript code that could be removed or deferred to speed up initial page loading. Optimizing image sizes and compression, along with cleaning up unnecessary JavaScript, could dramatically improve loading times and boost the performance score by 30+ points.
Other Optimization Recommendations
Optimize Image Delivery and Compression
High Impact+18 points estimatedWhy It Matters:
Images waste 698 KiB and delay LCP by 300ms, with the hero image alone being 479KB oversized.
How to Fix:
In Framer, replace PNG images with WebP format for 60-80% size reduction. Use Framer's responsive image settings to serve appropriately sized images (the hero image is 943x975 but displays at 296x306). Enable automatic compression in Framer's image optimization settings.
Add Priority Hints to LCP Image
Medium Impact+8 points estimatedWhy It Matters:
The LCP image lacks fetchpriority=high, missing an opportunity to load the critical content faster.
How to Fix:
In Framer, select the hero image and add fetchpriority='high' attribute through the custom attributes panel. Ensure the LCP image is not lazy-loaded by disabling any lazy loading settings. Consider adding a preload link tag for the hero image in the site's head section.
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 Generic Speed Tests
Generic Performance Resources
Fix Layout Shifts from Images
Unsized images cause 0.13 CLS score with layout shifts primarily from the logo and hero image lacking explicit dimensions.
Remove Unused JavaScript Resources
732 KiB of unused JavaScript delays LCP by 3.6 seconds, with block-editor and components scripts being 80%+ unused.
Optimize Image Delivery and Size
The 1.4MB hero image causes 5.1 second resource load delay and significantly impacts LCP by appearing oversized at 6000x4000 for 570x380 display.
Reduce Render-Blocking Resources
CSS and JavaScript files are blocking initial page render for 3,090ms, significantly delaying First Contentful Paint.