Tested 2024-10-17 09:11:42 using Chrome 129.0.6668.89 (runtime settings).
| Metric | Value |
|---|---|
| Page metrics | |
| Performance Score | 68 |
| Total Page Transfer Size | 1.1 MB |
| Requests | 100 |
| Timing metrics | |
| TTFB [median] | 328 ms |
| First Paint [median] | 858 ms |
| Fully Loaded [median] | 6.627 s |
| Google Web Vitals | |
| TTFB [median] | 328 ms |
| First Contentful Paint (FCP) [median] | 858 ms |
| Largest Contentful Paint (LCP) [median] | 2.358 s |
| Cumulative Layout Shift (CLS) [median] | 0.05 |
| Total Blocking Time [median] | 547 ms |
| Max Potential FID [median] | 292 ms |
| CPU metrics | |
| CPU long tasks [median] | 11 |
| CPU longest task duration | 341 ms |
| CPU last long task happens at | 2.765 s |
| Visual Metrics | |
| First Visual Change [median] | 867 ms |
| Speed Index [median] | 3.045 s |
| Visual Complete 85% [median] | 6.567 s |
| Visual Complete 99% [median] | 7.033 s |
| Last Visual Change [median] | 7.033 s |
| Metric | min | median | mean | max |
|---|---|---|---|---|
| Visual Metrics | ||||
| FirstVisualChange | 833 ms | 867 ms | 856 ms | 867 ms |
| LastVisualChange | 6.933 s | 7.033 s | 7.055 s | 7.200 s |
| SpeedIndex | 2.990 s | 3.045 s | 3.035 s | 3.069 s |
| VisualReadiness | 6.066 s | 6.200 s | 6.200 s | 6.333 s |
| VisualComplete85 | 6.467 s | 6.567 s | 6.623 s | 6.834 s |
| VisualComplete95 | 6.467 s | 6.567 s | 6.623 s | 6.834 s |
| VisualComplete99 | 6.933 s | 7.033 s | 7.055 s | 7.200 s |
| Google Web Vitals | ||||
| Time To First Byte (TTFB) | 304 ms | 328 ms | 350 ms | 417 ms |
| Largest Contentful Paint (LCP) | 2.327 s | 2.358 s | 2.428 s | 2.598 s |
| First Contentful Paint (FCP) | 825 ms | 858 ms | 857 ms | 889 ms |
| Cumulative Layout Shift (CLS) | 0.0337 | 0.0459 | 0.0431 | 0.0498 |
| More metrics | ||||
| firstPaint | 825 ms | 858 ms | 857 ms | 889 ms |
| loadEventEnd | 1.009 s | 1.064 s | 1.062 s | 1.114 s |
| CPU | ||||
| Total Blocking Time | 471 ms | 547 ms | 531 ms | 576 ms |
| Max Potential FID | 277 ms | 292 ms | 303 ms | 341 ms |
| CPU long tasks | 11 | 11 | 11 | 12 |
| CPU last long task happens at | 2.711 s | 2.765 s | 2.787 s | 2.885 s |
Run 2 SpeedIndex median
Use--filmstrip.showAll to show all filmstrips.
0 s
0.9 sFirst Contentful Paint 858 msFirst Visual Change 867 ms1 sCPU Long Task duration 76 ms1.1 sDOM Content Loaded Time 1.060 sPage Load Time 1.063 sCPU Long Task duration 116 ms1.2 sCPU Long Task duration 68 ms
1.3 s
1.4 s
1.5 s
1.6 s
1.7 s
1.8 sCPU Long Task duration 292 ms
1.9 s
2 s
2.1 sCPU Long Task duration 50 ms
2.2 sCPU Long Task duration 62 ms2.3 sCPU Long Task duration 80 ms
2.4 sLCP <> 2.358 sCPU Long Task duration 59 ms2.5 sCPU Long Task duration 110 ms2.6 sCPU Long Task duration 50 ms
2.8 sCPU Long Task duration 58 msLayout Shift 0.03278 2.777 s
2.9 sLayout Shift 0.00087 2.803 s
3 s6.4 sFully Loaded 6.329 s
6.6 sVisual Complete 85% 6.567 sVisual Complete 95% 6.567 s
6.7 s
6.8 s
6.9 s
7 sLast Visual Change 6.933 sVisual Complete 99% 6.933 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 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: | ||||||||
| 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 can be improved 2.598 s. It is in the Google Web Vitals needs improvement range, slower than 2.5 seconds. | 80 | ||||||
| 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: | ||||||||
| Avoid CPU Long Tasks (longTasks) | The page has 11 CPU long tasks with the total of 1.097 s. The total blocking time is 547 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: | ||||||||
| Avoid Frontend single point of failures (spof) | The page has 12 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 extra requests by setting cache headers (cacheHeaders) | The page has 28 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 222.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: | ||||||||
| 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 75.5 kB and uncompressed size is 404.3 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 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: | ||||||||
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 584.1 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:
| ||||||||
| Don't use private headers on static content (privateAssets) | The page has 3 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. | 80 | ||||||
| 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: | ||||||||
| 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 | 15577 |
| DOM elements | 2781 |
| Avg DOM depth | 15 |
| Max DOM depth | 20 |
| Iframes | 0 |
| Script tags | 13 |
| Local storage | 18 B |
| Session storage | 315 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 |
|---|---|---|
| Nginx | 100 | Web servers Reverse proxies |
| Amazon Web Services | 100 | PaaS |
| HSTS | 100 | Security |
Data from run 2
| Visual Metrics | |
|---|---|
| First Visual Change | 867 ms |
| Speed Index | 3.045 s |
| Visual Complete 85% | 6.567 s |
| Visual Complete 95% | 6.567 s |
| Visual Complete 99% | 6.933 s |
| Last Visual Change | 6.933 s |
| Visual Readiness | 6.066 s |
| Navigation Timing | |
|---|---|
| backEndTime | 328 ms |
| domContentLoadedTime | 1.060 s |
| domInteractiveTime | 359 ms |
| domainLookupTime | 33 ms |
| frontEndTime | 709 ms |
| pageDownloadTime | 26 ms |
| pageLoadTime | 1.063 s |
| redirectionTime | 0 ms |
| serverConnectionTime | 129 ms |
| serverResponseTime | 187 ms |
| Google Web Vitals | |
|---|---|
| Time to first byte (TTFB) | 328 ms |
| First Contentful Paint (FCP) | 858 ms |
| Largest Contentful Paint (LCP) | 2.358 s |
| Cumulative Layout Shift (CLS) | 0.03 |
| Total Blocking Time (TBT) | 471 ms |
| First Contentful Paint info | |
|---|---|
| Elements that needed recalculate style before FCP | 149 |
| Time spent in recalculate style before FCP | 23.571 ms |
| Extra timings | |
|---|---|
| TTFB | 328 ms |
| First Paint | 858 ms |
| Load Event End | 1.064 s |
| Fully loaded | 6.329 s |
| User Timing measures | ||
|---|---|---|
| Name | Start time | Duration |
| Next.js-before-hydration | 0 ms | 1.055 s |
| Next.js-hydration | 1.055 s | 122 ms |
When in time the page main content is rendered (collected using the Largest Contentful Paint API). Read more about Largest Contentful Paint.
| Render time | 2.358 s |
| Elements that needed recalculate style before LCP | 5226 |
| Time spent in recalculate style before LCP | 253.602 ms |
| Load time | 2.358 s |
| URL | https://pmdn.sokolov...F613A12CB8308.jpg |
| Size (width*height) | 48180 |
| DOM path | |
| <> | |
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.03366 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.03278 | <main class="mainLayout_main__L9rDe"></main>,<button class="TopLine_promo-topline__close__NxqbX"></button>,<div class="Header_header__inner__wmRSn Header_header_catalog___9RZY"></div> |
| body > div#__next > div#catalog > div > main,body > div#__next > div#catalog > div > header > div:eq(0) > button,body > div#__next > div#catalog > div > header > div:eq(1) | |
| 0.00087 | <button class="TopLine_promo-topline__close__NxqbX"></button>,<div class="Header_header__inner__wmRSn Header_header_catalog___9RZY"></div> |
| body > div#__next > div#catalog > div > header > div:eq(0) > button,body > div#__next > div#catalog > div > header > div:eq(1) | |
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 |
|---|---|---|---|---|
| 263 ms | 295.6 ms | 20.4 ms | 0.1 ms | 20.3 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/pages/_app-dada61507e705775.js | ||||
Forced Style And Layout Duration: 132 ms Invoker: Response.json.then | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 95 ms | 183.5 ms | 25.5 ms | 0.1 ms | 25.4 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 76 ms | 118.7 ms | 9.3 ms | 0 ms | 9.3 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 |
|---|---|---|---|---|
| 40 ms | 119.2 ms | 9.8 ms | 4.9 ms | 4.9 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 | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 26 ms | 76 ms | 0 ms | 0 ms | 0 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/pages/_app-dada61507e705775.js | ||||
Invoker: https://static-catalog.diamant.ru/_next/static/chunks/pages/_app-dada61507e705775.js | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 23 ms | 79 ms | 5 ms | 0 ms | 5 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
Forced Style And Layout Duration: 3 ms Invoker: MessagePort.onmessage | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 20 ms | 73.7 ms | 11.3 ms | 0.3 ms | 11 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
Forced Style And Layout Duration: 54 ms Invoker: MessagePort.onmessage | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 15 ms | 100.4 ms | 13.6 ms | 0 ms | 13.6 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 |
|---|---|---|---|---|
| 13 ms | 77.2 ms | 0.8 ms | 0.1 ms | 0.7 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 |
|---|---|---|---|---|
| 6 ms | 67.7 ms | 5.3 ms | 0.1 ms | 5.2 ms |
| https://static-catalog.diamant.ru/_next/static/chunks/framework-aaff1786eadd4e8b.js | ||||
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/2.0 |
| Total requests | 100 |
| Total domains | 9 |
| Total transfer size | 1.1 MB |
| Total content size | 4.9 MB |
| Responses missing compression | 44 |
| Number of cookies | 14 |
| Third party cookies | 0 |
| Requests per response code | |
|---|---|
| 200 | 96 |
| 206 | 3 |
| 404 | 1 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 10.6 KB | 37.6 KB | 1 |
| css | 0 b | 73.7 KB | 394.8 KB | 12 |
| javascript | 555 B | 570.4 KB | 1.8 MB | 44 |
| image | 0 b | 174.0 KB | 171.1 KB | 11 |
| font | 0 b | 208.2 KB | 206.8 KB | 4 |
| plain | 0 b | 0 b | 0 b | 2 |
| json | 0 b | 53.3 KB | 330.0 KB | 18 |
| 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 |
| video | 0 b | 13.5 KB | 2.0 MB | 3 |
| Total | 555 B | 1.1 MB | 4.9 MB | 99 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| diamant.ru | 2.643 s | 30.5 KB | 90.1 KB | 14 |
| cdn.sokolov.ru | 1.602 s | 218.6 KB | 216.9 KB | 5 |
| static-catalog.diamant.ru | 8.112 s | 518.2 KB | 1.7 MB | 58 |
| catalog.sokolov.ru | 942 ms | 32.4 KB | 276.9 KB | 4 |
| seo.sokolov.ru | 378 ms | 414 B | 62 B | 4 |
| cdn.diginetica.net | 372 ms | 129.0 KB | 543.0 KB | 1 |
| pmdn.sokolov.io | 1.885 s | 163.7 KB | 161.0 KB | 10 |
| autocomplete.diginetica.net | 241 ms | 363 B | 2 B | 1 |
| 2pmdn.sokolov.io | 2.019 s | 13.5 KB | 2.0 MB | 3 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 year | 1 year |
| Last modified | 4 hours | 1 week | 43 weeks |
Included requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 25.9 KB | 9 |
| javascript | 293.5 KB | 35 |
| image | 174.0 KB | 11 |
| font | 0 b | 0 |
| plain | 0 b | 2 |
| json | 53.3 KB | 18 |
| favicon | 1.4 KB | 1 |
| other | 0 b | 2 |
| svg | 894 B | 1 |
| video | 13.5 KB | 3 |
| Total | 563.3 KB | 83 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 25.9 KB | 9 |
| javascript | 293.5 KB | 35 |
| image | 174.0 KB | 11 |
| font | 0 b | 0 |
| plain | 0 b | 2 |
| json | 53.3 KB | 18 |
| favicon | 1.4 KB | 1 |
| other | 0 b | 2 |
| svg | 894 B | 1 |
| video | 13.5 KB | 3 |
| Total | 563.3 KB | 83 |
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 | 471 | |
| Max Potential First Input Delay | 292 | |
| Long Tasks before First Paint | 0 | 0 |
| Long Tasks before First Contentful Paint | 0 | 0 |
| Long Tasks before Largest Contentful Paint | 7 | 744 |
| Long Tasks after Load Event End | 10 | 945 |
| Total Long Tasks | 11 | 1021 |
CPU last long task happened at 2.711 s
| name | startTime | duration | containerId | containerName | containerSrc | containerType |
|---|---|---|---|---|---|---|
| self | 962 | 76 | window | |||
| self | 1065 | 116 | window | |||
| self | 1199 | 68 | window | |||
| self | 1763 | 292 | window | |||
| self | 2083 | 50 | window | |||
| self | 2163 | 62 | window | |||
| self | 2276 | 80 | window | |||
| self | 2380 | 59 | window | |||
| self | 2445 | 110 | window | |||
| self | 2582 | 50 | window | |||
| self | 2711 | 58 | window |
Calculated using Tracium.
| Categories (ms) | |
|---|---|
| parseHTML | 19 |
| styleLayout | 372 |
| paintCompositeRender | 50 |
| scriptParseCompile | 2 |
| scriptEvaluation | 1227 |
| garbageCollection | 56 |
| other | 371 |
| Events (ms) | |
|---|---|
| FunctionCall | 900 |
| UpdateLayoutTree | 254 |
| RunTask | 175 |
| RunMicrotasks | 157 |
| Layout | 117 |
| v8.run | 95 |
| URLLoader::Context::OnReceivedResponse | 48 |
| Paint | 40 |
| PrePaint | 39 |
| IntersectionObserverController::computeIntersections | 34 |
| V8.GC_SCAVENGER_SCAVENGE_PARALLEL | 29 |
| Layerize | 23 |
| V8.HandleInterrupts | 19 |
| V8.BytecodeBudgetInterrupt | 14 |
| URLLoader::Context::OnCompletedRequest | 14 |
| v8.callFunction | 11 |
| Commit | 11 |
| Tool/domain | Time (ms) |
|---|---|
| static-catalog.diamant.ru | 1453.7 |
| cdn.diginetica.net | 79.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 |
| catalog.sokolov.ru |
| seo.sokolov.ru |
| cdn.diginetica.net |
| pmdn.sokolov.io |
| autocomplete.diginetica.net |
| 2pmdn.sokolov.io |
Calculated using .*diamant.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 10.6 KB | 37.6 KB | 1 |
| css | 0 b | 73.7 KB | 394.8 KB | 12 |
| javascript | 0 b | 441.3 KB | 1.3 MB | 43 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| json | 0 b | 20.1 KB | 53.0 KB | 13 |
| favicon | 0 b | 1.4 KB | 9.4 KB | 1 |
| svg | 0 b | 894 B | 680 B | 1 |
| Total | N/A | 548.7 KB | 1.8 MB | 72 |
| 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 | 174.0 KB | 171.1 KB | 11 |
| font | 0 b | 208.2 KB | 206.8 KB | 4 |
| plain | 0 b | 0 b | 0 b | 2 |
| other | 0 b | 0 b | 0 b | 2 |
| json | 0 b | 33.2 KB | 277.0 KB | 5 |
| video | 0 b | 13.5 KB | 2.0 MB | 3 |
| Total | 528 B | 558.0 KB | 3.2 MB | 28 |
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 (148 issues) |
| Serious | 2 (304 issues) |
| Moderate | 0 (0 issues) |
| Minor | 0 (0 issues) |
