LCP
Largest Contentful Paint
8.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Unused JavaScript Bundles
How to optimize asi.reisen.de
Next.js SiteScore: 42/100Analyzed January 2026
Eliminate Unused JavaScript Bundles
High Impact+25 points estimated
Why It Matters
265 KiB of unused JavaScript is delaying LCP by 1.15 seconds and blocking user interactions.
How to Fix
Use Next.js dynamic imports with code splitting for large components. Remove unused third-party scripts like PushPanda (70KB unused). Implement tree shaking in your webpack config and audit GTM tags to load only essential tracking scripts.
0Poor
What This Score Means
A score of 42 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
149ms
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 travel website has poor performance with a concerning score of 42/100. The biggest problem is excessive unused JavaScript, wasting 265 KiB from scripts like Google Tag Manager and third-party SDKs, which is severely delaying page interactivity to nearly 12 seconds. The site also suffers from oversized images that are 75 KiB larger than needed and render-blocking CSS files that delay initial paint by 600ms. Removing unused JavaScript, properly sizing images, and optimizing CSS delivery could dramatically improve this score by 30+ points and provide a much faster user experience for potential travelers.
Other Optimization Recommendations
Optimize Responsive Image Sizing
High Impact+15 points estimatedWhy It Matters:
Images are 75 KiB larger than needed for their display dimensions, slowing LCP by 150ms.
How to Fix:
Update Next.js Image component sizes prop to match actual display dimensions (e.g., 451x601 instead of 687x1000). Use responsive breakpoints in your srcSet configuration. Enable automatic format optimization in next.config.js with formats: ['image/webp', 'image/avif'].
Remove Legacy JavaScript Polyfills
Medium Impact+8 points estimatedWhy It Matters:
39 KiB of unnecessary polyfills for modern browsers increase bundle size and execution time.
How to Fix:
Update your Next.js browserslist config to target modern browsers only. Remove polyfills for Array.flat, Object.fromEntries, and String.trim methods which are baseline supported. Configure Babel to skip transpilation for ES2019+ features unless supporting IE11.
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
Update JavaScript Build Configuration
Legacy JavaScript polyfills add 20KB of unnecessary code for modern browsers, slowing LCP by 200ms.
Eliminate Render Blocking CSS
CSS files are blocking first paint, delaying FCP by 300ms and hurting user experience.
Remove Unused JavaScript Code
35% of your JavaScript bundle (24KB) is unused, increasing LCP by 300ms and blocking page interactivity.
Optimize Decorative Images
Oversized garland images waste 1MB of bandwidth without contributing to core functionality.
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