Run 3 summary

Summary

Metric	Value
Page metrics
Performance score	67
Total page size	1.3 MB
Requests	117
Timing metrics
TTFB	599 ms
First Paint	952 ms
Fully Loaded	3.872 s
Google Web Vitals
TTFB	599 ms
First Contentful Paint (FCP)	952 ms
Largest Contentful Paint (LCP)	2.916 s
Cumulative Layout Shift (CLS)	0.04
Total Blocking Time	1.900 s
Max Potential FID	354 ms
CPU metrics
CPU long tasks	16
CPU last long task happens at	4.868 s
Visual Metrics
First Visual Change	967 ms
Speed Index	2.208 s
Visual Complete 85%	3.033 s
Visual Complete 99%	4.267 s
Last Visual Change	4.267 s

Waterfall

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.8 sCPU Long Task duration 69 msDOM Content Loaded Time 798 ms

0.9 sPage Load Time 822 msCPU Long Task duration 62 ms

1 sCPU Long Task duration 115 msFirst Contentful Paint 952 msFirst Visual Change 967 ms

1.1 s

1.2 sLayout Shift 0.00681 1.106 s

1.3 sLayout Shift 0.00009 1.260 s

1.4 sCPU Long Task duration 62 ms

1.5 sLayout Shift 0.00004 1.472 s

1.6 sCPU Long Task duration 79 ms

1.7 sLayout Shift 0.02383 1.618 sLayout Shift 0.00885 1.663 sCPU Long Task duration 104 ms

1.8 s

1.9 sLayout Shift 0.00015 1.822 s

2 sLayout Shift 0.00010 1.904 s

2.1 sCPU Long Task duration 294 ms

2.2 s

2.3 s

2.4 sCPU Long Task duration 354 ms

2.5 s

2.6 s

2.7 s

2.8 sCPU Long Task duration 212 ms

3 sLCP <IMG> 2.916 sCPU Long Task duration 100 ms

3.1 sVisual Complete 85% 3.033 sCPU Long Task duration 53 ms

3.2 s

3.3 sCPU Long Task duration 83 ms

3.4 s

3.5 s

3.6 s

3.7 s

3.8 s

3.9 sFully Loaded 3.872 sCPU Long Task duration 312 ms

4.3 sCPU Long Task duration 327 msLast Visual Change 4.267 sVisual Complete 95% 4.267 sVisual Complete 99% 4.267 s

Coach

The coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 8.0.2.

Coach score

• Total score 76
• Performance score 67
• Privacy score 86
• Best practice score 89

Performance advice (67)

Show/hide details

Title	Advice	Score
Don't scale images in the browser (avoidScalingImages)	The page has 16 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://pmdn.sokolov.io/pics/BC/78/0CDB73CC7F106A07A2CD8F5C299A.jpg https://pmdn.sokolov.io/pics/38/9C/D016DFFE37C198934F70DE38CB4B.jpg https://pmdn.sokolov.io/pics/6D/7E/C2785E3685C5261B70041BC93ABE.jpg https://pmdn.sokolov.io/pics/50/A8/AF837F4EE2E33544032842F6F129.jpg https://pmdn.sokolov.io/pics/BB/0B/B1E2DD99A233A3EE0C40BBA1184A.jpg https://pmdn.sokolov.io/pics/35/2D/7C48F720AA4A3EA9B8ABDF16D129.jpg https://pmdn.sokolov.io/pics/54/E7/D4FE0530594706A1AF586E4C86FA.jpg https://pmdn.sokolov.io/pics/82/27/A27F05511AF261785146EEF45AD4.jpg https://pmdn.sokolov.io/pics/31/36/B683F4781306F5E56133C27BD0BD.jpg https://pmdn.sokolov.io/pics/CF/26/F76FC343E2F85EFC18F3AD8F870F.jpg https://pmdn.sokolov.io/pics/77/18/E97E1FB9B7E4F84468656B68F671.jpg https://pmdn.sokolov.io/pics/A4/67/31407DC51F0249B66DEFB0866DF0.jpg https://pmdn.sokolov.io/pics/A4/49/F006F419099B568702BCA03E4C4F.jpg https://pmdn.sokolov.io/pics/61/3D/BE0611F5802EF2B7E98982227633.jpg https://pmdn.sokolov.io/pics/2F/75/1885AB281E36E3DB1EE29B831E8D.jpg https://pmdn.sokolov.io/pics/A4/61/0441B9E6076A1287A3A114582B48.jpg
Inline CSS for faster first render (inlineCss)	The page has both inline styles as well as it is requesting 15 CSS files inside of the head. Let's only inline CSS for really fast render.	90
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.
Offenders: https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/96fb30b8aa581b44.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/1054ed6e36258047.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/3a1c3f138ddf7a3b.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/5f5cf2985083d60d.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/923538a4e5a3c925.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/19d573113731dbc2.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/fa9047d82d6bf86b.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/b28748a954d46405.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/90bfe13a8ba625fb.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/a8734a6e2b3c0e0a.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/5bd6dffa208389a0.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/d32410ee3fa1a458.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/71b382922e80f972.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/998e8ce38d1e30c8.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/836fffc9a4348e28.css
Have a fast largest contentful paint (largestContentfulPaint)	Largest contentful paint can be improved 2.916 s. It is in the Google Web Vitals needs improvement range, slower than 2.5 seconds. You can add fetchPriority="high" to the image to increase the load priority in Chrome. The image is lazy loaded using the lazy attribute, you should avoid that on the LCP image.	55
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://pmdn.sokolov.io/pics/BC/78/0CDB73CC7F106A07A2CD8F5C299A.jpg
Avoid CPU Long Tasks (longTasks)	The page has 17 CPU long tasks with the total of 2.864 s. The total blocking time is 1.918 s and 3 long tasks before first contentful paint with total time of 246 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: self self self self self self self self self self self self self self self self self
Avoid Frontend single point of failures (spof)	The page has 15 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://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/96fb30b8aa581b44.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/1054ed6e36258047.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/3a1c3f138ddf7a3b.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/5f5cf2985083d60d.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/923538a4e5a3c925.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/19d573113731dbc2.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/fa9047d82d6bf86b.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/b28748a954d46405.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/90bfe13a8ba625fb.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/a8734a6e2b3c0e0a.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/5bd6dffa208389a0.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/d32410ee3fa1a458.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/71b382922e80f972.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/998e8ce38d1e30c8.css https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/836fffc9a4348e28.css
Avoid doing redirects (assetsRedirects)	The page has 4 redirects. 4 of the redirects are from the base domain, please fix them!	60
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://stage.sokolov.ru/upload/content/area/dfd375aa4e2f3c311213d48422039027.jpg https://stage.sokolov.ru/upload/content/area/de6daf5ac89f1e0522d9cf7a2728609a.png https://stage.sokolov.ru/upload/content/fb7a6e5625569f2b211959ccec295994.jpg?w=480 https://stage.sokolov.ru/upload/content/fb7a6e5625569f2b211959ccec295994.jpg
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 47 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 545.9 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://stage.sokolov.ru/spa-images/footer/app-store-badge.svg https://stage.sokolov.ru/spa-images/footer/google-play-badge.svg https://stage.sokolov.ru/spa-images/footer/app-gallery-badge.svg https://stage.sokolov.ru/spa-images/footer/rustore-badge.svg https://stage.sokolov.ru/api/v5/profile/ https://stage.sokolov.ru/api/v5/profile/products/ https://stage.sokolov.ru/api/v5/handbooks/currency-rates/ https://stage.sokolov.ru/api/v5/location/check/ https://stage.sokolov.ru/api/v4/content/area/nav-buttons/ https://frontend-stage-static.k8s.dev.sokolov.io/meta/manifest.json https://frontend-stage-static.k8s.dev.sokolov.io/meta/favicon.ico https://stage.sokolov.ru/api/v4/content/area/main-page-topline/ https://catalog-stage.k8s.dev.sokolov.io/api/v2/filters/jewelry-catalog/rings/gold/ https://stage.sokolov.ru/api/v4/content/area/feedback-channels/ https://sokolov-b2c-seo.k8s.dev.sokolov.io/api/v1/meta/ip/ https://catalog-stage.k8s.dev.sokolov.io/api/v2/catalog/jewelry-catalog/rings/gold/?per_page=72 https://stage.sokolov.ru/upload/content/area/dfd375aa4e2f3c311213d48422039027.jpg https://cdn.sokolov.ru/upload/content/area/dfd375aa4e2f3c311213d48422039027.jpg https://pmdn.sokolov.io/other/insert-forms/shock-price.svg https://stage.sokolov.ru/upload/content/area/de6daf5ac89f1e0522d9cf7a2728609a.png https://cdn.sokolov.ru/upload/content/area/de6daf5ac89f1e0522d9cf7a2728609a.png https://tracking.diginetica.net/csc-event...ica.net/csc-event https://stage.sokolov.ru/api/v5/handbooks/delivery-info/ https://stage.sokolov.ru/api/v5/products/sale-label/...ducts/sale-label/ https://stage.sokolov.ru/api/v5/products/comment-info/...cts/comment-info/ https://stage.sokolov.ru/api/v5/products/prices/.../products/prices/ https://pmdn.sokolov.io/pics/BC/78/0CDB73CC7F106A07A2CD8F5C299A.jpg https://pmdn.sokolov.io/pics/38/9C/D016DFFE37C198934F70DE38CB4B.jpg https://pmdn.sokolov.io/pics/6D/7E/C2785E3685C5261B70041BC93ABE.jpg https://pmdn.sokolov.io/pics/50/A8/AF837F4EE2E33544032842F6F129.jpg https://pmdn.sokolov.io/pics/BB/0B/B1E2DD99A233A3EE0C40BBA1184A.jpg https://pmdn.sokolov.io/pics/35/2D/7C48F720AA4A3EA9B8ABDF16D129.jpg https://pmdn.sokolov.io/pics/54/E7/D4FE0530594706A1AF586E4C86FA.jpg https://pmdn.sokolov.io/pics/82/27/A27F05511AF261785146EEF45AD4.jpg https://pmdn.sokolov.io/pics/31/36/B683F4781306F5E56133C27BD0BD.jpg https://pmdn.sokolov.io/pics/CF/26/F76FC343E2F85EFC18F3AD8F870F.jpg https://pmdn.sokolov.io/pics/77/18/E97E1FB9B7E4F84468656B68F671.jpg https://pmdn.sokolov.io/pics/A4/67/31407DC51F0249B66DEFB0866DF0.jpg https://pmdn.sokolov.io/pics/A4/49/F006F419099B568702BCA03E4C4F.jpg https://pmdn.sokolov.io/pics/61/3D/BE0611F5802EF2B7E98982227633.jpg https://pmdn.sokolov.io/pics/2F/75/1885AB281E36E3DB1EE29B831E8D.jpg https://pmdn.sokolov.io/pics/A4/61/0441B9E6076A1287A3A114582B48.jpg https://tracking.diginetica.net/csc-event...ica.net/csc-event https://stage.sokolov.ru/upload/content/fb7a6e5625569f2b211959ccec295994.jpg?w=480 https://stage.sokolov.ru/upload/content/fb7a6e5625569f2b211959ccec295994.jpg https://cdn.sokolov.ru/upload/content/fb7a6e5625569f2b211959ccec295994.jpg?w=480 https://cdn.sokolov.ru/upload/content/fb7a6e5625569f2b211959ccec295994.jpg
Long cache headers is good (cacheHeadersLong)	The page has 2 requests that have a shorter cache time than 30 days (but still a cache time).	98
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://stage.sokolov.ru/interface/icons/redesign/rocket-launch.svg https://cdn.diginetica.net/300/client-lite.js
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://frontend-stage-static.k8s.dev.sokolov.io/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
Avoid too many requests per domain [HTTP/1] (fewRequestsPerDomain)	The page has 1 domain that serves more than 30 requests. frontend-stage-static.k8s.dev.sokolov.io got 59 requests. Improve performance by sharding those or move to HTTP/2.	90
Description: Browsers have a limit on how many concurrent requests they can do per domain when using HTTP/1. When you hit the limit, the browser will wait before it can download more assets on that domain. So avoid having too many requests per domain.
Offenders: frontend-stage-static.k8s.dev.sokolov.io
Total JavaScript size shouldn't be too big (javascriptSize)	The total JavaScript transfer size is 497.4 kB and the uncompressed size is 1.6 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: URL Transfer size Content size https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/webpack-9624b4f44c6f4995.js 7.8 KB 15.1 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/framework-aaff1786eadd4e8b.js 65.5 KB 205.7 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/main-8933f27b2dfdcc1f.js 31.5 KB 109.0 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/pages/_app-daf3c63fbbdaa3d9.js 153.8 KB 522.3 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/52-d9aab76c31370c5e.js 6.9 KB 20.0 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4971-404605cbe97ec889.js 3.9 KB 10.1 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/pages/catal...c84d5db3959284.js 601 B 601 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/N5FImJc-WA-6J8kecq..._buildManifest.js 1.4 KB 4.5 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/N5FImJc-WA-6J8kecqpVE/_ssgManifest.js 77 B 77 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/5691.e9396392c321c350.js 2.0 KB 4.5 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/1541.98a271df74534fdf.js 1.2 KB 2.8 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/1389-ca22e2ec17e8e634.js 16.9 KB 60.9 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/3333.5eba57844a27645d.js 15.6 KB 49.8 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4349.b8d81f22b53a9055.js 276 B 276 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/2001.4a2c563424868068.js 1008 B 1008 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4729-d2f7556ef5a1e9ce.js 2.1 KB 3.9 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/1109-c76fec06d4af38d5.js 8.1 KB 23.1 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/5245-fd8ea53fd6ac16ab.js 7.5 KB 19.9 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/8570.91ac99e6a3424761.js 4.3 KB 11.8 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/7703.0eba1a3200eb135c.js 2.5 KB 5.6 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4643-fe528e618c90a44c.js 32.3 KB 110.9 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/1632.25c934f363257c16.js 1.6 KB 4.2 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/8400.e8ac19c47b8f8d27.js 2.3 KB 7.3 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/7811.45276236ac95f6e1.js 1.4 KB 3.2 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/7152.4e2cab3558b69188.js 1.0 KB 2.0 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/566.0c0417b504718185.js 784 B 784 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/8316.2f0baf6b0adfaf4f.js 824 B 824 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4803.a81bac4a22023b4a.js 673 B 673 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/9436.986629187286c143.js 6.0 KB 15.1 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/7413.07cdcc44c06b3a97.js 7.4 KB 21.7 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4399.43fd96f08ce3432e.js 1.1 KB 3.0 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4100.32b68982a7d87933.js 824 B 824 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/6503.06cb04399386cb06.js 724 B 724 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/724.5d002ad7e17fb8f5.js 609 B 609 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/6547.23d062a875b3ff92.js 8.9 KB 26.1 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4667.942ea719f5a4b578.js 14.0 KB 45.0 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/7330.ffeb9d46ff5fe264.js 975 B 975 B https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/2415.100e9038f6ab9a29.js 831 B 1.8 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/4379.021e104d0f1004dc.js 870 B 1.4 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/6611.a6ac3b8b55b95e77.js 915 B 1.5 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/3160.3189c606b5b58bd1.js 803 B 803 B https://cdn.diginetica.net/300/client-lite.js 66.8 KB 248.1 KB https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/chunks/8907.16d58c0e3cf80d79.js 1.2 KB 2.9 KB
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://sokolov-b2c-seo.k8s.dev.sokolov.io/api/v1/meta/ip/
Make each CSS response small (optimalCssSize)	https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/96fb30b8aa581b44.css size is 38.9 kB (38890) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB.	90
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: URL Transfer size Content size https://frontend-stage-static.k8s.dev.sokolov.io/_next/static/css/96fb30b8aa581b44.css 38.0 KB 246.0 KB
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.	60
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://stage.sokolov.ru/jewelry-catalog/rings/gold/ https://catalog-stage.k8s.dev.sokolov.io/api/v2/filters/jewelry-catalog/rings/gold/ https://catalog-stage.k8s.dev.sokolov.io/api/v2/catalog/jewelry-catalog/rings/gold/?per_page=72 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 1 error response. The page has 1 response with code 404.	90
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://stage.sokolov.ru/api/v5/profile/

Best practice advice (89)

Show/hide details

Title	Advice	Score
Meta description (metaDescription)	The meta description is too long. It has 273 characters, the recommended max is 155	50
Description: Use a page description to make the page more relevant to search engines.
Page title (pageTitle)	The title is too long by 56 characters. The recommended max is 60	50
Description: Use a title to make the page more relevant to search engines.
Do not send too long headers (longHeaders)	https://stage.sokolo...t/easy-calculate/ has a header set-cookie that is 837 characters long. https://stage.sokolo...profile/products/ has a header set-cookie that is 837 characters long. https://stage.sokolo...5/location/check/ has a header set-cookie that is 885 characters long. https://stage.sokolo...ducts/sale-label/ has a header link that is 851 characters long. https://stage.sokolo...cts/comment-info/ has a header link that is 2567 characters long.	95
Description: Do not send response headers that are too long.
Offenders: https://stage.sokolov.ru/api/v6/basket/easy-calculate/ https://stage.sokolov.ru/api/v5/profile/products/ https://stage.sokolov.ru/api/v5/location/check/ https://stage.sokolov.ru/api/v5/products/sale-label/...ducts/sale-label/ https://stage.sokolov.ru/api/v5/products/comment-info/...cts/comment-info/
Avoid unnecessary headers (unnecessaryHeaders)	There are 15 responses that sets both a max-age and expires header. There are 10 responses that sets a pragma no-cache header (that is a request header). There are 24 responses that sets a server header.	51
Description: Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
Offenders: https://cdn.sokolov.ru/fonts/montserrat/bold.woff2 https://cdn.sokolov.ru/fonts/montserrat/bold.woff2 https://cdn.sokolov.ru/fonts/montserrat/regular.woff2 https://cdn.sokolov.ru/fonts/montserrat/regular.woff2 https://cdn.sokolov.ru/fonts/montserrat/medium.woff2 https://cdn.sokolov.ru/fonts/montserrat/medium.woff2 https://cdn.sokolov.ru/fonts/montserrat/semibold.woff2 https://cdn.sokolov.ru/fonts/montserrat/semibold.woff2 https://stage.sokolov.ru/api/v6/basket/easy-calculate/ https://stage.sokolov.ru/api/v6/basket/easy-calculate/ https://stage.sokolov.ru/api/v5/profile/products/ https://stage.sokolov.ru/api/v5/profile/products/ https://pmdn.sokolov.io/other/insert-forms/shock-price.svg https://stage.sokolov.ru/interface/icons/redesign/rocket-launch.svg https://cdn.diginetica.net/300/client-lite.js 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 https://stage.sokolov.ru/api/v4/content/filter/ https://stage.sokolov.ru/api/v4/content/filter/ https://stage.sokolov.ru/api/v4/content/filter/web-catalog-top/ https://stage.sokolov.ru/api/v4/content/filter/web-catalog-top/ https://stage.sokolov.ru/api/v5/handbooks/delivery-info/ https://stage.sokolov.ru/api/v5/handbooks/delivery-info/ https://stage.sokolov.ru/api/v5/products/sale-label/...ducts/sale-label/ https://stage.sokolov.ru/api/v5/products/sale-label/...ducts/sale-label/ https://stage.sokolov.ru/api/v5/products/comment-info/...cts/comment-info/ https://stage.sokolov.ru/api/v5/products/comment-info/...cts/comment-info/ https://stage.sokolov.ru/api/v5/products/prices/.../products/prices/ https://stage.sokolov.ru/api/v5/products/prices/.../products/prices/ https://pmdn.sokolov.io/pics/BC/78/0CDB73CC7F106A07A2CD8F5C299A.jpg https://pmdn.sokolov.io/pics/38/9C/D016DFFE37C198934F70DE38CB4B.jpg https://pmdn.sokolov.io/pics/6D/7E/C2785E3685C5261B70041BC93ABE.jpg https://pmdn.sokolov.io/pics/50/A8/AF837F4EE2E33544032842F6F129.jpg https://pmdn.sokolov.io/pics/BB/0B/B1E2DD99A233A3EE0C40BBA1184A.jpg https://pmdn.sokolov.io/pics/35/2D/7C48F720AA4A3EA9B8ABDF16D129.jpg https://pmdn.sokolov.io/pics/54/E7/D4FE0530594706A1AF586E4C86FA.jpg https://pmdn.sokolov.io/pics/82/27/A27F05511AF261785146EEF45AD4.jpg https://pmdn.sokolov.io/pics/31/36/B683F4781306F5E56133C27BD0BD.jpg https://pmdn.sokolov.io/pics/CF/26/F76FC343E2F85EFC18F3AD8F870F.jpg https://pmdn.sokolov.io/pics/77/18/E97E1FB9B7E4F84468656B68F671.jpg https://pmdn.sokolov.io/pics/A4/67/31407DC51F0249B66DEFB0866DF0.jpg https://pmdn.sokolov.io/pics/A4/49/F006F419099B568702BCA03E4C4F.jpg https://pmdn.sokolov.io/pics/61/3D/BE0611F5802EF2B7E98982227633.jpg https://pmdn.sokolov.io/pics/2F/75/1885AB281E36E3DB1EE29B831E8D.jpg https://pmdn.sokolov.io/pics/A4/61/0441B9E6076A1287A3A114582B48.jpg 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

Privacy advice (86)

Show/hide details

Title	Advice	Score
Use a good Content-Security-Policy header to make sure you you avoid Cross Site Scripting (XSS) attacks. (contentSecurityPolicyHeader)	Set a Content-Security-Policy header to make sure you are not open for Cross Site Scripting (XSS) attacks. You can start with setting a Content-Security-Policy-Report-Only header, that will only report the violation, not stop the download.	0
Description: Content Security Policy is delivered via a HTTP response header, and defines approved sources of content that the browser may load. It can be an effective countermeasure to Cross Site Scripting (XSS) attacks and is also widely supported and usually easily deployed. https://scotthelme.co.uk/content-security-policy-an-introduction/.
Offenders: https://stage.sokolov.ru/jewelry-catalog/rings/gold/
Set a referrer-policy header to make sure you do not leak user information. (referrerPolicyHeader)	Set a referrer-policy header to make sure you do not leak user information.	0
Description: Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/.
Offenders: https://stage.sokolov.ru/jewelry-catalog/rings/gold/
Set a strict transport header to make sure the user always use HTTPS. (strictTransportSecurityHeader)	A strict transport header is set but miss out on setting includeSubDomainsThe max age is lower than six months. Increase it to get a better score.	70
Description: The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security.

Page info

Page info
Title	Золотые кольца ᐉ купить в официальном интернет-магазине SOKOLOV • Выгодные цены в каталоге • Доставка по Москве и РФ
Width	1904
Height	13860
DOM elements	5304
Avg DOM depth	16
Max DOM depth	26
Iframes	0
Script tags	13
Local storage	31 B
Session storage	321 B
Network Information API	4g

Resource Hints
dns-prefetch
http://cdn.diginetica.net/
preconnect
http://autocomplete.diginetica.net/
https://static.criteo.net/
https://cm.g.doubleclick.net/
https://ad.mail.ru/
https://googleads.g.doubleclick.net/
https://www.googletagmanager.com/
https://www.google-analytics.com/
https://api.mindbox.ru/
https://api.flocktory.com/
https://demo4.paasweb.co.il/

Technologies used to build the page.

Data collected using Wappalyzerversion 6.10.66.  Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyser find more information about technologies used.

Technology	Confidence	Category
Amazon Web Services	100	PaaS
HSTS	100	Security

Visual Metrics

Browser Metrics

Largest Contentful Paint

When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.

Element type	IMG
Element/tag	<img alt="Кольцо из белого золота с бриллиантами и танзанитом 6014351-3" loading="lazy" width="100" height="100" decoding="async" data-nimg="1" class="ProductListItem_product-image__DZ6vX" src="https://pmdn.sokolov.io/pics/BC/78/0CDB73CC7F106A07A2CD8F5C299A.jpg" style="color: transparent;">
Render time	2.916 s
Elements that needed recalculate style before LCP	5289
Time spent in recalculate style before LCP	276.99 ms
Load time	2.916 s
URL	https://pmdn.sokolov...7A2CD8F5C299A.jpg
Size (width*height)	53592
DOM path
div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(1) > div:eq(0) > a:eq(0) > div > div:eq(0) > div > div:eq(0) > picture > img> div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(1) > div:eq(0) > a:eq(0) > div > div:eq(0) > div > div:eq(0) > picture > img>

The largest contentful paint is highlighted in the image. If no element is highlighted the element was removed before the screenshot or the LCP API couldn't find the element.

The Largest Contentful Paint API highlighted this image as a part of the LCP.

Detected Cumulative Layout Shift

0.03988 cumulative layout shift collected from the Cumulative Layout Shift API.

These HTML elements contribute most to the Cumulative Layout Shifts of the page. The higher score, the more layout shift.

Score	HTML Element
0.02383	<div class="CatalogListHeader_sorting-area__fCNyj" data-qa="sorting_area"></div>,<a class="styles_tag__6Ja5v styles_tag__gray__sHQ2C styles_tag__s__TGnQM" href="/jewelry-catalog/rings/engagement/gold/"></a>,<a class="styles_tag__6Ja5v styles_tag__gray__sHQ2C styles_tag__s__TGnQM" href="/jewelry-catalog/rings/gold/yellowgold/"></a>,<button class="styles_catalog-tags__reset-btn__0guyb"></button>,<a class="styles_tag__6Ja5v styles_tag__gray__sHQ2C styles_tag__s__TGnQM" href="/jewelry-catalog/rings/gold/redgold/"></a>
body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(1),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > a:eq(1),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > a:eq(5),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > button:eq(4),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > a:eq(4)
0.00885	<a class="styles_tag__6Ja5v styles_tag__gray__sHQ2C styles_tag__s__TGnQM" href="/jewelry-catalog/rings/gold/yellowgold/"></a>,<button class="styles_catalog-tags-btn__hEZe_"></button>,<a class="styles_tag__6Ja5v styles_tag__gray__sHQ2C styles_tag__s__TGnQM" href="/jewelry-catalog/rings/wedding/gold/"></a>,<a class="styles_tag__6Ja5v styles_tag__gray__sHQ2C styles_tag__s__TGnQM" href="/jewelry-catalog/rings/engagement/gold/"></a>,<a class="styles_tag__6Ja5v styles_tag__gray__sHQ2C styles_tag__s__TGnQM" href="/jewelry-catalog/rings/gold/redgold/"></a>
body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > a:eq(5),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > button:eq(2),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > a:eq(0),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > a:eq(1),body > div#__next > div#catalog > div > main > div > div > section > div:eq(1) > div:eq(0) > div:eq(0) > div > a:eq(4)
0.00681	<input data-qa="header_search_input" enterkeyhint="search" id="text_search_input" autocomplete="off" type="text" placeholder="Поиск по каталогу" class="_Input_input__7xcBD _Input_input_small__MS1Mh _Input_input_icon__SFwu_" name="text_search_input" value="">
body > div#__next > div#catalog > div > header > div > div:eq(1) > div:eq(1) > div > div > div > input#text_search_input
0.00015	<div class="HeaderBottom_header-bottom_right__7W_NU"></div>
body > div#__next > div#catalog > div > header > div > div:eq(1) > div:eq(2)
0.00010	<div></div>
body > div#__next > div#catalog > div > main > div > div > section > div#filter-area > div > div > div > div:eq(3) > div:eq(0)
0.00009	<span class="CitySelectButton_city-text___XqH_"></span>,<button class="ButtonDeprecated_sklv-button__Wy8xr ButtonDeprecated_sklv-button_borderless__776ey" types="borderless" data-qa="header_shops_map_btn"></button>,<button class="ButtonDeprecated_sklv-button__Wy8xr HeaderTop_header-top_left-delivery__GG_8X" types=""></button>
body > div#__next > div#catalog > div > header > div > div:eq(0) > div:eq(1) > div:eq(1) > div:eq(0) > button > span,body > div#__next > div#catalog > div > header > div > div:eq(0) > div:eq(1) > div:eq(2) > a > button,body > div#__next > div#catalog > div > header > div > div:eq(0) > div:eq(1) > a > button
0.00004

The elements that have shifted place is highlighted in the image (that have a higher value than 0.01). If the element shifted outside of the viewport, you will not see it there. It can be hard to understand what content that has shifted, if that's the case, checkout the video or the filmstrip of the run.

Long Animation Frames

Read more about the Long Animation Frames API here here.

The top 10 longest animation frames entries

Server timings

There are no Server Timings.

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

CDP Performance

PageXray

How the page is built.

Largest assets on the page (by transfer size)

Requests and sizes per content type

Data per domain

Expires and last modified statistics

Requests loaded after onLoad event

Included requests done after load event end.

Requests loaded after onContentLoad

Includes requests done after DOM content loaded.

Render blocking requests

Render blocking information directly from Chrome.

Render information

CPU

Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.

Long Tasks

Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.

CPU last long task happened at 4.868 s

Individual Long Tasks

CPU time spent

Calculated using Tracium.

Time spent per request

CPU time spent

Third party

Third party requests categorised by Third party web version 0.24.0.

Unmatched third party domains

Here's a list of domains that didn't match any tool in Third party web. If you are sure they are third party domains, please do a PR to that project. You can also fine tune the list using --firstParty.

First party requests and sizes per content type

Calculated using .*sokolov.* (use --firstParty to configure).

Third party requests and sizes per content type

Screenshots

afterPageCompleteCheck.png

layoutShift.png

largestContentfulPaint.png

Axe

Axe is an accessibility testing engine for websites and other HTML-based user interfaces. Tested using axe-core version 4.10.0. Read more about axe-core .

Violations