Tested 2024-10-17 05:09:42 using Chrome 129.0.6668.89 (runtime settings).
| Metric | Value |
|---|---|
| Page metrics | |
| Performance Score | 71 |
| Total Page Transfer Size | 1.4 MB |
| Requests | 84 |
| Timing metrics | |
| TTFB [median] | 358 ms |
| First Paint [median] | 822 ms |
| Fully Loaded [median] | 7.466 s |
| Google Web Vitals | |
| TTFB [median] | 358 ms |
| First Contentful Paint (FCP) [median] | 822 ms |
| Largest Contentful Paint (LCP) [median] | 2.103 s |
| Cumulative Layout Shift (CLS) [median] | 0.52 |
| Total Blocking Time [median] | 100 ms |
| Max Potential FID [median] | 98 ms |
| CPU metrics | |
| CPU long tasks [median] | 4 |
| CPU longest task duration | 117 ms |
| CPU last long task happens at | 2.025 s |
| Visual Metrics | |
| First Visual Change [median] | 833 ms |
| Speed Index [median] | 1.946 s |
| Visual Complete 85% [median] | 2.133 s |
| Visual Complete 99% [median] | 2.200 s |
| Last Visual Change [median] | 2.200 s |
| Metric | min | median | mean | max |
|---|---|---|---|---|
| Visual Metrics | ||||
| FirstVisualChange | 800 ms | 833 ms | 833 ms | 867 ms |
| LastVisualChange | 2.133 s | 2.200 s | 4.067 s | 7.867 s |
| SpeedIndex | 1.889 s | 1.946 s | 2.722 s | 4.330 s |
| VisualReadiness | 1.333 s | 1.367 s | 3.233 s | 7.000 s |
| VisualComplete85 | 2.133 s | 2.133 s | 3.955 s | 7.600 s |
| VisualComplete95 | 2.133 s | 2.133 s | 4.000 s | 7.733 s |
| VisualComplete99 | 2.133 s | 2.200 s | 4.067 s | 7.867 s |
| Google Web Vitals | ||||
| Time To First Byte (TTFB) | 335 ms | 358 ms | 364 ms | 398 ms |
| Largest Contentful Paint (LCP) | 2.099 s | 2.103 s | 2.102 s | 2.105 s |
| First Contentful Paint (FCP) | 786 ms | 822 ms | 820 ms | 853 ms |
| Cumulative Layout Shift (CLS) | 0.5157 | 0.5173 | 0.5173 | 0.5187 |
| More metrics | ||||
| firstPaint | 786 ms | 822 ms | 820 ms | 853 ms |
| loadEventEnd | 1.020 s | 1.050 s | 1.434 s | 2.232 s |
| CPU | ||||
| Total Blocking Time | 85 ms | 100 ms | 104 ms | 128 ms |
| Max Potential FID | 93 ms | 98 ms | 103 ms | 117 ms |
| CPU long tasks | 4 | 4 | 4 | 4 |
| CPU last long task happens at | 1.639 s | 2.025 s | 2.080 s | 2.576 s |
Run 3 SpeedIndex median
Use--filmstrip.showAll to show all filmstrips.
0 s
0.9 sLayout Shift 0.00134 821 msFirst Contentful Paint 822 msFirst Visual Change 833 msLayout Shift 0.00009 870 ms
1 sCPU Long Task duration 63 ms
1.1 sDOM Content Loaded Time 1.048 sPage Load Time 1.050 sCPU Long Task duration 68 ms
1.2 sLayout Shift 0.00903 1.182 s
1.3 sCPU Long Task duration 117 ms
1.4 sLayout Shift 0.47340 1.383 s
1.5 sLayout Shift 0.00004 1.418 s
1.6 sLayout Shift 0.00010 1.505 s
1.7 sCPU Long Task duration 80 ms
1.9 sLayout Shift 0.03318 1.857 sLayout Shift 0.00155 1.868 s
2 s
2.1 s
2.2 sLCP <DIV> 2.103 sVisual Complete 85% 2.133 sVisual Complete 95% 2.133 sLast Visual Change 2.200 sVisual Complete 99% 2.200 sThe 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.
| Title | Advice | Score | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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: | |||||||||||||||||||||||||||||
| Inline CSS for faster first render (inlineCss) | The page has both inline styles as well as it is requesting 8 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: | |||||||||||||||||||||||||||||
| Avoid CPU Long Tasks (longTasks) | The page has 4 CPU long tasks with the total of 285 ms. The total blocking time is 85 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. | 20 | |||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||
| Avoid Frontend single point of failures (spof) | The page has 8 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: | |||||||||||||||||||||||||||||
| Avoid doing redirects (assetsRedirects) | The page has 5 redirects. 5 requests are from other domains, it could be 3rd-party assets doing unnecessary redirects. :( | 50 | |||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 25 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 381.5 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: | |||||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||
| Total CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 72 kB and uncompressed size is 412.4 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: | |||||||||||||||||||||||||||||
| Avoid too many fonts (fewFonts) | The page has 5 font requests. Do you really need them? What value does the fonts give the user? | 50 | |||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||
| Avoid too many requests per domain [HTTP/1] (fewRequestsPerDomain) | The page has 1 domain that serves more than 30 requests. static-catalog.diamant.ru got 48 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: | |||||||||||||||||||||||||||||
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 555.4 kB and the uncompressed size is 1.9 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 2 misconfigured mime types. | 98 | |||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||
| Make each CSS response small (optimalCssSize) | https://static-catalog.diamant.ru/_next/static/css/1c31fb0e095aa8e0.css size is 42.9 kB (42855) 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:
| |||||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||
| 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: | ||
| 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: | ||
| 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 | |
|---|---|
| Title | Ювелирная компания Diamant. Официальный интернет магазин |
| Width | 485 |
| Height | 4948 |
| DOM elements | 525 |
| Avg DOM depth | 11 |
| Max DOM depth | 20 |
| Iframes | 0 |
| Script tags | 10 |
| Local storage | 18 B |
| Session storage | 312 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/ |
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 |
Data from run 3
| Visual Metrics | |
|---|---|
| First Visual Change | 833 ms |
| Speed Index | 1.946 s |
| Visual Complete 85% | 2.133 s |
| Visual Complete 95% | 2.133 s |
| Visual Complete 99% | 2.200 s |
| Last Visual Change | 2.200 s |
| Visual Readiness | 1.367 s |
| Navigation Timing | |
|---|---|
| backEndTime | 358 ms |
| domContentLoadedTime | 1.048 s |
| domInteractiveTime | 377 ms |
| domainLookupTime | 35 ms |
| frontEndTime | 690 ms |
| pageDownloadTime | 2 ms |
| pageLoadTime | 1.050 s |
| redirectionTime | 0 ms |
| serverConnectionTime | 119 ms |
| serverResponseTime | 202 ms |
| Google Web Vitals | |
|---|---|
| Time to first byte (TTFB) | 358 ms |
| First Contentful Paint (FCP) | 822 ms |
| Largest Contentful Paint (LCP) | 2.103 s |
| Cumulative Layout Shift (CLS) | 0.52 |
| Total Blocking Time (TBT) | 128 ms |
| First Contentful Paint info | |
|---|---|
| Elements that needed recalculate style before FCP | 113 |
| Time spent in recalculate style before FCP | 13.752 ms |
| Extra timings | |
|---|---|
| TTFB | 358 ms |
| First Paint | 822 ms |
| Load Event End | 1.050 s |
| Fully loaded | 7.466 s |
| User Timing measures | ||
|---|---|---|
| Name | Start time | Duration |
| Next.js-before-hydration | 0 ms | 1.045 s |
| Next.js-hydration | 1.045 s | 71 ms |
When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.
| Element type | DIV |
| Element/tag | <div class="image_lazy-load__Wso7t image_loaded__8YbPx SklvTextWithPhotoSlide_sklv-slide-text__img__FNQCx" style="background-image: url("https://sokolov.ru/upload/content/area/30fa72de39937cdeefcda67078ea8540.jpg?w=700&h=700");"></div> |
| Render time | 2.103 s |
| Elements that needed recalculate style before LCP | 2009 |
| Time spent in recalculate style before LCP | 97.968 ms |
| Load time | 2.103 s |
| URL | https://sokolov.ru/u...b08ced16539d4.jpg |
| Size (width*height) | 231830 |
| DOM path | |
| div#__next > div#catalog > div > main > div > div > div:eq(0) > div > div > div:eq(1) > div > div:eq(1) > a > div > div> div#__next > div#catalog > div > main > div > div > div:eq(0) > div > div > div:eq(1) > div > div:eq(1) > a > div > div> | |
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.
0.51872 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.47340 | <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 20 261 48" itemProp="logo"></svg>,<footer class="DiamantFooter_footer__tyY4h DiamantFooter_diamant_footer___i6wl" style="overflow: hidden;"></footer>,<button type="button" class="ButtonDeprecated_sklv-button__Wy8xr ButtonTemplate_button__mMa6w" data-qa="header_catalog_nav_open_btn"></button>,<button type="button" class="ButtonDeprecated_sklv-button__Wy8xr ButtonTemplate_button__mMa6w" data-qa="header_favorites_btn"></button>,<button type="button" class="ButtonDeprecated_sklv-button__Wy8xr ButtonTemplate_button__mMa6w" data-qa="header_to_basket_btn"></button> |
| body > div#__next > div#catalog > div > header > div:eq(1) > div > div:eq(1) > div:eq(1) > svg:eq(1),body > div#__next > div#catalog > div > footer,body > div#__next > div#catalog > div > div:eq(0) > button:eq(1),body > div#__next > div#catalog > div > div:eq(0) > button:eq(2),body > div#__next > div#catalog > div > div:eq(0) > button:eq(3) | |
| 0.03318 | <main class="mainLayout_main__L9rDe"></main>,<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" fill="none" viewBox="0 0 24 24"></svg> |
| body > div#__next > div#catalog > div > main,body > div#__next > div#catalog > div > header > div:eq(0) > button > svg | |
| 0.00903 | <body data-diamant="true"></body>,<span class="ButtonTemplate_button-text__hHkJB"></span>,<span class="ButtonTemplate_button-text__hHkJB"></span> |
| body,body > div#__next > div#catalog > div > div:eq(0) > button:eq(1) > span,body > div#__next > div#catalog > div > div:eq(0) > button:eq(2) > span | |
| 0.00155 | <h2 class="Main_sklv-main-title__nFynB TileSlider_sklv-tile-slider__title__N8UsM"></h2> |
| body > div#__next > div#catalog > div > main > div > div > section:eq(0) > h2 | |
| 0.00134 | |
| 0.00010 | <span class="ButtonTemplate_button-text__hHkJB"></span>,<span class="ButtonTemplate_button-text__hHkJB"></span> |
| body > div#__next > div#catalog > div > div:eq(0) > button:eq(3) > span,body > div#__next > div#catalog > div > div:eq(0) > button:eq(4) > span | |
| 0.00009 | |
| 0.00004 | <span class="ButtonTemplate_button-text__hHkJB"></span> |
| body > div#__next > div#catalog > div > div:eq(0) > button:eq(0) > span | |
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.
Read more about the Long Animation Frames API here here.
The top 10 longest animation frames entries
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 73 ms | 127.9 ms | 5.1 ms | 2.3 ms | 2.8 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/2534.7b70be949c8adac1.js | ||||
Forced Style And Layout Duration: 39 ms Invoker: https://static-catalog.diamant.ru/_next/static/chunks/2534.7b70be949c8adac1.js | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 36 ms | 101.8 ms | 5.2 ms | 2.6 ms | 2.6 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
Invoker: MessagePort.onmessage | ||||
| https://cdn.diginetica.net/5183/client.js | ||||
Invoker: https://cdn.diginetica.net/5183/client.js | ||||
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
Invoker: MessagePort.onmessage | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 21 ms | 68.8 ms | 3.2 ms | 0.1 ms | 3.1 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
Invoker: MessagePort.onmessage | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 14 ms | 63.7 ms | 0.3 ms | 0 ms | 0.3 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/main-8933f27b2dfdcc1f.js | ||||
Invoker: https://static-catalog.diamant.ru/_next/static/chunks/main-8933f27b2dfdcc1f.js | ||||
| https://static-catalog.diamant.ru/_next/static/chunks/pages/_app-1547296f7ac5ca4a.js | ||||
Invoker: https://static-catalog.diamant.ru/_next/static/chunks/pages/_app-1547296f7ac5ca4a.js | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 425.8 ms | 24.2 ms | 0.1 ms | 24.1 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 83.7 ms | 4.3 ms | 0.5 ms | 3.8 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
Invoker: MessagePort.onmessage | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 59 ms | 2 ms | 0.3 ms | 1.7 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 86 ms | 3 ms | 0.5 ms | 2.5 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
Forced Style And Layout Duration: 2 ms Invoker: MessagePort.onmessage | ||||
There are no Server Timings.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Summary | |
|---|---|
| HTTP version | HTTP/1.1 |
| Total requests | 84 |
| Total domains | 7 |
| Total transfer size | 1.4 MB |
| Total content size | 3.0 MB |
| Responses missing compression | 29 |
| Number of cookies | 10 |
| Third party cookies | 0 |
| Requests per response code | |
|---|---|
| 200 | 78 |
| 302 | 5 |
| 404 | 1 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 484 B | 8.9 KB | 29.4 KB | 1 |
| css | 0 b | 70.3 KB | 402.7 KB | 8 |
| javascript | 555 B | 542.4 KB | 1.8 MB | 38 |
| image | 0 b | 512.5 KB | 509.5 KB | 9 |
| font | 0 b | 259.6 KB | 257.8 KB | 5 |
| json | 3.2 KB | 9.5 KB | 9.6 KB | 13 |
| favicon | 0 b | 1.4 KB | 9.4 KB | 1 |
| other | 0 b | 0 b | 0 b | 2 |
| svg | 0 b | 894 B | 680 B | 1 |
| Total | 4.3 KB | 1.4 MB | 3.0 MB | 78 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| diamant.ru | 2.266 s | 17.1 KB | 38.3 KB | 10 |
| cdn.sokolov.ru | 3.127 s | 772.0 KB | 767.2 KB | 14 |
| static-catalog.diamant.ru | 7.066 s | 486.9 KB | 1.6 MB | 48 |
| seo.sokolov.ru | 622 ms | 621 B | 93 B | 5 |
| sokolov.ru | 1.524 s | 0 b | 0 b | 5 |
| cdn.diginetica.net | 492 ms | 129.0 KB | 543.0 KB | 1 |
| autocomplete.diginetica.net | 268 ms | 363 B | 2 B | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 year | 1 year |
| Last modified | 24 hours | 1 week | 38 weeks |
Included requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 28.5 KB | 7 |
| javascript | 277.8 KB | 31 |
| image | 512.5 KB | 9 |
| font | 51.4 KB | 1 |
| json | 9.5 KB | 13 |
| favicon | 1.4 KB | 1 |
| other | 0 b | 2 |
| svg | 894 B | 1 |
| Total | 882.5 KB | 71 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 28.5 KB | 7 |
| javascript | 277.8 KB | 31 |
| image | 512.5 KB | 9 |
| font | 51.4 KB | 1 |
| json | 9.5 KB | 13 |
| favicon | 1.4 KB | 1 |
| other | 0 b | 2 |
| svg | 894 B | 1 |
| Total | 882.5 KB | 71 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 0 | 0 | 0 |
Download the Chrome trace log and drag and drop it into Developer Tools / Performance in Chrome.
Collected using the Long Task API. A long task is a task that take 50 milliseconds or more.
| Type | Quantity | Total duration (ms) |
|---|---|---|
| Total Blocking Time | 128 | |
| Max Potential First Input Delay | 117 | |
| Long Tasks before First Paint | 0 | 0 |
| Long Tasks before First Contentful Paint | 0 | 0 |
| Long Tasks before Largest Contentful Paint | 4 | 328 |
| Long Tasks after Load Event End | 3 | 265 |
| Total Long Tasks | 4 | 328 |
CPU last long task happened at 1.639 s
| name | startTime | duration | containerId | containerName | containerSrc | containerType |
|---|---|---|---|---|---|---|
| self | 987 | 63 | window | |||
| self | 1052 | 68 | window | |||
| self | 1262 | 117 | window | |||
| self | 1639 | 80 | window |
Calculated using Tracium.
| Categories (ms) | |
|---|---|
| parseHTML | 10 |
| styleLayout | 211 |
| paintCompositeRender | 206 |
| scriptParseCompile | 1 |
| scriptEvaluation | 682 |
| garbageCollection | 17 |
| other | 453 |
| Events (ms) | |
|---|---|
| FunctionCall | 466 |
| RunTask | 238 |
| UpdateLayoutTree | 166 |
| Paint | 131 |
| v8.run | 93 |
| RunMicrotasks | 76 |
| Layerize | 66 |
| PaintImage | 47 |
| Layout | 44 |
| Commit | 43 |
| PrePaint | 32 |
| UpdateLayer | 27 |
| URLLoader::Context::OnReceivedResponse | 26 |
| IntersectionObserverController::computeIntersections | 13 |
| v8.callFunction | 10 |
| Tool/domain | Time (ms) |
|---|---|
| static-catalog.diamant.ru | 748.6 |
| cdn.diginetica.net | 80.7 |
Third party requests categorised by Third party web version 0.24.0.
| Category | Requests |
|---|
| Category | Number of tools |
|---|
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.
| cdn.sokolov.ru |
| seo.sokolov.ru |
| cdn.diginetica.net |
| autocomplete.diginetica.net |
| sokolov.ru |
Calculated using .*diamant.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 484 B | 8.9 KB | 29.4 KB | 1 |
| css | 0 b | 70.3 KB | 402.7 KB | 8 |
| javascript | 0 b | 413.3 KB | 1.2 MB | 37 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| json | 3.2 KB | 8.5 KB | 9.5 KB | 9 |
| favicon | 0 b | 1.4 KB | 9.4 KB | 1 |
| svg | 0 b | 894 B | 680 B | 1 |
| Total | 4.0 KB | 504.0 KB | 1.7 MB | 58 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 0 b | 0 b | 0 |
| javascript | 555 B | 129.0 KB | 543.0 KB | 1 |
| image | 0 b | 512.5 KB | 509.5 KB | 9 |
| font | 0 b | 259.6 KB | 257.8 KB | 5 |
| other | 0 b | 0 b | 0 b | 2 |
| json | 0 b | 984 B | 95 B | 4 |
| Total | 1.9 KB | 902.0 KB | 1.3 MB | 26 |
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 .
Median number of violations for all the runs. Check each individual run to see all the violations.
| Type | Violations (median) |
|---|---|
| Critical | 2 (6 issues) |
| Serious | 2 (12 issues) |
| Moderate | 1 (1 issues) |
| Minor | 0 (0 issues) |
