Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

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.

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
fortza.net/wp-content/plugins/revslider/sr6/assets/js/rs6.min.js?ver=6.7.40	0.0 ms	102.2 KiB
/maps/api/js?key=AIzaSyDFm0Ch2iXc78Gx5svtdICn-zF-qX17Pd0&...	1800.0 s	102.5 KiB
/wp-content/themes/jupiter/assets/js/min/full-scripts.6.1...	0.0 ms	73.0 KiB
/wp-content/plugins/LayerSlider/assets/static/layerslider...	0.0 ms	64.8 KiB
fortza.net/wp-content/plugins/revslider/sr6/assets/js/rbtools.min.js?ver=6.7.40	0.0 ms	58.6 KiB
/wp-content/plugins/LayerSlider/assets/static/layerslider...	0.0 ms	39.6 KiB
fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	0.0 ms	29.1 KiB
fortza.net/wp-content/uploads/2015/11/home-header.jpg	604800.0 s	181.3 KiB
/wp-content/litespeed/css/0abac1b93e910ce3ae7b1bddd8513ab...	604800.0 s	167.9 KiB
/wp-content/plugins/jupiter-donut/assets/js/shortcodes-sc...	0.0 ms	16.6 KiB
/wp-content/uploads/2015/11/simple_blue_background-wallpa...	604800.0 s	164.5 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
www.fortza.net/wp-content/uploads/2015/11/home-worker.jpg	604800.0 s	110.5 KiB
/wp-content/plugins/cookie-law-info/legacy/public/js/cook...	0.0 ms	7.1 KiB
fortza.net/wp-content/uploads/2015/11/home-head-img-01.jpg	604800.0 s	69.1 KiB
fortza.net/wp-content/uploads/2015/11/home-head-img-4.jpg	604800.0 s	56.2 KiB
/wp-content/plugins/js_composer_theme/assets/js/dist/js_c...	0.0 ms	4.8 KiB
/wp-content/themes/jupiter/assets/js/plugins/wp-enqueue/m...	0.0 ms	4.7 KiB
fortza.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	0.0 ms	4.6 KiB
/maps/api/js/StaticMapService.GetMapImage?1m2&1i2380445&2...	86400.0 s	11.5 KiB
/wp-content/plugins/LayerSlider/assets/static/layerslider...	0.0 ms	4.4 KiB
fortza.net/wp-content/plugins/contact-form-7/includes/js/index.js?ver=6.1.5	0.0 ms	3.9 KiB
fortza.net/wp-content/uploads/2015/11/home-head-img-03.jpg	604800.0 s	34.4 KiB
fortza.net/wp-content/plugins/contact-form-7/includes/swv/js/index.js?ver=6.1.5	0.0 ms	3.3 KiB
/wp-content/themes/jupiter/assets/js/plugins/wp-enqueue/m...	0.0 ms	2.7 KiB
fortza.net/wp-includes/js/dist/i18n.min.js?ver=c26c3dc7bed366793375	0.0 ms	2.1 KiB
fortza.net/wp-includes/js/dist/hooks.min.js?ver=dd5603f07f9220ed27f1	0.0 ms	1.9 KiB
/wp-content/themes/jupiter/header-builder/includes/assets...	0.0 ms	1.7 KiB
/wp-content/plugins/wpcf7-redirect/build/assets/frontend-...	0.0 ms	1.2 KiB
fortza.net/wp-content/uploads/2024/01/logo-fortza1x5.png	604800.0 s	11.3 KiB
/wp-content/themes/jupiter/header-builder/includes/assets...	0.0 ms	1001 B
fortza.net/wp-content/uploads/2024/01/logo-fortza1x5w.png	604800.0 s	7.6 KiB
/wp-content/uploads/bfi_thumb/dummy-transparent-3idrdbhzu...	604800.0 s	730 B

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.16599444493695822] map[node:map[boundingRect:map[bottom:849 height:713 left:0 right:1350 top:136 width:1350] lhId:page-5-DIV nodeLabel:div#page-section-2 > div.mk-page-section-inner > div.background-layer-holder > div#background-layer--2 path:1,HTML,1,BODY,2,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV selector:div#page-section-2 > div.mk-page-section-inner > div.background-layer-holder > div#background-layer--2 snippet:<div id="background-layer--2" data-mk-lazyload="false" class="background-layer mk-background-stretch none-blend-effect js-el" data-mk-img-set="{"landscape":{"desktop":"https://fortza.net/wp-content/uploads/2015/11/hom…" mk-img-loaded="" style="background-image: url("https://fortza.net/wp-content/uploads/2015/11/home-…");"> type:node] score:0.1427016843971631 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2593 height:796 left:690 right:1320 top:1797 width:630] lhId:page-2-IMG nodeLabel:home-worker path:1,HTML,1,BODY,2,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,6,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG selector:div.mk-image-container > div.mk-image-holder > div.mk-image-inner > img.lightbox-false snippet:<img loading="lazy" decoding="async" class="lightbox-false" alt="home-worker" width="630" height="796" src="https://www.fortza.net/wp-content/uploads/2015/11/home-worker.jpg"> type:node]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/ubuntu/v21/4iCs6KVjbNBYlgoKcQ72nU6AF7xm.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:135 height:100 left:669 right:1350 top:35 width:681] lhId:page-7-DIV nodeLabel:ACASĂ DESPRE NOI SERVICII MAGAZIN CARIERE BLOG CONTACT path:1,HTML,1,BODY,2,DIV,0,DIV,0,HEADER,0,DIV,1,DIV,2,DIV,0,DIV selector:div.mk-header-holder > div.mk-header-inner > div.mk-grid > div.mk-header-nav-container snippet:<div class="mk-header-nav-container one-row-style menu-hover-style-4" role="navigation" itemscope="itemscope" itemtype="https://schema.org/SiteNavigationElement"> type:node] score:0.02329276053979511 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:2593 height:796 left:690 right:1320 top:1797 width:630] lhId:page-2-IMG nodeLabel:home-worker path:1,HTML,1,BODY,2,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,6,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG selector:div.mk-image-container > div.mk-image-holder > div.mk-image-inner > img.lightbox-false snippet:<img loading="lazy" decoding="async" class="lightbox-false" alt="home-worker" width="630" height="796" src="https://www.fortza.net/wp-content/uploads/2015/11/home-worker.jpg"> type:node]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu0SC55I.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSGmu0SC55K5gw.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/opensans/v44/memtYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWqWuU6FxZCJgg.woff2]]] type:subitems]]]

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/s/opensans/v44/memtYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWqWu...	145 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	140 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSGmu...	135 ms
fonts.gstatic.com/s/ubuntu/v21/4iCs6KVjbNBYlgoKfw72nU6AFw.woff2	120 ms
fonts.gstatic.com/s/ubuntu/v21/4iCv6KVjbNBYlgoCxCvjvmyNPYZvg7UI.woff2	115 ms
fonts.gstatic.com/s/ubuntu/v21/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2	115 ms
fonts.gstatic.com/s/ubuntu/v21/4iCs6KVjbNBYlgoKcQ72nU6AF7xm.woff2	90 ms
/s/opensans/v44/memtYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWqWt...	55 ms

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:33.687 source:map[type:text value:[unattributed]]] map[reflowTime:4.117 source:map[column:9998 line:2 type:source-location url:https://fortza.net/wp-content/themes/jupiter/assets/js/min/full-scripts.6.12.3.js?ver=1769716017 urlProvider:network]] map[reflowTime:0.402 source:map[column:50335 line:1 type:source-location url:https://fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.245 source:map[column:50393 line:1 type:source-location url:https://fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.202 source:map[column:50457 line:1 type:source-location url:https://fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:6.975 source:map[column:49637 line:1 type:source-location url:https://fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.174 source:map[column:49615 line:1 type:source-location url:https://fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.346 source:map[column:51395 line:1 type:source-location url:https://fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:1.375 source:map[column:21339 line:5 type:source-location url:https://fortza.net/wp-content/themes/jupiter/assets/js/min/full-scripts.6.12.3.js?ver=1769716017 urlProvider:network]] map[reflowTime:4.119 source:map[column:30706 line:1 type:source-location url:https://fortza.net/wp-content/themes/jupiter/assets/js/min/full-scripts.6.12.3.js?ver=1769716017 urlProvider:network]] map[reflowTime:1.44 source:map[column:27873 line:1 type:source-location url:https://fortza.net/wp-content/themes/jupiter/assets/js/min/full-scripts.6.12.3.js?ver=1769716017 urlProvider:network]] map[reflowTime:0.191 source:map[column:28008 line:1 type:source-location url:https://fortza.net/wp-content/themes/jupiter/assets/js/min/full-scripts.6.12.3.js?ver=1769716017 urlProvider:network]] map[reflowTime:0.17 source:map[column:28053 line:1 type:source-location url:https://fortza.net/wp-content/themes/jupiter/assets/js/min/full-scripts.6.12.3.js?ver=1769716017 urlProvider:network]] map[reflowTime:3.095 source:map[column:83946 line:1 type:source-location url:https://fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]]]

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
home-head-img-01 `div.mk-image-container > div.mk-image-holder > div.mk-image-inner > img.lightbox-false`	fortza.net/wp-content/uploads/2015/11/home-head-img-01.jpg	69.0 KiB	54.1 KiB
home-head-img-4 `div.mk-image-container > div.mk-image-holder > div.mk-image-inner > img.lightbox-false`	fortza.net/wp-content/uploads/2015/11/home-head-img-4.jpg	56.2 KiB	41.2 KiB
home-worker `div.mk-image-container > div.mk-image-holder > div.mk-image-inner > img.lightbox-false`	www.fortza.net/wp-content/uploads/2015/11/home-worker.jpg	110.4 KiB	28.8 KiB
home-head-img-03 `div.mk-image-container > div.mk-image-holder > div.mk-image-inner > img.lightbox-false`	fortza.net/wp-content/uploads/2015/11/home-head-img-03.jpg	34.3 KiB	19.4 KiB
Macarale – Schele – Cofraje – Utilaje `div.mk-grid > div.header-logo > a > img.mk-sticky-logo`	fortza.net/wp-content/uploads/2024/01/logo-fortza1x5w.png	7.6 KiB	4.9 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-5-DIV

nodeLabel: div#page-section-2 > div.mk-page-section-inner > div.background-layer-holder > div#background-layer--2

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

selector: div#page-section-2 > div.mk-page-section-inner > div.background-layer-holder > div#background-layer--2

snippet: <div id="background-layer--2" data-mk-lazyload="false" class="background-layer mk-background-stretch none-blend-effect js-el" data-mk-img-set="{"landscape":{"desktop":"https://fortza.net/wp-content/uploads/2015/11/hom…" mk-img-loaded="" style="background-image: url("https://fortza.net/wp-content/uploads/2015/11/home-…");">

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

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
/wp-content/plugins/LayerSlider/assets/static/layerslider...	64.8 KiB
/wp-content/plugins/cookie-law-info/legacy/public/js/cook...	7.1 KiB
/wp-content/litespeed/css/0abac1b93e910ce3ae7b1bddd8513ab...	167.9 KiB	277 ms
/wp-content/plugins/LayerSlider/assets/static/layerslider...	4.4 KiB
/wp-content/plugins/LayerSlider/assets/static/layerslider...	39.6 KiB	92 ms
fortza.net/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	29.1 KiB	92 ms
fortza.net/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	4.6 KiB
/wp-content/themes/jupiter/assets/js/plugins/wp-enqueue/m...	4.7 KiB
/css?family=Ubuntu%3A100italic%2C200italic%2C300italic%2C...	1.4 KiB	322 ms

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

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
div#page-section-2 > div.mk-page-section-inner > div.background-layer-holder > div#background-layer--2 `div#page-section-2 > div.mk-page-section-inner > div.background-layer-holder > div#background-layer--2`	0.143
ACASĂ DESPRE NOI SERVICII MAGAZIN CARIERE BLOG CONTACT `div.mk-header-holder > div.mk-header-inner > div.mk-grid > div.mk-header-nav-container`	0.023

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 180 ms 161.8 KiB

URL	Transfer Size	Est Savings
/wp-content/litespeed/css/0abac1b93e910ce3ae7b1bddd8513ab...	167.8 KiB	161.8 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 180 ms 558.0 KiB

URL	Transfer Size	Est Savings
fortza.net/wp-content/plugins/revslider/sr6/assets/js/rs6.min.js?ver=6.7.40	102.1 KiB	99.5 KiB
www.googletagmanager.com/gtag/js?id=G-1Q94ZKRVGW	184.8 KiB	73.7 KiB
www.googletagmanager.com/gtag/js?id=UA-98752256-8&cx=c&gtm=4e6al1	120.4 KiB	70.5 KiB
/wp-content/plugins/LayerSlider/assets/static/layerslider...	64.7 KiB	61.2 KiB
/maps/api/js?key=AIzaSyDFm0Ch2iXc78Gx5svtdICn-zF-qX17Pd0&...	102.2 KiB	53.0 KiB
/wp-content/themes/jupiter/assets/js/min/full-scripts.6.1...	72.9 KiB	50.9 KiB
fortza.net/wp-content/plugins/revslider/sr6/assets/js/rbtools.min.js?ver=6.7.40	58.6 KiB	40.9 KiB
/wp-content/plugins/LayerSlider/assets/static/layerslider...	39.5 KiB	30.4 KiB
maps.googleapis.com/maps-api-v3/api/js/66/11a/common.js	37.7 KiB	28.1 KiB
maps.googleapis.com/maps-api-v3/api/js/66/11a/util.js	70.7 KiB	26.9 KiB
maps.googleapis.com/maps-api-v3/api/js/66/11a/map.js	25.2 KiB	22.8 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.7 KiB

URL	Transfer Size	Est Savings
/wp-content/plugins/jupiter-donut/assets/js/shortcodes-sc...	16.5 KiB	6.7 KiB

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
Fortza `div.mk-grid > div.mk-footer-logo > a > img`	fortza.net/wp-content/uploads/2024/01/logo-fortza1x5w.png

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

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Avoids enormous network payloads Total size was 2,092 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 80 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 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
ACASĂ `nav.mk-main-navigation > ul#menu-main-menu > li#menu-item-545 > a.menu-item-link`
NOUTĂȚI `div.vc_col-sm-12 > h2#fancy-title-50 > span > p`
24/07/2025 `div.mk-blog-meta > div.mk-blog-meta-wrapper > time > a`
24/10/2023 `div.mk-blog-meta > div.mk-blog-meta-wrapper > time > a`
18/08/2023 `div.mk-blog-meta > div.mk-blog-meta-wrapper > time > a`
FACEM PERFORMANȚĂ ÎN URMĂTOARELE `div.vc_col-sm-12 > h2#fancy-title-63 > span > p`
Vânzare și închiriere de macarale. Service, mentenanță, transport, piese de sch… `div.mk-flipbox-holder > div.mk-flipbox-front > div.mk-flipbox-content > div.front-desc`
Secții dotare modern pentru confecții metalice de orice fel. O echipă de profes… `div.mk-flipbox-holder > div.mk-flipbox-front > div.mk-flipbox-content > div.front-desc`
Schele metalice, podine, diagonale, popi metalici și tot ce ține de lucrul pe ș… `div.mk-flipbox-holder > div.mk-flipbox-front > div.mk-flipbox-content > div.front-desc`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Experiența `div.vc_column-inner > div.wpb_wrapper > div#box-icon-35 > h4.icon-box-title`
Macarale de închiriat sau vânzare `div#list-44 > ul > li > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.mk-header-social > ul > li > a.twitter-hover `div.mk-header-social > ul > li > a.twitter-hover`
div.mk-header-social > ul > li > a.facebook-hover `div.mk-header-social > ul > li > a.facebook-hover`
div.mk-header-social > ul > li > a.googleplus-hover `div.mk-header-social > ul > li > a.googleplus-hover`
div.mk-header-social > ul > li > a.linkedin-hover `div.mk-header-social > ul > li > a.linkedin-hover`
div.wpb_row > div.vc_col-sm-12 > div.mk-pagination > a.mk-pagination-next `div.wpb_row > div.vc_col-sm-12 > div.mk-pagination > a.mk-pagination-next`
div#testimonial_60 > ul.flex-direction-nav > li > a.flex-prev `div#testimonial_60 > ul.flex-direction-nav > li > a.flex-prev`
div#testimonial_60 > ul.flex-direction-nav > li > a.flex-next `div#testimonial_60 > ul.flex-direction-nav > li > a.flex-next`
body.home > div.bottom-corner-btns > a.mk-go-top `body.home > div.bottom-corner-btns > a.mk-go-top`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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-*]` attributes match their roles

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

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

●`[role]` values are valid

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

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

●Image elements have `[alt]` attributes

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

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

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

●Elements use only permitted ARIA attributes

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○Buttons have an accessible name

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

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

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