| Don't scale images in the browser (avoidScalingImages) | The page has 10 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. | 0 |
| 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://cdn.sokolov.ru/upload/content/area/8454610412606ef982c9118970903e53.jpg https://cdn.sokolov.ru/upload/content/area/f77c187c912eed81b9a940d56f4e733f.jpg https://cdn.sokolov.ru/upload/content/area/29692ce29bea0ed9fc48a32b78e96577.jpg https://cdn.sokolov.ru/upload/content/area/599381a89a12f2135e4cc41d907c53af.jpg https://cdn.sokolov.ru/upload/content/area/7b737af32bfdf0a9756be23dad1122fa.jpg https://cdn.sokolov.ru/upload/content/area/aacd8376c5eeab8dec4904e69f2fa2d7.jpg https://cdn.sokolov.ru/upload/content/area/d50e7d97286724aca1441de191909703.jpg https://cdn.sokolov.ru/upload/content/area/4a175e582f4323dd74687852cf297369.jpg https://cdn.sokolov.ru/upload/content/area/4754f43eedc890535a35cd5d5da5b413.jpg https://cdn.sokolov.ru/upload/content/area/7730846614634f1e713444e0c80a2198.jpg |
| Have a fast first contentful paint (firstContentfulPaint) | First contentful paint is poor (4.056 s). It is in the Google Web Vitals poor range, slower than 3 seconds.The page has a high time to first byte (TTFB) 1.568 s that you should look into to improve first contentful paint. | 0 |
| Description: The First Contentful Paint (FCP) metric measures the time from when the page starts loading to when any part of the page content is rendered on the screen. For this metric, "content" refers to text, images (including background images), <svg> elements, or non-white <canvas> elements. |
| Inline CSS for faster first render (inlineCss) | The page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens. | 95 |
| Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded. |
| Have a fast largest contentful paint (largestContentfulPaint) | Largest contentful paint is poor 12.436 s. It is in the Google Web Vitals poor range, slower than 4.5 seconds. | 0 |
| 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. |
| Offenders: https://cdn.sokolov.ru/upload/content/area/261309fc704925c726a2b5a50989eaa3.jpg?w=560&h=700 |
| Avoid CPU Long Tasks (longTasks) | The page has 3 CPU long tasks with the total of 498 ms. The total blocking time is 348 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. | 40 |
| 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: selfselfself |
| Avoid Frontend single point of failures (spof) | The page has 11 requests inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head. | 90 |
| Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag. |
| Offenders: https://static-catalog.sokolov.ru/_next/static/css/d952859c721b8e52.css https://static-catalog.sokolov.ru/_next/static/css/753a88f965ca8564.css https://static-catalog.sokolov.ru/_next/static/css/7e6914a619aaaccf.css https://static-catalog.sokolov.ru/_next/static/css/13226014bc357e4b.css https://static-catalog.sokolov.ru/_next/static/css/f2f640d30117f472.css https://static-catalog.sokolov.ru/_next/static/css/d67471c075b0c8ff.css https://static-catalog.sokolov.ru/_next/static/css/a6a191b9c8b7721f.css https://static-catalog.sokolov.ru/_next/static/css/7d06de3534181a6c.css https://static-catalog.sokolov.ru/_next/static/css/29d30e70ddab6860.css https://static-catalog.sokolov.ru/_next/static/css/dc41697283a04350.css https://static-catalog.sokolov.ru/_next/static/css/5513378153b0b486.css |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 18 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 19 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://sokolov.ru/api/v4/content/area/main-banner-004/ https://sokolov.ru/api/v4/content/area/main-stories/ https://sokolov.ru/api/v4/content/area/navigation-block-008/ https://sokolov.ru/api/v5/profile/ https://sokolov.ru/api/v5/profile/products/ https://sokolov.ru/api/v5/handbooks/currency-rates/ https://sokolov.ru/api/v5/location/check/ https://sokolov.ru/api/v3/profile/comment-product/?filter[last_year]=0&page-size=10 https://sokolov.ru/api/v4/content/area/tile-block/ https://sokolov.ru/api/v4/content/area/main-page-topline/ https://static-catalog.sokolov.ru/meta/favicon.ico https://seo.sokolov.ru/api/v1/meta/ip/ https://static-catalog.sokolov.ru/meta/manifest.json https://sokolov.ru/api/v4/content/area/feedback-channels/ https://sokolov.ru/api/v4/content/area/download-app-banner/ https://tracking.diginetica.net/csc-event...ica.net/csc-event https://tracking.diginetica.net/csc-event...ica.net/csc-event https://tracking.diginetica.net/csc-event...ica.net/csc-event |
| Long cache headers is good (cacheHeadersLong) | The page has 1 request that have a shorter cache time than 30 days (but still a cache time). | 99 |
| 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://cdn.diginetica.net/300/client-lite.js |
| Total CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 113.8 kB and uncompressed size is 779.2 kB. That is big and the CSS could most probably be smaller. | 50 |
| 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: |
| The favicon should be small and cacheable (favicon) | The favicon has no cache time. | 50 |
| Description: It is easy to make the favicon big but please avoid doing that, because every browser will then perform an unnecessarily large download. And make sure the cache headers are set for a long time for the favicon. It is easy to miss since it's another content type. |
| Offenders: https://static-catalog.sokolov.ru/meta/favicon.ico |
| Avoid too many fonts (fewFonts) | The page has 4 font requests. Do you really need them? What value does the fonts give the user? | 60 |
| Description: How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive. |
| Offenders: https://cdn.sokolov.ru/fonts/montserrat/bold.woff2 https://cdn.sokolov.ru/fonts/montserrat/regular.woff2 https://cdn.sokolov.ru/fonts/montserrat/medium.woff2 https://cdn.sokolov.ru/fonts/montserrat/semibold.woff2 |
| Total image size shouldn't be too big (imageSize) | The page total image size is 801.1 kB. 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 2.7 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: |
| Avoid using incorrect mime types (mimeTypes) | The page has 1 misconfigured mime type. | 99 |
| Description: It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk. |
| Offenders: https://seo.sokolov.ru/api/v1/meta/ip/ |
| Make each CSS response small (optimalCssSize) | https://static-catalog.sokolov.ru/_next/static/css/d952859c721b8e52.css size is 70.3 kB (70326) and that is bigger than the limit of 14.5 kB. https://static-catalog.sokolov.ru/_next/static/css/13226014bc357e4b.css size is 20.1 kB (20122) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 80 |
| 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 2.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 5 requests with private headers. The main page has a private header. It could be right in some cases where the user can be logged in and served specific content. But if your asset is static it should never be private. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 70 |
| 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://sokolov.ru/ https://sokolov.ru/ https://tracking.diginetica.net/csc-event...ica.net/csc-event https://tracking.diginetica.net/csc-event...ica.net/csc-event https://tracking.diginetica.net/csc-event...ica.net/csc-event |
| Avoid missing and error requests (responseOk) | The page has 2 error responses. The page has 1 response with code 401. The page has 1 response with code 404. | 80 |
| Description: Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it. |
| Offenders: https://sokolov.ru/api/v5/profile/ https://sokolov.ru/api/v3/profile/comment-product/?filter[last_year]=0&page-size=10 |
0 s
4.3 sFirst Contentful Paint 4.252 sFirst Visual Change 4.291 s
4.4 s
4.5 s
4.6 s
5.1 s
5.2 s
5.3 s
5.4 s
5.5 s
5.6 s
5.7 s
6.2 s
6.3 s
6.4 s
6.5 s
6.6 s
6.7 s
6.8 s
7.3 s
7.4 s
7.5 s
7.6 s
7.7 s
7.8 s
7.9 s
8.4 s
8.5 s
8.6 s
8.7 s
8.8 sDOM Content Loaded Time 8.741 sPage Load Time 8.746 sCPU Long Task duration 193 ms
9.1 s
9.3 sLayout Shift 0.00687 9.213 s
9.4 sLayout Shift 0.03318 9.354 s
9.5 s
9.6 s
10.1 s
10.6 s
10.9 s
11 s
11.1 sVisual Complete 85% 11.062 s
11.2 s
11.5 sLCP <DIV> 11.420 s
11.9 s
12 s
12.1 s
12.4 s
12.6 s
12.7 sCPU Long Task duration 57 ms
13 s
13.1 s
13.2 s
13.3 s
13.4 s
13.5 sVisual Complete 95% 13.408 sLast Visual Change 13.475 sVisual Complete 99% 13.475 s
