Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize playgramlandingpage.git.feat.blog.page.playgram.vercel.app
Oversized images waste 45 KiB and slow down page load with poor user experience.
Resize images to match display dimensions (104x104px instead of 512x512px). Implement Next.js Image component with responsive sizes. Set proper cache headers for S3 images (Cache-Control: max-age=31536000) to enable browser caching.
A score of 33 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This website has severe performance issues with a critically low score of 33/100, taking over 18 seconds to become fully interactive. The biggest problem is excessive JavaScript from reCAPTCHA and other scripts, which is blocking the page from rendering and consuming over 821 KB of unused code that delays content loading by nearly 4 seconds. The site also suffers from oversized images (particularly profile photos that are 5x larger than needed), poor caching policies, and render-blocking CSS files. Immediate fixes should focus on removing or deferring unnecessary JavaScript, properly sizing images, and implementing efficient caching to dramatically improve the user experience.
Why It Matters:
821 KiB of unused JavaScript is blocking render for 3.75 seconds and severely impacting LCP.
How to Fix:
Defer reCAPTCHA loading until user interaction using dynamic imports. Split large bundles using Next.js dynamic imports for non-critical components. Remove duplicate reCAPTCHA script references and audit other third-party scripts for necessity.
Why It Matters:
CSS files are blocking initial render and delaying both LCP and FCP by 150ms.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Use Next.js font optimization to preload fonts. Defer non-critical CSS using media='print' onload='this.media="all"' technique for below-fold styles.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
CSS files are blocking initial render and delaying both LCP and FCP by 150ms.
Profile images are 5x larger than needed (512x512 vs 104x104 display), wasting 77 KiB unnecessarily.
821 KiB of unused JavaScript is blocking render for 3.75 seconds and severely impacting LCP.
Render-blocking CSS delays LCP and FCP by 900ms, preventing users from seeing content quickly.