LCP
Largest Contentful Paint
7.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Responsive Image Optimization
How to optimize staging.modelia.ai
Implement Responsive Image Optimization
Medium Impact+8 points estimated
Why It Matters
Oversized images waste 57 KiB and delay LCP by 250ms with unnecessary downloads.
How to Fix
Add responsive srcset attributes to all images using React components. Configure proper image sizes: author profile (64x64 instead of 600x600), main article image (676x393 instead of 1516x880). Use Next.js Image component or react-image-gallery with automatic WebP conversion and size optimization.
0Poor
What This Score Means
A score of 38 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
537ms
Poor
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 React site has poor performance with a score of 38/100, indicating serious speed issues that will frustrate users. The biggest problem is excessive unused JavaScript code (440 KiB), particularly from a main chunk file that's 80% unused, which is delaying your page's first visual content by over 1.8 seconds. The site also suffers from render-blocking CSS files and oversized images that could be easily optimized. Removing unused JavaScript, implementing code splitting, and properly sizing images could improve your performance score by 30+ points and dramatically reduce the current 7.8-second loading time.
Other Optimization Recommendations
Eliminate Unused JavaScript Bundle Splitting
High Impact+25 points estimatedWhy It Matters:
Unused JavaScript accounts for 440 KiB wasted bytes and delays LCP by 1.85 seconds.
How to Fix:
Implement React code splitting using React.lazy() and Suspense for route-based chunks. Configure Webpack/Vite bundle analyzer to identify unused code in chunk-ZmQTtvHt.js (79% unused). Remove or defer Google Tag Manager and Analytics until after page interactive using useEffect with setTimeout.
Optimize Critical Resource Loading
High Impact+18 points estimatedWhy It Matters:
Render-blocking CSS and slow resource discovery delay FCP by 1.35 seconds and hurt LCP.
How to Fix:
Inline critical CSS for above-the-fold content directly in HTML head. Use React Helmet or Next.js Head to add fetchpriority='high' to the LCP image. Implement CSS code splitting to load only necessary styles per route. Remove 100% unused CSS from CT0VcnK1.css (22 KiB wasted).
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 Performance Analyses
React Performance Resources
Optimize Critical Resource Loading
Render-blocking CSS and slow resource discovery delay FCP by 1.35 seconds and hurt LCP.
Eliminate Unused JavaScript Bundle Splitting
Unused JavaScript accounts for 440 KiB wasted bytes and delays LCP by 1.85 seconds.
Implement Modern Image Delivery
Large unoptimized images delay LCP and waste 84KB of bandwidth on every page load.
Optimize Main Thread Processing
32 seconds of main thread work creates 10.4 seconds of Total Blocking Time, preventing user interactions.