Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize tin.verso.works
Poor caching wastes 73 KiB on repeat visits and adds 450ms to LCP for returning users.
Configure your server to set cache headers for JavaScript assets to 1 year (31536000 seconds) instead of current 7 days. Implement cache busting through filename hashing to safely extend cache lifetimes. Add immutable directive to vendor assets that never change.
A score of 60 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 significant performance problems with a poor score of 60/100, taking over 6 seconds to become fully interactive for users. The biggest issue is excessive unused JavaScript - the site loads 446 KB of unnecessary code that could be removed or deferred, which alone is delaying page loading by over 2 seconds. The site is also suffering from inefficient caching (wasting 73 KB of potential savings) and render-blocking resources that prevent content from displaying quickly. Removing unused JavaScript, implementing better caching strategies, and optimizing the loading sequence could dramatically improve this site's performance and user experience.
Why It Matters:
446 KiB of unused JavaScript is delaying LCP by 2.2 seconds and blocking page interactivity.
How to Fix:
Implement code splitting to load only necessary JavaScript chunks per route. Use dynamic imports for vendor libraries like tiptap editor that show 94% unused code. Configure your bundler to create smaller vendor chunks and lazy load reporting functionality when needed.
Why It Matters:
3.3 seconds of element render delay is causing your LCP to reach 6.3 seconds.
How to Fix:
Inline critical CSS for above-the-fold content to avoid render-blocking requests. Preload the main CSS file and defer non-critical styles. Optimize the DOM structure around your LCP element (HOME button) to render earlier in the page lifecycle.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.