Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize prenotaofficina.it
Your CSS file is blocking initial render and delaying LCP by 350ms, preventing users from seeing content.
Inline critical above-the-fold CSS directly in the HTML head section. Load the remaining CSS (index-BjYuMvG_.css) asynchronously using media='print' onload technique. Remove the 90% unused CSS rules or split into component-specific stylesheets.
A score of 68 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 concerning performance issues with a score of 68/100, indicating significant room for improvement. The biggest problem is excessive unused JavaScript code, which is wasting 84 KiB and slowing down page loading by nearly half a second - over 43% of the main JavaScript file isn't actually being used. The site also suffers from render-blocking CSS that delays content appearance by 350ms and unused CSS rules consuming an additional 33 KiB of bandwidth. These issues are causing slow loading times, with the largest content not appearing until 5.6 seconds and first content taking 3.5 seconds to show, which will frustrate users and hurt search rankings.
Why It Matters:
84KB of unused JavaScript is blocking LCP by 450ms and delaying first paint by the same amount.
How to Fix:
Audit your main bundle (index-DH6OJpmO.js) to remove 43% unused code and InfoHome component's 71% unused code. Use tree-shaking in your build process and code-splitting to load components only when needed. Consider lazy loading the InfoHome component if it's below the fold.
Why It Matters:
Your longest dependency chain takes 1.46 seconds, creating unnecessary delays in content loading.
How to Fix:
Preload critical JavaScript files like Utility-B4Vngspv.js and InfoHome-MVBnKouZ.js using <link rel='preload'>. Bundle frequently used small JavaScript files together to reduce network requests. Consider inlining small utilities directly in your main bundle.
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
Critical resources are chained with a 211ms dependency tree that delays page rendering.
The main CSS file blocks initial rendering and creates a 345ms delay in the critical path.
Firebase auth iframe creates a long dependency chain that extends page load by 1.4 seconds.
95% of your CSS (14 KiB) is unused and delays both FCP and LCP by 150ms.