Page summary

Summary

Metric	Value
Page metrics
Performance Score	92
Total Page Transfer Size	224.7 KB
Requests	4
Timing metrics
TTFB [median]	41 ms
First Paint [median]	1.509 s
Fully Loaded [median]	1.476 s
Google Web Vitals
TTFB [median]	41 ms
First Contentful Paint (FCP) [median]	1.509 s
Largest Contentful Paint (LCP) [median]	1.509 s
Cumulative Layout Shift (CLS) [median]	0.00
Interaction To Next Paint (INP) [median]	264 ms
CPU metrics
CPU long tasks [median]	1
CPU longest task duration	285 ms
CPU last long task happens at	139 ms
Visual Metrics
First Visual Change [median]	1.500 s
Speed Index [median]	1.500 s
Visual Complete 85% [median]	1.500 s
Visual Complete 99% [median]	1.500 s
Last Visual Change [median]	1.500 s
Chrome User Experience Report (CRUX)
First Contentful Paint [p75]	1.963 s
Largest Contentful Paint (LCP) [p75]	2.437 s
Cumulative Layout Shift (CLS) [p75]	0.15

Timings Summary

Waterfall

Run 1 SpeedIndex median

Filmstrip

Use--filmstrip.showAll to show all filmstrips.

0 s

0.2 sCPU Long Task duration 252 msDOM Content Loaded Time 139 msPage Load Time 140 ms

1.5 sFully Loaded 1.476 sFirst Visual Change 1.500 sLast Visual Change 1.500 sVisual Complete 85% 1.500 sVisual Complete 95% 1.500 sVisual Complete 99% 1.500 s

1.6 sFirst Contentful Paint 1.509 sLCP <DIV> 1.509 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.1.1.

Coach score

• Total score 91
• Performance score 92
• Privacy score 88
• Best practice score 90

Performance advice (92)

Show/hide details

Title	Advice	Score
Avoid slowing down the critical rendering path (avoidRenderBlocking)	The page has 1 blocking requests and 0 in body parser blocking (1 JavaScript and 0 CSS).	90
Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path.
Offenders: https://www.585zolotoy.ru/__qrator/qauth.js
Avoid CPU Long Tasks (longTasks)	The page has 1 CPU long task with the total of 252 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 252 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.	80
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
Avoid extra requests by setting cache headers (cacheHeaders)	The page has 2 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 229.5 kB the next access.	80
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://www.585zolotoy.ru/__qrator/qauth.js https://www.585zolotoy.ru/qrerror/403.html
Always compress text content (compressAssets)	The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.	90
Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
Offenders: URL Transfer size Content size https://www.585zolotoy.ru/__qrator/qauth.js 222.9 KB 222.4 KB
Total JavaScript size shouldn't be too big (javascriptSize)	The total JavaScript transfer size is 228.2 kB. This is quite large.	50
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://www.585zolotoy.ru/__qrator/qauth.js 222.9 KB 222.4 KB
Avoid missing and error requests (responseOk)	The page has 3 error responses. The page has 1 response with code 401. The page has 2 responses with code 403.	70
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://www.585zolotoy.ru/ https://www.585zolotoy.ru/__qrator/validate...__qrator/validate https://www.585zolotoy.ru/qrerror/403.html

Best practice advice (90)

Show/hide details

Title	Advice	Score
Meta description (metaDescription)	The page is missing a meta description.	0
Description: Use a page description to make the page more relevant to search engines.
Avoid unnecessary headers (unnecessaryHeaders)	There are 3 responses that sets both a max-age and expires header. There are 3 responses that sets a pragma no-cache header (that is a request header). There are 4 responses that sets a server header.	90
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://www.585zolotoy.ru/ https://www.585zolotoy.ru/ https://www.585zolotoy.ru/ https://www.585zolotoy.ru/__qrator/qauth.js https://www.585zolotoy.ru/__qrator/qauth.js https://www.585zolotoy.ru/__qrator/qauth.js https://www.585zolotoy.ru/__qrator/validate...__qrator/validate https://www.585zolotoy.ru/__qrator/validate...__qrator/validate https://www.585zolotoy.ru/__qrator/validate...__qrator/validate https://www.585zolotoy.ru/qrerror/403.html

Privacy advice (88)

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://www.585zolotoy.ru/
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://www.585zolotoy.ru/

Page info

Page info
Title	HTTP 403
Width	1919
Height	912
DOM elements	18
Avg DOM depth	4
Max DOM depth	6
Iframes	0
Script tags	0
Local storage	0 b
Session storage	0 b
Network Information API	4g

Technologies used to build the page.

Data collected using Wappalyzer version 6.10.66. With updated code from Webappanalyzer 2024-12-27. Use --browsertime.firefox.includeResponseBodies htmlor --browsertime.chrome.includeResponseBodies htmlto help Wappalyzer find more information about technologies used.

Wappalyzer didn't find any information.

Data from run 1

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	DIV
Element/tag	<div class="guru"></div>
Render time	1.509 s
Elements that needed recalculate style before LCP	30
Time spent in recalculate style before LCP	2.053 ms
Load time	0 ms
Size (width*height)	17094
DOM path
div > div:eq(3) > div> div > div:eq(3) > 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.

Detected Cumulative Layout Shift

No layout shift detected.

Interaction to Next Paint

Interaction to Next Paint (INP) is a metric that try to measure responsiveness. It's useful if you are testing user journeys. Read more about Interaction to Next Paint.

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.

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

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 139 ms

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.26.2.

First party requests and sizes per content type

Calculated using .*585zolotoy.* (use --firstParty to configure).

Third party requests and sizes per content type

Axe

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

Violations

Median number of violations for all the runs. Check each individual run to see all the violations.

| loadingExperience ALL | | originLoadingExperience ALL | | 

CrUx

Chrome User Experience Report (CrUx) is powered by real user measurement across the public web, aggregated from users who have opted-in to syncing their browsing history, have not set up a Sync passphrase, and have usage statistic reporting enabled and is using Chrome.

The CrUx data has four different buckets (form factor) depending on device: DESKTOP, PHONE, TABLET and ALL. You can choose which data to get with --crux.formFactor.

Over the last 30 days, this is the field data for this page for Chrome users.

Form Factor ALL

Data collected between 2024-12-17 and 2025-1-13

Form factors

Navigation types

Distribution

All pages served from this origin

This is a summary of all pages served from this origin over the last 30 days for Chrome users.

Form Factor ALL

Data collected between 2024-12-17 and 2025-1-13

Form factors

Navigation types

Distribution