Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize v3.staging.nuitee.link
Layout shifts of 0.182 occur primarily from hotels list loading dynamically, hurting user experience.
Reserve space for the hotels list container using CSS min-height before content loads. Add explicit width and height dimensions to the logo image in the header. Implement skeleton screens or placeholders for dynamically loaded hotel cards to prevent content jumping.
A score of 31 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This website has severe performance issues with a score of only 31/100, indicating critical problems that significantly impact user experience. The biggest issue is extremely slow loading times - it takes over 26 seconds for the page to become interactive and 13 seconds for the largest content to appear, which is far beyond acceptable standards. The primary culprits are inefficient caching (wasting 3.2MB of data on repeat visits), oversized JavaScript files (5.7MB total), and unoptimized images that could be 184KB smaller with modern formats like WebP. Implementing proper cache headers, reducing JavaScript bundle sizes, and optimizing images could dramatically improve performance and potentially double the current score.
Why It Matters:
Poor cache lifetimes waste 3,258 KiB on repeat visits and delay LCP by 5.1 seconds.
How to Fix:
Configure your web server to set cache headers for static assets to at least 1 year (31536000 seconds). Set main JavaScript bundle cache to 1 year with versioned filenames. Configure image assets from static.cupid.travel to cache for at least 30 days instead of current 1 hour.
Why It Matters:
The 1.77MB main JavaScript bundle blocks rendering and causes 1.4 seconds of execution delay.
How to Fix:
Implement code splitting to break the large main bundle into smaller chunks loaded on demand. Remove unused JavaScript (412 KiB identified) through tree shaking and audit. Use dynamic imports for non-critical features and defer third-party scripts like Google Tag Manager until after page load.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Short 4-hour cache lifetime wastes 217 KiB on repeat visits, slowing LCP by 1050ms.
JavaScript is causing 34ms of forced reflows in main-website-41slwGrA.js, blocking user interactions.
77 KiB of unused JavaScript is delaying LCP by 300ms and blocking the main thread.
No cache headers are set for critical assets totaling 1.35MB, forcing full downloads on every visit.