Tested 2025-07-25 08:01:53 using Chrome 138.0.7204.49 (runtime settings).
| Metric | Value |
|---|---|
| Page metrics | |
| Performance score | 62 |
| Total page size | 3.6 MB |
| Requests | 71 |
| Timing metrics | |
| TTFB | 476 ms |
| First Paint | 784 ms |
| Fully Loaded | 7.104 s |
| Google Web Vitals | |
| TTFB | 476 ms |
| First Contentful Paint (FCP) | 784 ms |
| Largest Contentful Paint (LCP) | 1.104 s |
| Cumulative Layout Shift (CLS) | 0.00 |
| 200 ms | |
| Total Blocking Time | 158 ms |
| Max Potential FID | 116 ms |
| CPU metrics | |
| CPU long tasks | 7 |
| CPU last long task happens at | 3.346 s |
| Visual Metrics | |
| First Visual Change | 801 ms |
| Speed Index | 1.083 s |
| Visual Complete 85% | 1.101 s |
| Visual Complete 99% | 1.101 s |
| Last Visual Change | 1.101 s |
Use--filmstrip.showAll to show all filmstrips.
0 s0.6 sCPU Long Task duration 77 ms0.8 sFirst Contentful Paint 784 ms
0.9 sFirst Visual Change 801 msCPU Long Task duration 116 ms
1 sLayout Shift 0.00090 970 ms
1.1 sCPU Long Task duration 58 ms
1.2 sLast Visual Change 1.101 sVisual Complete 85% 1.101 sVisual Complete 95% 1.101 sVisual Complete 99% 1.101 sLCP <IMG> 1.104 sDOM Content Loaded Time 1.174 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.1.1.
| Title | Advice | Score | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Don't scale images in the browser (avoidScalingImages) | The page has 6 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. | 40 | |||||||||||||||
| 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: | |||||||||||||||||
| Avoid using Google Tag Manager. (googleTagManager) | The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page. | 0 | |||||||||||||||
| Description: Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance. | |||||||||||||||||
| Have a fast largest contentful paint (largestContentfulPaint) | You can add fetchPriority="high" to the image to increase the load priority in Chrome. | 95 | |||||||||||||||
| 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. | |||||||||||||||||
| Avoid CPU Long Tasks (longTasks) | The page has 7 CPU long tasks with the total of 535 ms. The total blocking time is 158 ms and 1 long task before first contentful paint with total time of 77 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 doing redirects (assetsRedirects) | The page has 6 redirects. 6 requests are from other domains, it could be 3rd-party assets doing unnecessary redirects. :( | 40 | |||||||||||||||
| 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 13 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 28.8 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 6 requests that have a shorter cache time than 30 days (but still a cache time). | 94 | |||||||||||||||
| 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: | |||||||||||||||||
| Always compress text content (compressAssets) | The page has 4 requests that are served uncompressed. You could save a lot of bytes by sending them compressed instead. | 60 | |||||||||||||||
| 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:
| |||||||||||||||||
| Avoid too many fonts (fewFonts) | The page has 3 font requests. Do you really need them? What value does the fonts give the user? | 70 | |||||||||||||||
| 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 image size shouldn't be too big (imageSize) | The page total image size is 2.4 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/. | 50 | |||||||||||||||
| Description: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user. | |||||||||||||||||
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 738.8 kB and the uncompressed size is 2.2 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: | |||||||||||||||||
| Make each CSS response small (optimalCssSize) | https://loyalty.vidi.ua/bundles/core/css/bootstrap_build/bootstrap.css?v1.4.720 size is 17.4 kB (17397) and that is bigger than the limit of 14.5 kB. https://loyalty.vidi.ua/bundles/core/css/core.prod.css?v1.4.720 size is 19.5 kB (19493) and that is bigger than the limit of 14.5 kB. https://loyalty.vidi.ua/bundles/my/css/style.css?v1.4.720 size is 14.7 kB (14677) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 70 | |||||||||||||||
| Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier. | |||||||||||||||||
Offenders:
| |||||||||||||||||
| Total page size shouldn't be too big (pageSize) | The page total transfer size is 3.8 MB, which is more than the coach limit of 2 MB. That is really big and you need to make it smaller. | 0 | |||||||||||||||
| Description: Avoid having pages that have a transfer size over the wire of more than 2 MB (desktop) and 1 MB (mobile) because that is really big and will hurt performance and will make the page expensive for the user if she/he pays for the bandwidth. | |||||||||||||||||
| Offenders: | |||||||||||||||||
| Don't use private headers on static content (privateAssets) | The page has 12 requests with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 0 | |||||||||||||||
| 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: | |||||||||||||||||
| 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. | ||
| Do not share user data with third parties. (thirdPartyPrivacy) | The page has 31% requests that are 3rd party (22 requests with a size of 587.3 kB). The page also have request to companies that harvest data from users and do not respect users privacy (see https://en.wikipedia.org/wiki/Surveillance_capitalism). The page do 4 tag-manager requests and uses 1 tag-manager tool. The page do 7 survelliance requests and uses 3 survelliance tools. The page do 1 analytics request and uses 1 analytics tool. The page do 13 utility requests and uses 1 utility tool. The page do 2 social requests and uses 1 social tool. The page do 2 ad requests and uses 1 ad tool. | 0 |
| Description: Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests. | ||
| Offenders: | ||
| Page info | |
|---|---|
| Title | Офіційний сайт родини Джуринських |
| Width | 1350 |
| Height | 4004 |
| DOM elements | 283 |
| Avg DOM depth | 9 |
| Max DOM depth | 13 |
| Iframes | 1 |
| Script tags | 5 |
| Local storage | 0 b |
| Session storage | 0 b |
| Network Information API | 4g |
| Resource Hints |
|---|
| preconnect |
| https://www.googletagmanager.com/ |
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.
| Technology | Confidence | Category |
|---|---|---|
| Microsoft ASP.NET | 100 | Web frameworks |
| Azure Front Door | 100 | Load balancers |
| Azure | 100 | PaaS |
| Nginx | 100 | Web servers Reverse proxies |
| HSTS | 100 | Security |
| HTTP/3 | 100 | Miscellaneous |
Data collected using Third Party Web 0.26.2
| Tag-manager |
|---|
| Google Tag Manager |
| Survelliance |
| Google Tag Manager |
| Google Analytics |
| Analytics |
| Google Analytics |
| Utility |
| Clarity |
| Social |
| Ad |
| Bing Ads |
| Visual Metrics | |
|---|---|
| First Visual Change | 801 ms |
| Speed Index | 1.083 s |
| Visual Complete 85% | 1.101 s |
| Visual Complete 95% | 1.101 s |
| Visual Complete 99% | 1.101 s |
| Last Visual Change | 1.101 s |
| Visual Readiness | 300 ms |
| Navigation Timing | |
|---|---|
| backEndTime | 476 ms |
| domContentLoadedTime | 1.174 s |
| domInteractiveTime | 1.174 s |
| domainLookupTime | 27 ms |
| frontEndTime | 2.934 s |
| pageDownloadTime | 1 ms |
| pageLoadTime | 3.410 s |
| redirectionTime | 0 ms |
| serverConnectionTime | 107 ms |
| serverResponseTime | 338 ms |
| Google Web Vitals | |
|---|---|
| Time to first byte (TTFB) | 476 ms |
| First Contentful Paint (FCP) | 784 ms |
| Largest Contentful Paint (LCP) | 1.104 s |
| Cumulative Layout Shift (CLS) | 0.00 |
| Interaction to next paint (INP) | 200 ms |
| Total Blocking Time (TBT) | 158 ms |
| Extra timings | |
|---|---|
| TTFB | 476 ms |
| First Paint | 784 ms |
| Load Event End | 3.411 s |
| Fully loaded | 7.104 s |
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 class="global_banner_img" src="/bundles/founders/img/home-banner.jpg?v1.4.720" alt=""> |
| Render time | 1.104 s |
| Element render delay | 153 ms |
| TTFB | 476 ms |
| Resource delay | 11 ms |
| Resource load duration | 465 ms |
| Load time | 958 ms |
| URL | https://dzhurynskyi....g/home-banner.jpg |
| Size (width*height) | 530506 |
| DOM path | |
| div > main#main > section:eq(0) > div > div > img> div > main#main > section:eq(0) > div > div > 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.
0.00090 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.00090 | <li class="header__dropdown__menu"></li>,<li class="header__dropdown__menu header__dropdown__menu-burger"></li>,<li class="header__dropdown__menu"></li>,<li class="header__dropdown__menu"></li> |
| body > div > header > div > div > nav > ul > li:eq(0),body > div > header > div > div > nav > ul > li:eq(1),body > div > header > div > div > nav > ul > li:eq(2),body > div > header > div > div > nav > ul > li:eq(3) | |
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.
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.
The measured latency was 200 ms.
| Event type | pointerover |
| Element type | IMG |
| Element class name | global_banner_img |
| Event target | div.container>div.global_banner_wrapper.global_banner_arrow>img.global_banner_img |
| Load state when the event happened | loading |
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 |
|---|---|---|---|---|
| 66.4 ms | 116.4 ms | 0 ms | 0 ms | 0 ms |
| https://www.googletagmanager.com/gtag/js?id=G-GMHEC3ZK39&cx=c>m=45He57n0v9187860044za200&tag_exp=101509157~103116026~103200004~103233427~104684208~104684211 | ||||
Invoker: https://www.googletagmanager.com/gtag/js?id=G-GMHEC3ZK39&cx=c>m=45He57n0v9187860044za200&tag_exp=101509157~103116026~103200004~103233427~104684208~104684211 | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 31.6 ms | 166.7 ms | 0.7 ms | 0.6 ms | 0.1 ms |
| https://www.googletagmanager.com/gtag/js?id=G-GMHEC3ZK39&cx=c>m=45He57n0v9187860044za200&tag_exp=101509157~103116026~103200004~103233427~104684208~104684211 | ||||
Invoker: Promise.resolve | ||||
| https://dzhurynskyi.com/dist/prod/founders/js/founders.js?v1.4.720 | ||||
Invoker: https://dzhurynskyi.com/dist/prod/founders/js/founders.js?v1.4.720 | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 16.1 ms | 15.2 ms | 57 ms | 57 ms | 0 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 89.3 ms | 1.1 ms | 0.1 ms | 1 ms |
| No availible script information. | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 70.1 ms | 0.3 ms | 0 ms | 0.3 ms |
| https://www.googletagmanager.com/gtm.js?id=GTM-NG92CK5W | ||||
Invoker: TimerHandler:setTimeout | ||||
| https://www.googletagmanager.com/gtm.js?id=GTM-NG92CK5W | ||||
Invoker: TimerHandler:setTimeout | ||||
| Blocking duration | Work duration | Render duration | PreLayout Duration | Style And Layout Duration |
|---|---|---|---|---|
| 0 ms | 70.4 ms | 0.4 ms | 0.3 ms | 0.1 ms |
| No availible script information. | ||||
There are no Server Timings.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
| name | value |
|---|---|
| AudioHandlers | 0 |
| AudioWorkletProcessors | 0 |
| Documents | 10 |
| Frames | 9 |
| JSEventListeners | 461 |
| LayoutObjects | 439 |
| MediaKeySessions | 0 |
| MediaKeys | 0 |
| Nodes | 6340 |
| Resources | 75 |
| ContextLifecycleStateObservers | 21 |
| V8PerContextDatas | 4 |
| WorkerGlobalScopes | 0 |
| UACSSResources | 0 |
| RTCPeerConnections | 0 |
| ResourceFetchers | 10 |
| AdSubframes | 0 |
| DetachedScriptStates | 0 |
| ArrayBufferContents | 21 |
| LayoutCount | 15 |
| RecalcStyleCount | 25 |
| LayoutDuration | 50 |
| RecalcStyleDuration | 26 |
| DevToolsCommandDuration | 41 |
| ScriptDuration | 914 |
| V8CompileDuration | 2 |
| TaskDuration | 1575 |
| TaskOtherDuration | 542 |
| ThreadTime | 1 |
| ProcessTime | 1 |
| JSHeapUsedSize | 16217916 |
| JSHeapTotalSize | 23855104 |
| FirstMeaningfulPaint | 1103 |
How the page is built.
| Summary | |
|---|---|
| HTTP version | HTTP/2.0 |
| Total requests | 71 |
| Total domains | 9 |
| Total transfer size | 3.6 MB |
| Total content size | 5.4 MB |
| Responses missing compression | 28 |
| Number of cookies | 3 |
| Third party cookies | 0 |
| Requests per response code | |
|---|---|
| 200 | 60 |
| 204 | 5 |
| 302 | 6 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 32.4 KB | 203.3 KB | 5 |
| css | 0 b | 79.8 KB | 362.8 KB | 11 |
| javascript | 0 b | 721.5 KB | 2.1 MB | 18 |
| image | 0 b | 2.3 MB | 2.3 MB | 16 |
| font | 0 b | 482.2 KB | 480.9 KB | 3 |
| svg | 0 b | 10.5 KB | 23.3 KB | 3 |
| plain | 1.8 KB | 46 B | 26 B | 7 |
| json | 0 b | 660 B | 26 B | 2 |
| Total | 1.8 KB | 3.6 MB | 5.4 MB | 65 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| dzhurynskyi.com | 6.825 s | 2.8 MB | 3.0 MB | 22 |
| www.googletagmanager.com | 98 ms | 465.1 KB | 1.3 MB | 4 |
| loyalty.vidi.ua | 4.879 s | 207.7 KB | 826.3 KB | 27 |
| region1.google-analytics.com | 26 ms | N/A | 0 b | 1 |
| www.clarity.ms | 408 ms | 32.3 KB | 73.8 KB | 3 |
| connect.facebook.net | 63 ms | 75.5 KB | 252.3 KB | 2 |
| d.clarity.ms | 1.288 s | 46 B | 26 B | 6 |
| c.clarity.ms | 399 ms | 633 B | 84 B | 4 |
| c.bing.com | 327 ms | N/A | 0 b | 2 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 year | 1 year |
| Last modified | 2 hours | 11 weeks | 1 year |
Included requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 5.2 KB | 3 |
| font | 0 b | 0 |
| plain | 0 b | 4 |
| Total | 5.2 KB | 9 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 26.1 KB | 4 |
| css | 72.8 KB | 9 |
| javascript | 440.4 KB | 14 |
| image | 12.8 KB | 6 |
| font | 0 b | 0 |
| json | 660 B | 2 |
| plain | 46 B | 6 |
| Total | 552.8 KB | 46 |
Third party requests categorised by Third party web version 0.26.2.
| Category | Requests |
|---|---|
| tag-manager | 4 |
| survelliance | 7 |
| analytics | 1 |
| utility | 13 |
| social | 2 |
| ad | 2 |
| Category | Number of tools |
|---|---|
| tag-manager | 1 |
| survelliance | 3 |
| analytics | 1 |
| utility | 1 |
| social | 1 |
| ad | 1 |
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.
| loyalty.vidi.ua |
Calculated using .*dzhurynskyi.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 6.3 KB | 33.7 KB | 1 |
| css | 0 b | 7.0 KB | 27.2 KB | 2 |
| javascript | 0 b | 48.0 KB | 143.8 KB | 2 |
| image | 0 b | 2.3 MB | 2.3 MB | 11 |
| font | 0 b | 482.2 KB | 480.9 KB | 3 |
| svg | 0 b | 10.5 KB | 23.3 KB | 3 |
| Total | N/A | 2.8 MB | 3.0 MB | 22 |
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 26.1 KB | 169.5 KB | 4 |
| css | 0 b | 72.8 KB | 335.7 KB | 9 |
| javascript | 0 b | 673.4 KB | 1.9 MB | 16 |
| image | 0 b | 8.2 KB | 6.8 KB | 5 |
| font | 0 b | 0 b | 0 b | 0 |
| plain | 1.8 KB | 46 B | 26 B | 7 |
| json | 0 b | 660 B | 26 B | 2 |
| Total | 1.7 KB | 781.2 KB | 2.4 MB | 49 |
afterPageCompleteCheck.png
layoutShift.png
largestContentfulPaint.png
