Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize trios.photo.booth.com
Your CSS file blocks rendering for 1.16 seconds and contains 84% unused rules.
Extract above-the-fold CSS and inline it in the HTML head. Load the remaining CSS asynchronously using media='print' onload trick. Use tools like Critical or PurgeCSS to remove unused CSS rules from your stylesheet.
A score of 94 falls in the "Good" 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 excellent performance with a score of 94/100, but there are still some optimization opportunities that could make it even faster. The biggest issue is inefficient caching policies on images and resources, which could save 693 KiB and improve loading times by 600ms for repeat visitors. The site is also loading 99 KiB of unused JavaScript code, with nearly half of the main script file going unused, which adds unnecessary 460ms to load times. Additionally, the CSS file has 84% unused rules, wasting 18 KiB of bandwidth. Fixing these caching policies and removing unused code could push this already strong-performing site closer to a perfect score while significantly improving the experience for returning visitors.
Why It Matters:
Current 1-hour cache lifetime wastes 693 KiB on repeat visits and delays LCP by 600ms.
How to Fix:
Configure your CDN (Hostinger) to cache images for 1 year (31536000 seconds) instead of 1 hour. Update Supabase storage bucket policy to set Cache-Control: max-age=31536000 for static images. Add versioning to image URLs for cache busting when needed.
Why It Matters:
48% of your main JavaScript bundle (99 KiB) is unused, adding 460ms to load time.
How to Fix:
Analyze your main bundle with webpack-bundle-analyzer to identify unused code. Implement code splitting to separate components into smaller chunks that load on demand. Use dynamic imports for non-critical sections like modals and secondary features.
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
91% of CSS (44 KiB) is unused and blocks initial render, delaying FCP by 100ms.
The hero background image is oversized (1182x1168 for 721x712 display) adding 600ms to LCP.
Unused JavaScript (452 KiB) delays LCP by 1.5 seconds and blocks main thread execution.
Over 316KB of unused JavaScript is loaded, wasting bandwidth and blocking the main thread.