LCP
Largest Contentful Paint
18.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Hero Image Delivery
How to optimize europodroze.pl
Next.js SiteScore: 36/100Analyzed February 2026
Optimize Hero Image Delivery
High Impact+18 points estimated
Why It Matters
The LCP hero image is oversized by 306 KiB and has 2.5 seconds of render delay.
How to Fix
Resize hero image to match actual display dimensions (614x247 vs 1008x604). Use Next.js Image component with priority={true} and proper sizes attribute. Increase WebP compression or switch to AVIF format. Preload the hero image in document head.
0Poor
What This Score Means
A score of 36 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
254ms
Needs Improvement
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 severe performance issues with a score of only 36/100. The biggest problem is excessive JavaScript execution taking over 3 seconds, which creates a massive 950ms delay before users can interact with the page and pushes your Largest Contentful Paint to an unacceptable 18.6 seconds. Reducing unused JavaScript (especially the 1,223 KiB of unnecessary code from reCAPTCHA and other libraries), optimizing images to save 306 KiB, and improving your caching strategy could dramatically improve both your Core Web Vitals and user experience. The site is also loading legacy JavaScript polyfills that modern browsers don't need, adding another 53 KiB of waste.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+25 points estimatedWhy It Matters:
Unused JavaScript wastes 1,223 KiB and delays LCP by 3.75 seconds while blocking user interactions.
How to Fix:
Use Next.js bundle analyzer to identify unused code in chunks. Remove duplicate reCAPTCHA instances (366KB each). Implement dynamic imports for non-critical components using Next.js lazy loading. Configure tree-shaking in webpack to eliminate dead code.
Modernize JavaScript Build Target
Medium Impact+8 points estimatedWhy It Matters:
Legacy JavaScript polyfills add 53 KiB of unnecessary code for modern browsers.
How to Fix:
Update Next.js target in next.config.js to 'es2017' or newer. Remove Babel polyfills for Array methods and Object methods that are now baseline. Configure browserslist to exclude Internet Explorer and very old browsers.
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
Eliminate Duplicate JavaScript Modules
175 KiB of duplicated JavaScript from Nike Design System components is loaded multiple times across bundles.
Fix LCP Image Discovery
The LCP image is not discoverable in the initial HTML, causing a 4-second resource load delay.
Remove Unused JavaScript Code
460 KiB of unused JavaScript is blocking the main thread for 7.3 seconds and delaying LCP by 2.4 seconds.
Fix Page Redirects Chain
Multiple redirects add 1.53 seconds delay before the page even starts loading, directly impacting both FCP and LCP.
Frequently Asked Questions
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