LCP
Largest Contentful Paint
10.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Above-fold Video Loading
How to optimize codeart.mk
Optimize Above-fold Video Loading
High Impact+18 points estimated
Why It Matters
The LCP video has 4.7 seconds of element render delay and lacks fetchpriority optimization.
How to Fix
Add fetchpriority='high' to the video element that serves as LCP. Preload the video poster image using <link rel='preload' as='image' href='/images/video-placeholder.webp'>. Consider using a lighter video format or optimized poster image for faster initial render.
0Needs Improvement
What This Score Means
A score of 56 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
103ms
Good
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 Next.js website has poor performance with a score of 56/100, indicating significant user experience issues. The biggest problem is excessive JavaScript execution taking over 3 seconds, which is blocking the main thread and preventing user interactions - your page doesn't become interactive until 10.6 seconds, which is extremely slow. The site is also serving an unnecessarily large 12MB video file and oversized images that aren't properly optimized for mobile devices. Reducing JavaScript bundle sizes, optimizing the video file, and implementing responsive images could improve your score by 30+ points and dramatically speed up load times for your users.
Other Optimization Recommendations
Reduce JavaScript Bundle Size
High Impact+15 points estimatedWhy It Matters:
182 KiB of unused JavaScript is delaying LCP by 950ms and blocking main thread for 1.6 seconds.
How to Fix:
Enable Next.js code splitting by using dynamic imports for non-critical components. Remove unused polyfills by updating your Babel config to target modern browsers only. Defer third-party scripts (Facebook Pixel, Google Analytics) using Next.js Script component with strategy='afterInteractive'.
Implement Proper Image Optimization
Medium Impact+8 points estimatedWhy It Matters:
Images are oversized by 131 KiB and missing responsive optimization, impacting LCP by 200ms.
How to Fix:
Configure Next.js Image component with proper responsive breakpoints matching your CSS. Use quality={75} instead of quality={100} for blog images. Add sizes='(max-width: 575px) 545px, (max-width: 992px) 975px, 100vw' with correct breakpoint values that match your actual layout.
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 Next.js Speed Tests
Next.js Performance Resources
Optimize Font Loading Strategy
Font display issues cause 30ms delay to First Contentful Paint and contribute to layout shifts during text rendering.
Fix Hero Section Layout Shifts
The main hero section causes 0.288 CLS score due to content shifting during load, representing 95% of total layout shift issues.
Reduce JavaScript Bundle Size
399 KiB of unused JavaScript and 3.3s of main thread blocking time severely impact Time to Interactive (19.9s) and user experience.
Fix Layout Shifts from Images
Unsized images are causing 0.258 CLS score, making content jump and hurting user experience.