LCP
Largest Contentful Paint
13.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Render Blocking Resources
How to optimize playgram.ai
Optimize Render Blocking Resources
High Impact+25 points estimated
Why It Matters
Render-blocking CSS delays First Contentful Paint and Largest Contentful Paint by 900ms.
How to Fix
Preload critical fonts by adding <link rel='preload' href='fonts.googleapis.com/css2?family=Inter...' as='style'> to the <head>. Inline critical CSS for above-the-fold content directly in HTML. Defer non-critical CSS using media='print' onload="this.media='all'" technique.
0Poor
What This Score Means
A score of 40 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
176ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.01
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 poor score of 40/100, indicating significant problems that hurt user experience. The biggest issue is extremely slow interactivity - it takes over 16 seconds for the page to become fully interactive, which is far beyond acceptable limits. The main culprits are render-blocking CSS and fonts that delay initial page display by 900ms, excessive JavaScript execution taking 2.4 seconds, and 372KB of unused JavaScript code that's unnecessarily downloaded. Addressing these JavaScript and CSS blocking issues could dramatically improve load times and boost the performance score by 30+ points.
Other Optimization Recommendations
Reduce Unused JavaScript Execution
High Impact+20 points estimatedWhy It Matters:
372 KiB of unused JavaScript increases LCP by 1.65 seconds and blocks main thread for 2.4 seconds.
How to Fix:
Implement code splitting in Next.js using dynamic imports for non-critical components. Remove or defer Google Analytics/GTM scripts until after page load. Tree-shake unused code by auditing bundle analyzer output and removing dead code paths.
Fix CookieYes Forced Reflows
Medium Impact+8 points estimatedWhy It Matters:
CookieYes banner causes 43ms of forced reflows, blocking user interactions and degrading Total Blocking Time.
How to Fix:
Replace synchronous DOM queries in cookie banner with cached measurements. Use CSS transforms instead of changing layout properties. Consider switching to a more performant cookie consent solution or implement custom lightweight banner.
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
Optimize Image Delivery
Oversized images waste 45 KiB and slow down page load with poor user experience.
Eliminate Render-Blocking CSS
CSS files are blocking initial render and delaying both LCP and FCP by 150ms.
Optimize Profile Images Loading
Profile images are 5x larger than needed (512x512 vs 104x104 display), wasting 77 KiB unnecessarily.
Remove Unused JavaScript Code
821 KiB of unused JavaScript is blocking render for 3.75 seconds and severely impacting LCP.