LCP
Largest Contentful Paint
5.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Update JavaScript Build Target
How to optimize kejoola.com
Update JavaScript Build Target
Medium Impact+8 points estimated
Why It Matters
36 KiB of legacy polyfills are unnecessarily delaying LCP by 150ms for modern browsers.
How to Fix
Update your Next.js target in next.config.js to 'es2020' or higher to remove unnecessary polyfills. Configure Babel to exclude modern JavaScript features from transpilation. Set browserslist to exclude IE and older browsers if not needed.
0Needs Improvement
What This Score Means
A score of 73 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
199ms
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 site has moderate performance issues with a score of 73/100. The biggest problem is the slow Largest Contentful Paint at 5.0 seconds, which is primarily caused by 191 KiB of unused JavaScript that's blocking the page load for 600ms. The site is shipping outdated JavaScript code (with potential savings of 36 KiB) and has render-blocking CSS files that delay initial page rendering. Removing unused JavaScript, updating the build process to avoid legacy polyfills for modern browsers, and optimizing CSS delivery could significantly improve load times and boost the performance score by 15-20 points.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
191 KiB of unused JavaScript is delaying LCP by 600ms and blocking critical rendering.
How to Fix:
Configure Next.js bundle analyzer to identify unused code in your chunks. Remove or lazy-load PostHog recorder features not immediately needed. Use dynamic imports for heavy components that aren't above-the-fold. Enable tree-shaking in your Next.js build configuration.
Optimize CSS Delivery Strategy
Medium Impact+7 points estimatedWhy It Matters:
Render-blocking CSS files are creating a 1.2-second delay before content can be painted.
How to Fix:
Implement critical CSS inlining in your Next.js _document.js for above-the-fold styles. Use next/dynamic with ssr: false for non-critical components. Split large CSS chunks using Next.js CSS modules to reduce the main bundle size.
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
Modernize JavaScript Build Target
Your bundle includes 13KB of unnecessary polyfills for modern browser features, adding extra parsing and execution overhead.
Optimize LCP Image Loading
Your LCP image has a 1.7-second resource load delay and 979ms render delay, contributing to a poor 6.2-second LCP score.
Reduce JavaScript Execution Time
JavaScript execution takes 2.3 seconds and blocks the main thread for 1.3 seconds, severely impacting Total Blocking Time and user interactivity.
Optimize CSS Delivery Strategy
Render-blocking CSS files are creating a 1.2-second delay before content can be painted.