LCP
Largest Contentful Paint
29.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Loading
How to optimize convivial.operation.061829.framer.app
Optimize LCP Image Loading
High Impact+15 points estimated
Why It Matters
The LCP image takes 6 seconds to load due to resource load delay and lacks proper optimization.
How to Fix
Add fetchpriority='high' to your hero image element. Ensure the LCP image URL is discoverable in the initial HTML document rather than loaded by JavaScript. Compress the 604KB hero image using modern formats like WebP or AVIF.
0Poor
What This Score Means
A score of 48 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
692ms
Poor
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 48/100, primarily due to massive JavaScript bloat and inefficient resource loading. The biggest problem is an extremely slow Largest Contentful Paint of 29.8 seconds, caused by unused JavaScript that could save 2,319 KiB and a complex network dependency chain that delays critical resources by over 4 seconds. The site is loading excessive amounts of unused code from the Framer framework, with over 90% of some JavaScript files going unused, while also serving oversized images that waste an additional 502 KiB. Reducing unused JavaScript, optimizing images, and implementing better caching strategies could potentially improve the performance score by 30+ points and dramatically reduce load times.
Other Optimization Recommendations
Eliminate Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
Unused JavaScript is wasting 2.3MB and delaying LCP by 13.4 seconds, severely impacting performance.
How to Fix:
Review Framer components and remove unused features from app.framerstatic.com chunks. Enable tree-shaking in your build process. Split large JavaScript bundles into smaller, page-specific chunks that load only when needed.
Implement Preconnect for Critical Origins
Medium Impact+8 points estimatedWhy It Matters:
Missing preconnect hints to Framer's CDN and Sentry are adding 626ms of connection overhead.
How to Fix:
Add <link rel='preconnect' href='https://site-6aea31f2ed69a25c8aad5030b6529bf22b3dcba8b4b66aab542576566b.framercanvas.com'> to your document head. Include preconnect for https://o20425.ingest.sentry.io as well. Limit total preconnect hints to 4 or fewer for optimal performance.
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.