Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize ainights.ai
Render-blocking resources delay First Contentful Paint by 1.3 seconds and cause extremely poor LCP of 38.5 seconds.
Implement preconnect hints for fonts.bunny.net and external origins. Inline critical CSS to eliminate render blocking. Defer non-critical JavaScript like CCM19 analytics script using async or defer attributes. Use font-display: swap on custom fonts.
A score of 52 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.
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 problems with a critically low score of 52/100, indicating a poor user experience. The biggest issue is an extremely slow Time to Interactive of 40.1 seconds, caused primarily by excessive JavaScript processing that blocks the main thread for 2.5 seconds. The site is also loading massive unoptimized images (over 8MB of potential savings) that are too large for their display size and not using modern formats like WebP. Reducing JavaScript execution time, optimizing and properly sizing images, and fixing caching issues could dramatically improve the score by 30+ points and make the site usable for visitors.
Why It Matters:
Unused JavaScript totals 1,313 KiB and blocks main thread execution for 2.5 seconds, severely impacting interactivity.
How to Fix:
Code-split your application bundle to load only necessary JavaScript initially. Remove unused dependencies from vendor bundles, especially YouTube embed scripts when not needed above-fold. Implement dynamic imports for third-party widgets like Funnerix. Use tree-shaking in your build process to eliminate dead code.
Why It Matters:
Images waste 8,628 KiB in unnecessary bytes and lack proper sizing, contributing to poor loading performance.
How to Fix:
Convert PNG event images to WebP/AVIF format for 90%+ compression improvement. Implement responsive images with srcset to serve appropriately sized images (current images are 3.5x larger than needed). Add explicit width/height attributes to prevent layout shifts. Set up proper caching headers for static assets.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Product images are oversized by 3.4MB and loading eagerly above the fold without priority hints.
Critical CSS and JavaScript files are blocking first paint by 1,970ms, preventing content visibility.
94.8% of your CSS (146 KiB) is unused, blocking first paint by 750ms and severely delaying LCP.
Images waste 8,628 KiB in unnecessary bytes and lack proper sizing, contributing to poor loading performance.
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.