Skip to content
https://kharkov.ua

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

75

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

Performance issues directly impact user engagement and conversion rates.

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

URLResource SizeEst Savings
Велодень в Харькове. li > noindex > a > img
www.kharkov.ua/cache/649.jpeg43.0 KiB38.8 KiB
Новая полиция начала работу в Харькове li > noindex > a > img
www.kharkov.ua/cache/650.jpeg29.7 KiB25.6 KiB
images/kharlogo.png body > div > div
www.kharkov.ua/images/gosprbkg.jpg51.7 KiB25.0 KiB
Станция метро ?Победа? в Харькове официально открыта li > noindex > a > img
www.kharkov.ua/cache/651.jpeg22.6 KiB18.5 KiB
images/kharlogo.png div.logo > div > a.nob > img
www.kharkov.ua/images/kharlogo.png15.8 KiB13.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.png33.0 KiB12.6 KiB
images/lira1.png div.thumb_wrapper > div.thumbd3 > div > img
www.kharkov.ua/images/lira1.png11.2 KiB10.2 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn10.png9.7 KiB8.8 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn3_.png9.6 KiB8.8 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn1_.png9.6 KiB8.7 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn4.png9.5 KiB8.6 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn2.png9.5 KiB8.6 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn2_.png9.4 KiB8.5 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn4_.png9.3 KiB8.5 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn1.png9.3 KiB8.5 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn8.png9.3 KiB8.4 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn3.png9.2 KiB8.4 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn5_.png9.0 KiB8.2 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn9_.png8.9 KiB8.0 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn10_.png8.8 KiB7.9 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn6_.png8.8 KiB7.9 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn8_.png8.7 KiB7.8 KiB
body > div.wrap > div.sixt > div body > div.wrap > div.sixt > div
www.kharkov.ua/img/btn7_.png7.6 KiB6.8 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn9.png7.2 KiB6.3 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn5.png6.6 KiB5.7 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn6.png6.4 KiB5.5 KiB
body > div.wrap > div.sixt body > div.wrap > div.sixt
www.kharkov.ua/img/btn7.png6.3 KiB5.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(&quot;images/gosprbkg.jpg&quot;);">

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.

URLProtocol
www.kharkov.ua/http/1.1
www.kharkov.ua/date.jshttp/1.1
www.kharkov.ua/images/kharlogo.pnghttp/1.1
www.kharkov.ua/img/lnk1.pnghttp/1.1
www.kharkov.ua/img/lnk2.pnghttp/1.1
www.kharkov.ua/img/lnk3.pnghttp/1.1
www.kharkov.ua/img/lnk4.pnghttp/1.1
www.kharkov.ua/img/lnk5.pnghttp/1.1
www.kharkov.ua/img/lnk6.pnghttp/1.1
www.kharkov.ua/img/lnk7.pnghttp/1.1
www.kharkov.ua/img/lnk8.pnghttp/1.1
www.kharkov.ua/img/lnk9.pnghttp/1.1
www.kharkov.ua/img/lnk10.pnghttp/1.1
www.kharkov.ua/img/lnk11.pnghttp/1.1
www.kharkov.ua/img/lnk12.pnghttp/1.1
www.kharkov.ua/img/kharkov_ua-qrcode.pnghttp/1.1
www.kharkov.ua/images/sq_small.pnghttp/1.1
www.kharkov.ua/images/ffar.pnghttp/1.1
www.kharkov.ua/images/lira1.pnghttp/1.1
www.kharkov.ua/images/bls.gifhttp/1.1
www.kharkov.ua/cache/651.jpeghttp/1.1
www.kharkov.ua/cache/650.jpeghttp/1.1
www.kharkov.ua/cache/649.jpeghttp/1.1
www.kharkov.ua/css/imres.csshttp/1.1
www.kharkov.ua/css/mstyle.csshttp/1.1
www.kharkov.ua/images/gosprbkg.jpghttp/1.1
www.kharkov.ua/images/bg.jpghttp/1.1
www.kharkov.ua/images/btnbkg.jpghttp/1.1
www.kharkov.ua/img/btn1.pnghttp/1.1
www.kharkov.ua/img/btn1_.pnghttp/1.1
www.kharkov.ua/img/btn2.pnghttp/1.1
www.kharkov.ua/img/btn2_.pnghttp/1.1
www.kharkov.ua/img/btn3.pnghttp/1.1
www.kharkov.ua/img/btn3_.pnghttp/1.1
www.kharkov.ua/img/btn4.pnghttp/1.1
www.kharkov.ua/img/btn4_.pnghttp/1.1
www.kharkov.ua/img/btn5.pnghttp/1.1
www.kharkov.ua/img/btn5_.pnghttp/1.1
www.kharkov.ua/img/btn6.pnghttp/1.1
www.kharkov.ua/img/btn6_.pnghttp/1.1
www.kharkov.ua/img/btn7.pnghttp/1.1
www.kharkov.ua/img/btn7_.pnghttp/1.1
www.kharkov.ua/img/btn8.pnghttp/1.1
www.kharkov.ua/img/btn8_.pnghttp/1.1
www.kharkov.ua/img/btn9.pnghttp/1.1
www.kharkov.ua/img/btn9_.pnghttp/1.1
www.kharkov.ua/img/btn10.pnghttp/1.1
www.kharkov.ua/img/btn10_.pnghttp/1.1
www.kharkov.ua/favicon.icohttp/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.

URLTransfer SizeDuration
www.kharkov.ua/date.js1.3 KiB82 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.

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.

ElementLayout 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
71

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

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

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

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

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`

Send Feedback