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
The LCP element has a massive 4.6 second render delay, making your page feel unresponsive.
Move critical CSS inline to avoid render-blocking requests. Preload the roboto-condensed fonts using <link rel='preload'> tags. Optimize the font loading chain by using font-display: swap and consider using a system font stack as fallback.
A score of 67 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 poor performance issues with a score of 67/100, primarily due to excessive unused JavaScript that's wasting 380 KiB and delaying page loading by nearly 2 seconds. The site takes 4.2 seconds for users to see the first meaningful content (First Contentful Paint), and the Speed Index of 11.9 seconds indicates an extremely slow visual loading experience. The biggest quick wins would be removing or deferring unused JavaScript from vendor files and implementing proper browser caching for the custom fonts, which could save an additional 190 KiB on repeat visits. These optimizations could potentially improve the performance score by 25+ points and dramatically reduce loading times for users.
Why It Matters:
Unused JavaScript wastes 380 KiB and delays both LCP and FCP by 1.95 seconds.
How to Fix:
Use webpack-bundle-analyzer or similar tools to identify dead code in your vendor bundles. Implement code splitting to load only necessary JavaScript per page. Configure tree shaking in your build process to eliminate unused exports from vendor-reporting, vendor-ui, and vendor-tiptap bundles.
Why It Matters:
Font files totaling 190 KiB have zero cache lifetime, forcing re-downloads on every visit.
How to Fix:
Configure your server to set Cache-Control headers with max-age=31536000 (1 year) for font files. Add proper ETags for cache validation. Consider using a CDN to serve fonts with automatic compression and optimal caching policies.
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.