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
Critical resources are loading sequentially in a 4.3-second chain instead of in parallel.
Add preconnect hints for fonts.googleapis.com and fonts.gstatic.com in your HTML head. Preload the critical font file (Roboto Condensed) to avoid the sequential download chain. Move font loading to occur earlier in the page lifecycle rather than after JavaScript execution.
A score of 55 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 with a score of 55/100, primarily due to excessive unused JavaScript that's slowing down the page. The biggest issue is that 474KB of JavaScript code isn't being used but still needs to be downloaded and processed, causing the page to take over 7 seconds to become interactive and 13 seconds for content to fully appear. The site is loading large vendor libraries for React, reporting tools, and text editing that are mostly going unused, which could be optimized through code splitting or removing unnecessary features. Additionally, implementing better caching policies and preconnecting to external services like Sentry could provide further speed improvements.
Why It Matters:
474 KiB of unused JavaScript is blocking rendering and delaying LCP by 2.2 seconds.
How to Fix:
Implement code splitting to break vendor bundles into smaller chunks loaded on-demand. Use dynamic imports for React components not needed on initial page load. Configure your build tool to tree-shake unused exports from vendor-reporting, vendor-react, and vendor-tiptap bundles.
Why It Matters:
4.3 seconds of element render delay is severely impacting LCP performance and user experience.
How to Fix:
Move critical CSS inline to prevent render blocking. Optimize the 'HOME' button component rendering by removing unnecessary re-renders. Ensure fonts load immediately by preloading the Roboto Condensed font file and using font-display: swap.
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.