Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize www1.ru
702 KiB of unused JavaScript is blocking LCP by 3.9 seconds and severely impacting page performance.
Audit Google Ads and Yandex scripts to remove duplicate implementations. Use code splitting to load only required ad functionality. Implement lazy loading for non-critical advertising scripts using async/defer attributes and intersection observer.
A score of 41 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 serious performance problems with a very poor score of 41/100, meaning most users will experience frustratingly slow loading times. The biggest issue is excessive JavaScript that takes over 4 seconds to process, causing the page to become interactive only after nearly 20 seconds and delaying the main content display to 13.6 seconds. The site is loaded with unused JavaScript code (702 KB that could be removed) and poorly cached resources, particularly from advertising and analytics scripts that are severely slowing down the entire page. Removing unused JavaScript, enabling better caching for frequently-used files, and optimizing the numerous third-party scripts could dramatically improve performance and cut loading times in half.
Why It Matters:
3.1 seconds of JavaScript execution time is blocking the main thread and preventing user interactions.
How to Fix:
Break up long-running tasks in embed.js and ad scripts using setTimeout or requestIdleCallback. Move non-critical scripts to web workers where possible. Defer heavy analytics and advertising code until after page load using dynamic imports.
Why It Matters:
Short cache lifetimes for 584 KiB of resources are causing unnecessary network requests and slowing repeat visits.
How to Fix:
Configure longer cache headers (1 year minimum) for static assets like Yandex Metrica and Google Ad scripts. Implement versioning strategy for cache busting. Set up CDN caching rules to serve cached versions globally.
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
Short cache lifetimes for 584 KiB of resources are causing unnecessary network requests and slowing repeat visits.
3.1 seconds of JavaScript execution time is blocking the main thread and preventing user interactions.
The LCP element has a 4,194ms render delay due to JavaScript animations, severely delaying content visibility.
CSS files are blocking initial page render by 2,070ms, preventing users from seeing content immediately.