| Don't scale images in the browser (avoidScalingImages) | The page has 4 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them. | 60 |
| Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one. |
| Offenders: https://specteh-vidi.com.ua/uploads/media/dc_site/0020/72/cad15012cdf25103bd1644...86e392ecde35.webp https://specteh-vidi.com.ua/uploads/media/dc_site/0007/75/d27f9b5f8b1fc5b47939d9...0e31b41dc43ab.png https://specteh-vidi.com.ua/uploads/media/dc_site/0007/75/b3d82e23feaeff86851f12...ac59c9e7ffb11.png https://specteh-vidi.com.ua/uploads/media/dc_site/0007/75/b3faed6ca26475d165171f...51b41ba11797c.png |
| Avoid using Google Tag Manager. (googleTagManager) | The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page. | 0 |
| Description: Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance. |
| Have a fast largest contentful paint (largestContentfulPaint) | You can add fetchPriority="high" to the image to increase the load priority in Chrome. | 95 |
| Description: Largest contentful paint is one of Google Web Vitals and reports the render time of the largest image or text block visible within the viewport, relative to when the page first started loading. To be fast according to Google, it needs to render before 2.5 seconds and results over 4 seconds is poor performance. |
| Avoid CPU Long Tasks (longTasks) | The page has 7 CPU long tasks with the total of 501 ms. The total blocking time is 138 ms and 2 long tasks before first contentful paint with total time of 113 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks. | 0 |
| Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler. |
| Offenders: unknownselfselfselfselfcross-origin-descendantmultiple-contexts |
| Avoid doing redirects (assetsRedirects) | The page has 9 redirects. 1 of the redirects are from the base domain, please fix them! 8 requests are from other domains, it could be 3rd-party assets doing unnecessary redirects. :( | 10 |
| Description: A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile. |
| Offenders: https://specteh-vidi.com.ua/ https://loyalty.vidi.ua/auth/check-user https://loyalty.vidi.ua/auth/check-user https://c.clarity.ms/c.gif https://c.clarity.ms/c.gif https://c.clarity.ms/c.gif https://c.bing.com/c.gif.../c.bing.com/c.gif https://c.bing.com/c.gif.../c.bing.com/c.gif https://c.bing.com/c.gif.../c.bing.com/c.gif |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 23 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 31 kB the next access. | 0 |
| Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request. |
| Offenders: https://loyalty.vidi.ua/auth/check-user https://www.clarity.ms/tag/jxjvr212jo https://www.google.de/ads/ga-audiences.../ads/ga-audiences https://www.google.de/ads/ga-audiences.../ads/ga-audiences https://specteh-vidi.com.ua/ua/core/app/load-message-tpl https://www.facebook.com/privacy_sandbox/topics/registration/?id=3355927271217469 https://www.facebook.com/tr/....facebook.com/tr/ https://www.facebook.com/privacy_sandbox/pixel/register/trigger/...register/trigger/ https://loyalty.vidi.ua/login https://loyalty.vidi.ua/auth/check-user https://www.clarity.ms/tag/qnlng5p6c6 https://loyalty.vidi.ua/ua/core/app/load-message-tpl https://loyalty.vidi.ua/login https://www.clarity.ms/tag/qnlng5p6c6 https://c.clarity.ms/c.gif https://c.clarity.ms/c.gif https://c.clarity.ms/c.gif https://c.bing.com/c.gif.../c.bing.com/c.gif https://c.bing.com/c.gif.../c.bing.com/c.gif https://c.bing.com/c.gif.../c.bing.com/c.gif https://c.clarity.ms/c.gif....clarity.ms/c.gif https://c.clarity.ms/c.gif....clarity.ms/c.gif https://c.clarity.ms/c.gif....clarity.ms/c.gif |
| Long cache headers is good (cacheHeadersLong) | The page has 11 requests that have a shorter cache time than 30 days (but still a cache time). | 89 |
| Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version. |
| Offenders: https://specteh-vidi.com.ua/ https://www.googletagmanager.com/gtm.js?id=GTM-TMFTS4NC https://connect.facebook.net/en_US/fbevents.js https://connect.facebook.net/signals/config/3355927271217469.../3355927271217469 https://www.googletagmanager.com/gtag/js...nager.com/gtag/js https://www.googletagmanager.com/gtag/js...nager.com/gtag/js https://www.clarity.ms/s/0.8.19/clarity.js https://www.googletagmanager.com/gtm.js?id=GTM-5WFLZNW https://connect.facebook.net/en_US/sdk.js https://www.googletagmanager.com/gtag/js...nager.com/gtag/js https://www.clarity.ms/s/0.8.19/clarity.js |
| Always compress text content (compressAssets) | The page has 8 requests that are served uncompressed. You could save a lot of bytes by sending them compressed instead. | 20 |
| Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith. |
| Offenders: |
| Total CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 138 kB and uncompressed size is 729.6 kB. That is big and the CSS could most probably be smaller. | 0 |
| Description: Delivering a massive amount of CSS to the browser is not the best thing you can do, because it means more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page. And make sure to remove CSS rules when they aren't used anymore. |
| Offenders: |
| Avoid redirecting the main document (documentRedirect) | The main document gets redirected 1 time(s). Remove those redirect and make the page faster! | 0 |
| Description: You should never ever redirect the main document, because it will make the page load slower for the user. Well, you should redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. The coach checks for that. :) |
| Offenders: https://specteh-vidi.com.ua/ |
| Total image size shouldn't be too big (imageSize) | The page total image size is 1.9 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/. | 50 |
| Description: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user. |
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 1.1 MB and the uncompressed size is 3.5 MB. This is totally crazy! There is really room for improvement here. | 0 |
| Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks? |
| Offenders: |
| Make each CSS response small (optimalCssSize) | https://specteh-vidi.com.ua/dist/prod/dcsite/unicommerce/css/unicommerce.css?v1.4.720 size is 58.7 kB (58683) and that is bigger than the limit of 14.5 kB. https://loyalty.vidi.ua/bundles/core/css/bootstrap_build/bootstrap.css?v1.4.720 size is 17.4 kB (17397) and that is bigger than the limit of 14.5 kB. https://loyalty.vidi.ua/bundles/core/css/core.prod.css?v1.4.720 size is 19.5 kB (19493) and that is bigger than the limit of 14.5 kB. https://loyalty.vidi.ua/bundles/my/css/style.css?v1.4.720 size is 14.7 kB (14677) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 60 |
| Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier. |
| Offenders: |
| Total page size shouldn't be too big (pageSize) | The page total transfer size is 3.3 MB, which is more than the coach limit of 2 MB. That is really big and you need to make it smaller. | 0 |
| Description: Avoid having pages that have a transfer size over the wire of more than 2 MB (desktop) and 1 MB (mobile) because that is really big and will hurt performance and will make the page expensive for the user if she/he pays for the bandwidth. |
| Offenders: |
| Don't use private headers on static content (privateAssets) | The page has 16 requests with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 0 |
| Description: If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private. |
| Offenders: https://www.googletagmanager.com/gtm.js?id=GTM-TMFTS4NC https://loyalty.vidi.ua/auth/check-user https://www.googletagmanager.com/gtag/js...nager.com/gtag/js https://www.googletagmanager.com/gtag/js...nager.com/gtag/js https://specteh-vidi.com.ua/ua/core/app/load-message-tpl https://www.facebook.com/privacy_sandbox/topics/registration/?id=3355927271217469 https://www.facebook.com/privacy_sandbox/pixel/register/trigger/...register/trigger/ https://loyalty.vidi.ua/login https://www.googletagmanager.com/gtm.js?id=GTM-5WFLZNW https://loyalty.vidi.ua/auth/check-user https://www.googletagmanager.com/gtag/js...nager.com/gtag/js https://loyalty.vidi.ua/ua/core/app/load-message-tpl https://loyalty.vidi.ua/login https://c.clarity.ms/c.gif....clarity.ms/c.gif https://c.clarity.ms/c.gif....clarity.ms/c.gif https://c.clarity.ms/c.gif....clarity.ms/c.gif |
0 s
1.4 sFirst Contentful Paint 1.308 sFirst Visual Change 1.335 s
1.6 sLayout Shift 0.00031 1.505 sCPU Long Task duration 54 msCPU Long Task duration 190 ms
1.8 sDOM Content Loaded Time 1.756 s
1.9 s
2 sCPU Long Task duration 54 ms
2.1 s
2.2 s
2.3 s
2.4 s
7.5 s
7.6 s
7.7 s
9.3 s
9.4 s
9.5 s
9.6 s
9.7 s
9.8 sLast Visual Change 9.744 sVisual Complete 85% 9.744 sVisual Complete 95% 9.744 sVisual Complete 99% 9.744 s
