C — https://kharkov.ua | BeaverCheck Audit

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

HSTS · 2189 peers

You 76

Avg 74

At average

0 50 100

Better than 65% of HSTS sites See full HSTS benchmark →

Apache · 424 peers

You 76

Avg 72

At average

0 50 100

Better than 80% of Apache sites See full Apache benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

Cookie 'PHPSESSID' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

13 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

4 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fkharkov.ua)](https://beavercheck.com/results/0d7b6038-78c8-4a59-a895-25e3d554da7f)

HTML

<a href="https://beavercheck.com/results/0d7b6038-78c8-4a59-a895-25e3d554da7f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkharkov.ua" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fkharkov.ua

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~23%.

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

4 form field(s) without a label

+6% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (2)

13 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

₴5,400 investment → ₴4.93/month returns

Payback period: > 2 years First-year ROI: -99%

Investment

₴5,400

4h · 5 findings

Monthly returns

₴4.93 /mo

~₴59 / year

Bandwidth savings ₴4.93

Regulatory risk avoided

No applicable regulations in this jurisdiction

₴1,800 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

₴5,400

4.5 developer hours at ₴1200/hr

Based on Ukraine rates (₴1200/hr)

Quick wins

₴1,800 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

₴ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

₴4.93 / month at risk

~₴59 / year if left unfixed

Bandwidth Waste

₴4.93 /mo

1479.4 MB/mo × 3.333 UAH/GB

Optimize transfer: save ~148 KB per page load
Saves ₴4.93/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.12 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.43 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.983

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.37 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.43 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.983475] map[node:map[boundingRect:map[bottom:2577 height:2569 left:0 right:412 top:8 width:412] lhId:page-29-BODY nodeLabel:body path:1,HTML,1,BODY selector:body snippet:<body> type:node] score:0.891612 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:234 height:16 left:2 right:135 top:218 width:133] lhId:page-39-IMG nodeLabel:div.sixt > div > a.nob > img path:1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div.sixt > div > a.nob > img snippet:<img alt="" src="/img/lnk1.png" style="margin-top:1px; border: 0;"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:2467 height:2169 left:0 right:412 top:298 width:412] lhId:page-27-DIV nodeLabel:Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… path:1,HTML,1,BODY,3,DIV selector:body > div snippet:<div style="max-width: 798px; margin: 0px auto 10px; background: rgb(229, 228, 222); display: table;"> type:node] score:0.061878 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:234 height:16 left:2 right:135 top:218 width:133] lhId:page-39-IMG nodeLabel:div.sixt > div > a.nob > img path:1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div.sixt > div > a.nob > img snippet:<img alt="" src="/img/lnk1.png" style="margin-top:1px; border: 0;"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:693 height:118 left:3 right:139 top:575 width:136] lhId:page-34-DIV nodeLabel:Харьков +3° влажн.: 68% давл.: 743 мм 0 м/с path:1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,DIV,25,A,0,DIV,1,DIV,1,DIV selector:a > div#SinoptikInformer > div.siBody > div.siCity snippet:<div class="siCity"> type:node] score:0.013544] map[node:map[boundingRect:map[bottom:2467 height:2169 left:0 right:412 top:298 width:412] lhId:page-27-DIV nodeLabel:Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… path:1,HTML,1,BODY,3,DIV selector:body > div snippet:<div style="max-width: 798px; margin: 0px auto 10px; background: rgb(229, 228, 222); display: table;"> type:node] score:0.006405 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:234 height:16 left:276 right:409 top:218 width:133] lhId:page-44-IMG nodeLabel:div.sixt > div > a.nob > img path:1,HTML,1,BODY,2,DIV,2,DIV,0,DIV,0,A,0,IMG selector:div.sixt > div > a.nob > img snippet:<img alt="" src="/img/lnk3.png" style="margin-top:1px; border: 0;"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:2467 height:2169 left:0 right:412 top:298 width:412] lhId:page-27-DIV nodeLabel:Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… path:1,HTML,1,BODY,3,DIV selector:body > div snippet:<div style="max-width: 798px; margin: 0px auto 10px; background: rgb(229, 228, 222); display: table;"> type:node] score:0.003476 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:254 height:16 left:276 right:409 top:238 width:133] lhId:page-42-IMG nodeLabel:div.sixt > div > a.nob > img path:1,HTML,1,BODY,2,DIV,5,DIV,0,DIV,0,A,0,IMG selector:div.sixt > div > a.nob > img snippet:<img alt="" src="/img/lnk6.png" style="margin-top:1px; border: 0;"> type:node]]] type:subitems]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Велодень в Харькове. `li > noindex > a > img`	www.kharkov.ua/cache/649.jpeg	43.0 KiB	38.8 KiB
Новая полиция начала работу в Харькове `li > noindex > a > img`	www.kharkov.ua/cache/650.jpeg	29.7 KiB	25.6 KiB
images/kharlogo.png `body > div > div`	www.kharkov.ua/images/gosprbkg.jpg	51.7 KiB	25.0 KiB
Станция метро ?Победа? в Харькове официально открыта `li > noindex > a > img`	www.kharkov.ua/cache/651.jpeg	22.6 KiB	18.5 KiB
images/kharlogo.png `div.logo > div > a.nob > img`	www.kharkov.ua/images/kharlogo.png	15.8 KiB	13.3 KiB
div.siCity > div#siCont0 > div.siLeft > div#weatherIco0 `div.siCity > div#siCont0 > div.siLeft > div#weatherIco0`	sinoptik.ua/resources/legacy/informers/s-informers-t2.png	33.0 KiB	12.6 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn10.png	9.7 KiB	8.8 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn3_.png	9.6 KiB	8.8 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn1_.png	9.6 KiB	8.7 KiB
images/lira1.png `div.thumb_wrapper > div.thumbd3 > div > img`	www.kharkov.ua/images/lira1.png	11.2 KiB	8.7 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn4.png	9.5 KiB	8.6 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn2.png	9.5 KiB	8.6 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn2_.png	9.4 KiB	8.5 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn4_.png	9.3 KiB	8.5 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn1.png	9.3 KiB	8.5 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn8.png	9.3 KiB	8.4 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn3.png	9.2 KiB	8.4 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn5_.png	9.0 KiB	8.2 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn9_.png	8.9 KiB	8.0 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn10_.png	8.8 KiB	7.9 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn6_.png	8.8 KiB	7.9 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn8_.png	8.7 KiB	7.8 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn7_.png	7.6 KiB	6.8 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn9.png	7.2 KiB	6.3 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn5.png	6.6 KiB	5.7 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn6.png	6.4 KiB	5.5 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn7.png	6.3 KiB	5.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-2-DIV

nodeLabel: images/kharlogo.png

path: 1,HTML,1,BODY,1,DIV,0,DIV

selector: body > div > div

snippet: <div style="max-width: 800px; background-image: url("images/gosprbkg.jpg");">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
www.kharkov.ua/	http/1.1
www.kharkov.ua/date.js	http/1.1
www.kharkov.ua/images/kharlogo.png	http/1.1
www.kharkov.ua/img/lnk1.png	http/1.1
www.kharkov.ua/img/lnk2.png	http/1.1
www.kharkov.ua/img/lnk3.png	http/1.1
www.kharkov.ua/img/lnk4.png	http/1.1
www.kharkov.ua/img/lnk5.png	http/1.1
www.kharkov.ua/img/lnk6.png	http/1.1
www.kharkov.ua/img/lnk7.png	http/1.1
www.kharkov.ua/img/lnk8.png	http/1.1
www.kharkov.ua/img/lnk9.png	http/1.1
www.kharkov.ua/img/lnk10.png	http/1.1
www.kharkov.ua/img/lnk11.png	http/1.1
www.kharkov.ua/img/lnk12.png	http/1.1
www.kharkov.ua/img/kharkov_ua-qrcode.png	http/1.1
www.kharkov.ua/images/sq_small.png	http/1.1
www.kharkov.ua/images/ffar.png	http/1.1
www.kharkov.ua/images/lira1.png	http/1.1
www.kharkov.ua/images/bls.gif	http/1.1
www.kharkov.ua/cache/651.jpeg	http/1.1
www.kharkov.ua/cache/650.jpeg	http/1.1
www.kharkov.ua/cache/649.jpeg	http/1.1
www.kharkov.ua/css/imres.css	http/1.1
www.kharkov.ua/css/mstyle.css	http/1.1
www.kharkov.ua/images/gosprbkg.jpg	http/1.1
www.kharkov.ua/images/bg.jpg	http/1.1
www.kharkov.ua/images/btnbkg.jpg	http/1.1
www.kharkov.ua/img/btn1.png	http/1.1
www.kharkov.ua/img/btn1_.png	http/1.1
www.kharkov.ua/img/btn2.png	http/1.1
www.kharkov.ua/img/btn2_.png	http/1.1
www.kharkov.ua/img/btn3.png	http/1.1
www.kharkov.ua/img/btn3_.png	http/1.1
www.kharkov.ua/img/btn4.png	http/1.1
www.kharkov.ua/img/btn4_.png	http/1.1
www.kharkov.ua/img/btn5.png	http/1.1
www.kharkov.ua/img/btn5_.png	http/1.1
www.kharkov.ua/img/btn6.png	http/1.1
www.kharkov.ua/img/btn6_.png	http/1.1
www.kharkov.ua/img/btn7.png	http/1.1
www.kharkov.ua/img/btn7_.png	http/1.1
www.kharkov.ua/img/btn8.png	http/1.1
www.kharkov.ua/img/btn8_.png	http/1.1
www.kharkov.ua/img/btn9.png	http/1.1
www.kharkov.ua/img/btn9_.png	http/1.1
www.kharkov.ua/img/btn10.png	http/1.1
www.kharkov.ua/img/btn10_.png	http/1.1
www.kharkov.ua/favicon.ico	http/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.kharkov.ua/date.js	1.3 KiB	194 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
finance.ua/cgi-bin/fip.cgi?currency=eur/uah&source=nbu&lang=ru	0.0 ms	974 B
finance.ua/cgi-bin/fip.cgi?currency=pln/uah&source=nbu&lang=ru	0.0 ms	932 B
finance.ua/cgi-bin/fip.cgi?currency=usd/uah&source=nbu&lang=ru	0.0 ms	926 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
images/lira1.png `div.thumb_wrapper > div.thumbd3 > div > img`	www.kharkov.ua/images/lira1.png
images/kharlogo.png `div.logo > div > a.nob > img`	www.kharkov.ua/images/kharlogo.png
images/sq_small.png `div > noindex > a > img`	www.kharkov.ua/images/sq_small.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk1.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk2.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk3.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk4.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk5.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk6.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk7.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk8.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk9.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk10.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk11.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk12.png
images/bls.gif `div.thumb_wrapper > div.thumbd3 > div > img`	www.kharkov.ua/images/bls.gif

More information about the performance of your application. These numbers don't directly affect the Performance score.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
body `body`	0.892
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.062
Харьков +3° влажн.: 68% давл.: 743 мм 0 м/с `a > div#SinoptikInformer > div.siBody > div.siCity`	0.014
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.006
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.003
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.002
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.002
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.001
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.001
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +3° влажн.… `body > div`	0.000

●Time to Interactive 2.4 s

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 482 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.7 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 110 ms

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
49346018 `div.thumb_wrapper > div.thumbd3 > div > font`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016… `div > form > div.numpd > select.navform`
Январь Февраль Март Апрель Май Июнь Июль Август Сентябрь Октябрь Ноябрь Декабрь `div > form > div.numpd > select.navform`
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 3… `div > form > div.numpd > select.navform`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.thumb_wrapper > div.thumbd3 > div > a `div.thumb_wrapper > div.thumbd3 > div > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●`<input type="image">` elements have `[alt]` text

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●The page contains a heading, skip link, or landmark region

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○Form elements have associated labels

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
images/kharlogo.png `div.logo > div > a.nob > img`	www.kharkov.ua/images/kharlogo.png	320 x 41	342 x 44	480 x 62
images/sq_small.png `div > noindex > a > img`	www.kharkov.ua/images/sq_small.png	130 x 25	130 x 25	195 x 38
Курс EUR, НБУ `div > noindex > a > img`	finance.ua/cgi-bin/fip.cgi?currency=eur/uah&source=nbu&lang=ru	88 x 31	88 x 31	132 x 47
Курс PLN, НБУ `div > noindex > a > img`	finance.ua/cgi-bin/fip.cgi?currency=pln/uah&source=nbu&lang=ru	88 x 31	88 x 31	132 x 47
Курс USD, НБУ `div > noindex > a > img`	finance.ua/cgi-bin/fip.cgi?currency=usd/uah&source=nbu&lang=ru	88 x 31	88 x 31	132 x 47
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk1.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk10.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk11.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk12.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk2.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk3.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk4.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk5.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk6.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk7.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk8.png	133 x 16	133 x 16	200 x 24
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk9.png	133 x 16	133 x 16	200 x 24

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

411 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

793 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

1.073

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

613 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

793 ms

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

items: [map[node:map[type:text value:Total] score:1.072696] map[node:map[boundingRect:map[bottom:1692 height:1684 left:0 right:1350 top:8 width:1350] lhId:page-30-BODY nodeLabel:body path:1,HTML,1,BODY selector:body snippet:<body> type:node] score:0.991489 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:235 height:16 left:275 right:408 top:219 width:133] lhId:page-40-IMG nodeLabel:div.sixt > div > a.nob > img path:1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div.sixt > div > a.nob > img snippet:<img alt="" src="/img/lnk1.png" style="margin-top:1px; border: 0;"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1606 height:1347 left:275 right:1075 top:259 width:800] lhId:page-28-DIV nodeLabel:Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… path:1,HTML,1,BODY,3,DIV selector:body > div snippet:<div style="max-width: 798px; margin: 0px auto 10px; background: rgb(229, 228, 222); display: table;"> type:node] score:0.072516] map[node:map[boundingRect:map[bottom:652 height:118 left:282 right:418 top:534 width:136] lhId:page-35-DIV nodeLabel:Харьков +5° влажн.: 71% давл.: 742 мм 3 м/с, path:1,HTML,1,BODY,3,DIV,0,DIV,0,DIV,0,DIV,25,A,0,DIV,1,DIV,1,DIV selector:a > div#SinoptikInformer > div.siBody > div.siCity snippet:<div class="siCity"> type:node] score:0.002428] map[node:map[boundingRect:map[bottom:1606 height:1347 left:275 right:1075 top:259 width:800] lhId:page-28-DIV nodeLabel:Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… path:1,HTML,1,BODY,3,DIV selector:body > div snippet:<div style="max-width: 798px; margin: 0px auto 10px; background: rgb(229, 228, 222); display: table;"> type:node] score:0.002223 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:235 height:16 left:275 right:408 top:219 width:133] lhId:page-40-IMG nodeLabel:div.sixt > div > a.nob > img path:1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,A,0,IMG selector:div.sixt > div > a.nob > img snippet:<img alt="" src="/img/lnk1.png" style="margin-top:1px; border: 0;"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1606 height:1347 left:275 right:1075 top:259 width:800] lhId:page-28-DIV nodeLabel:Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… path:1,HTML,1,BODY,3,DIV selector:body > div snippet:<div style="max-width: 798px; margin: 0px auto 10px; background: rgb(229, 228, 222); display: table;"> type:node] score:0.001663 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:235 height:16 left:808 right:941 top:219 width:133] lhId:page-41-IMG nodeLabel:div.sixt > div > a.nob > img path:1,HTML,1,BODY,2,DIV,4,DIV,0,DIV,0,A,0,IMG selector:div.sixt > div > a.nob > img snippet:<img alt="" src="/img/lnk5.png" style="margin-top:1px; border: 0;"> type:node]]] type:subitems]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Велодень в Харькове. `li > noindex > a > img`	www.kharkov.ua/cache/649.jpeg	43.0 KiB	38.8 KiB
Новая полиция начала работу в Харькове `li > noindex > a > img`	www.kharkov.ua/cache/650.jpeg	29.7 KiB	25.6 KiB
images/kharlogo.png `body > div > div`	www.kharkov.ua/images/gosprbkg.jpg	51.7 KiB	25.0 KiB
Станция метро ?Победа? в Харькове официально открыта `li > noindex > a > img`	www.kharkov.ua/cache/651.jpeg	22.6 KiB	18.5 KiB
images/kharlogo.png `div.logo > div > a.nob > img`	www.kharkov.ua/images/kharlogo.png	15.8 KiB	13.6 KiB
div.siCity > div#siCont0 > div.siLeft > div#weatherIco0 `div.siCity > div#siCont0 > div.siLeft > div#weatherIco0`	sinoptik.ua/resources/legacy/informers/s-informers-t2.png	33.0 KiB	12.6 KiB
images/lira1.png `div.thumb_wrapper > div.thumbd3 > div > img`	www.kharkov.ua/images/lira1.png	11.2 KiB	10.2 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn10.png	9.7 KiB	8.8 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn3_.png	9.6 KiB	8.8 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn1_.png	9.6 KiB	8.7 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn4.png	9.5 KiB	8.6 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn2.png	9.5 KiB	8.6 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn2_.png	9.4 KiB	8.5 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn4_.png	9.3 KiB	8.5 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn1.png	9.3 KiB	8.5 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn8.png	9.3 KiB	8.4 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn3.png	9.2 KiB	8.4 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn5_.png	9.0 KiB	8.2 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn9_.png	8.9 KiB	8.0 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn10_.png	8.8 KiB	7.9 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn6_.png	8.8 KiB	7.9 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn8_.png	8.7 KiB	7.8 KiB
body > div.wrap > div.sixt > div `body > div.wrap > div.sixt > div`	www.kharkov.ua/img/btn7_.png	7.6 KiB	6.8 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn9.png	7.2 KiB	6.3 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn5.png	6.6 KiB	5.7 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn6.png	6.4 KiB	5.5 KiB
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	www.kharkov.ua/img/btn7.png	6.3 KiB	5.5 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-2-DIV

nodeLabel: images/kharlogo.png

path: 1,HTML,1,BODY,1,DIV,0,DIV

selector: body > div > div

snippet: <div style="max-width: 800px; background-image: url("images/gosprbkg.jpg");">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
www.kharkov.ua/	http/1.1
www.kharkov.ua/date.js	http/1.1
www.kharkov.ua/images/kharlogo.png	http/1.1
www.kharkov.ua/img/lnk1.png	http/1.1
www.kharkov.ua/img/lnk2.png	http/1.1
www.kharkov.ua/img/lnk3.png	http/1.1
www.kharkov.ua/img/lnk4.png	http/1.1
www.kharkov.ua/img/lnk5.png	http/1.1
www.kharkov.ua/img/lnk6.png	http/1.1
www.kharkov.ua/img/lnk7.png	http/1.1
www.kharkov.ua/img/lnk8.png	http/1.1
www.kharkov.ua/img/lnk9.png	http/1.1
www.kharkov.ua/img/lnk10.png	http/1.1
www.kharkov.ua/img/lnk11.png	http/1.1
www.kharkov.ua/img/lnk12.png	http/1.1
www.kharkov.ua/img/kharkov_ua-qrcode.png	http/1.1
www.kharkov.ua/images/sq_small.png	http/1.1
www.kharkov.ua/images/ffar.png	http/1.1
www.kharkov.ua/images/lira1.png	http/1.1
www.kharkov.ua/images/bls.gif	http/1.1
www.kharkov.ua/cache/651.jpeg	http/1.1
www.kharkov.ua/cache/650.jpeg	http/1.1
www.kharkov.ua/cache/649.jpeg	http/1.1
www.kharkov.ua/css/imres.css	http/1.1
www.kharkov.ua/css/mstyle.css	http/1.1
www.kharkov.ua/images/gosprbkg.jpg	http/1.1
www.kharkov.ua/images/bg.jpg	http/1.1
www.kharkov.ua/images/btnbkg.jpg	http/1.1
www.kharkov.ua/img/btn1.png	http/1.1
www.kharkov.ua/img/btn1_.png	http/1.1
www.kharkov.ua/img/btn2.png	http/1.1
www.kharkov.ua/img/btn2_.png	http/1.1
www.kharkov.ua/img/btn3.png	http/1.1
www.kharkov.ua/img/btn3_.png	http/1.1
www.kharkov.ua/img/btn4.png	http/1.1
www.kharkov.ua/img/btn4_.png	http/1.1
www.kharkov.ua/img/btn5.png	http/1.1
www.kharkov.ua/img/btn5_.png	http/1.1
www.kharkov.ua/img/btn6.png	http/1.1
www.kharkov.ua/img/btn6_.png	http/1.1
www.kharkov.ua/img/btn7.png	http/1.1
www.kharkov.ua/img/btn7_.png	http/1.1
www.kharkov.ua/img/btn8.png	http/1.1
www.kharkov.ua/img/btn8_.png	http/1.1
www.kharkov.ua/img/btn9.png	http/1.1
www.kharkov.ua/img/btn9_.png	http/1.1
www.kharkov.ua/img/btn10.png	http/1.1
www.kharkov.ua/img/btn10_.png	http/1.1
www.kharkov.ua/favicon.ico	http/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.kharkov.ua/date.js	1.3 KiB	82 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
finance.ua/cgi-bin/fip.cgi?currency=eur/uah&source=nbu&lang=ru	0.0 ms	976 B
finance.ua/cgi-bin/fip.cgi?currency=pln/uah&source=nbu&lang=ru	0.0 ms	927 B
finance.ua/cgi-bin/fip.cgi?currency=usd/uah&source=nbu&lang=ru	0.0 ms	924 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
images/lira1.png `div.thumb_wrapper > div.thumbd3 > div > img`	www.kharkov.ua/images/lira1.png
images/kharlogo.png `div.logo > div > a.nob > img`	www.kharkov.ua/images/kharlogo.png
images/sq_small.png `div > noindex > a > img`	www.kharkov.ua/images/sq_small.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk1.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk2.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk3.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk4.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk5.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk6.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk7.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk8.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk9.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk10.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk11.png
div.sixt > div > a.nob > img `div.sixt > div > a.nob > img`	www.kharkov.ua/img/lnk12.png
images/bls.gif `div.thumb_wrapper > div.thumbd3 > div > img`	www.kharkov.ua/images/bls.gif

More information about the performance of your application. These numbers don't directly affect the Performance score.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
body `body`	0.991
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… `body > div`	0.073
Харьков +5° влажн.: 71% давл.: 742 мм 3 м/с, `a > div#SinoptikInformer > div.siBody > div.siCity`	0.002
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… `body > div`	0.002
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… `body > div`	0.002
body > div.wrap > div.sixt `body > div.wrap > div.sixt`	0.001
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… `body > div`	0.001
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… `body > div`	0.000
Наш QR-Код Медиа партнер Погода Четверг 23.04.26, ночь Харьков +5° влажн.… `body > div`	0.000

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Optimize viewport for mobile

●Time to Interactive 0.8 s

●Max Potential First Input Delay 20 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 482 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 0.2 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 40 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 90 ms

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
49346019 `div.thumb_wrapper > div.thumbd3 > div > font`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016… `div > form > div.numpd > select.navform`
Январь Февраль Март Апрель Май Июнь Июль Август Сентябрь Октябрь Ноябрь Декабрь `div > form > div.numpd > select.navform`
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 3… `div > form > div.numpd > select.navform`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.wrap > div.sixt > div > a.nob `div.wrap > div.sixt > div > a.nob`
div.thumb_wrapper > div.thumbd3 > div > a `div.thumb_wrapper > div.thumbd3 > div > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●`<input type="image">` elements have `[alt]` text

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●The page contains a heading, skip link, or landmark region

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○Form elements have associated labels

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`

Results for https://kharkov.ua

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Trust (1)

Usability (2)

Content (2)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best practices

Best Practices

User Experience

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best practices

Best Practices

SEO

Keyboard Shortcuts