LCP
Largest Contentful Paint
6.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Element Render Delay
How to optimize tin.verso.works
Optimize Element Render Delay
High Impact+12 points estimated
Why It Matters
4.5 seconds of element render delay is causing extremely poor LCP performance and user experience.
How to Fix
Identify why the LCP element (HOME button text) takes so long to render after resources load. Optimize React component mounting and reduce JavaScript execution blocking the main thread. Consider server-side rendering or prerendering critical navigation elements.
0Needs Improvement
What This Score Means
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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
91ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website has poor performance with a score of 60/100, meaning users experience slow loading that could hurt engagement and search rankings. The biggest problem is render-blocking CSS that delays the first content from appearing for 4.6 seconds, with an estimated 870ms improvement available by deferring or inlining stylesheets. The site is also bloated with 445 KiB of unused JavaScript from React and other vendor libraries, which adds another 2+ seconds to loading time. Fixing these render-blocking resources and removing unnecessary JavaScript could dramatically improve the user experience and boost the performance score by 30+ points.
Other Optimization Recommendations
Eliminate Render Blocking CSS
High Impact+15 points estimatedWhy It Matters:
CSS is blocking initial page render and delaying LCP by 850ms, preventing users from seeing content quickly.
How to Fix:
Inline critical CSS directly in the HTML head section for above-the-fold content. Use media queries or async loading for non-critical styles. Consider splitting the 613-byte CSS file into critical and non-critical parts to reduce render blocking time.
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
445KB of unused JavaScript is wasting 2.2 seconds of load time and significantly impacting LCP performance.
How to Fix:
Analyze vendor bundles to remove unused features from React, reporting, and TipTap libraries. Implement code splitting to load only required JavaScript modules. Use tree shaking in your build process to eliminate dead code from the 61% unused reporting vendor file.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Optimize Network Dependency Chain
Critical resources are chained with a 211ms dependency tree that delays page rendering.
Defer Render-Blocking CSS
The main CSS file blocks initial rendering and creates a 345ms delay in the critical path.
Optimize Firebase Loading Strategy
Firebase auth iframe creates a long dependency chain that extends page load by 1.4 seconds.
Eliminate Unused CSS Rules
95% of your CSS (14 KiB) is unused and delays both FCP and LCP by 150ms.