Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize polyd.com
850KB of unused JavaScript increases download time and blocks the main thread, delaying interactivity by nearly 6 seconds.
Analyze your main app bundle (app-BCRAFwIT.js) and remove unused functions using tree-shaking. Defer loading of reCAPTCHA until user interaction is needed. Split JavaScript into smaller chunks and load only what's needed for the initial page view using dynamic imports.
A score of 42 falls in the "Poor" 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 42/100, indicating significant issues that are hurting user experience. The biggest problem is render-blocking CSS files that are delaying page rendering by over 1 second, combined with a redirect from the root domain that adds another 760ms of delay before the page even starts loading. The site is also loading massive video files (over 4MB total) and has 850KB of unused JavaScript that's slowing everything down. Fixing the redirect, optimizing CSS delivery, and reducing the bloated media files could easily improve the performance score by 30+ points and dramatically speed up the 9.5-second load time.
Why It Matters:
Render-blocking CSS delays LCP by 1.05 seconds, preventing users from seeing meaningful content quickly.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Move non-critical CSS files like sweetalert.css and bootstrap.css to load asynchronously using rel='preload' and onload. Consider combining multiple CSS files into one optimized bundle to reduce HTTP requests.
Why It Matters:
The redirect from polyd.com to polyd.com/it/ adds 760ms delay before page loading even begins.
How to Fix:
Update your web server configuration to serve the Italian version directly without redirects. If using Apache, modify .htaccess rules to point the root domain directly to the Italian content. For Nginx, update the server block configuration to avoid the intermediate redirect step.
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
The redirect from polyd.com to polyd.com/it/ adds 760ms delay before page loading even begins.
Render-blocking CSS delays LCP by 1.05 seconds, preventing users from seeing meaningful content quickly.
Short 1-hour cache lifetime for static assets wastes 3.6MB of repeat downloads for returning visitors.
Unsized images are causing a CLS score of 0.252, significantly hurting user experience and rankings.