LCP
Largest Contentful Paint
9.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Font Display Optimization
How to optimize kfc.com.np
Implement Font Display Optimization
Medium Impact+8 points estimated
Why It Matters
Custom fonts block text rendering for 1.6 seconds causing invisible text during page load.
How to Fix
Add font-display: swap to @font-face declarations for National2 fonts. Preload critical font files in Next.js Head component. Consider using next/font for automatic font optimization with fallback fonts.
0Poor
What This Score Means
A score of 44 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
130ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.43
Poor
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js/React KFC Nepal website has poor performance with a score of 44/100. The biggest problem is massive layout shifts (CLS of 0.428) caused by images loading without proper size dimensions, making the page content jump around as it loads. Additionally, the site suffers from an extremely slow Largest Contentful Paint of 9.7 seconds due to oversized images and render-blocking CSS files. Fixing image dimensions, optimizing image delivery (which could save 433 KiB), and addressing the render-blocking resources could improve the score by 30+ points and dramatically enhance user experience.
Other Optimization Recommendations
Fix Unsized Image Layout Shifts
High Impact+25 points estimatedWhy It Matters:
Unsized images cause 0.428 CLS score with major layout shifts affecting user experience.
How to Fix:
Add explicit width/height attributes to all Next.js Image components. Remove loading='lazy' from above-the-fold images like the hero banner. Set proper aspect ratios in CSS to reserve space before images load.
Optimize Hero Image Loading
High Impact+20 points estimatedWhy It Matters:
LCP image takes 9.7 seconds to load due to lazy loading and oversized dimensions.
How to Fix:
Remove loading='lazy' from the hero banner image. Add fetchpriority='high' to the Next.js Image component. Resize the 1920x800 image to match actual display size of 412x172 on mobile to reduce file size by 161KB.
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 Hero Image Loading
LCP image takes 9.7 seconds to load due to lazy loading and oversized dimensions.
Fix Unsized Image Layout Shifts
Unsized images cause 0.428 CLS score with major layout shifts affecting user experience.
Remove Unused JavaScript Code
114 KiB of unused JavaScript is increasing bundle size and delaying LCP by 300ms.
Eliminate Render-Blocking Resources
CSS and JavaScript files are blocking initial render, delaying LCP by 900ms and preventing fast page loads.