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.

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
termly_solutions_showcase_with_badges `div.flex > div.lg:w-6/12 > div.hidden > img.w-full`	termly.io/wp-content/uploads/termly_solutions_showcase_with_badges.webp	171.5 KiB	127.2 KiB
Termly-IAB-TCF-v2-2 `div.grid > div.flex > div.w-full > img.h-14`	termly.io/wp-content/uploads/Termly-IAB-TCF-v2-2.png.webp	28.4 KiB	25.7 KiB

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

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

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
/resource-blocker/9598d17a-6c78-437c-83a3-52d50ae899fd?au...	14400.0 s	143.5 KiB
app.termly.io/resource-blocker/support/894-6156b36a131577c56e7e.min.js	14400.0 s	8.4 KiB
/dcdn/settings.js?a=1133967&settings_type=4&ts=1776790939...	1800.0 s	5.3 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
termly.io/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js	2871.0 s	4.0 KiB
app.termly.io/resource-blocker/support/808-26e9c6c7a3bd048ed656.min.js	14400.0 s	3.2 KiB
app.termly.io/resource-blocker/support/524-7d36cb122791702e3df2.min.js	14400.0 s	2.7 KiB
app.termly.io/resource-blocker/support/377-e518d8a5c599aa1c5977.min.js	14400.0 s	873 B
/eu01/v.gif?cd=0&a=1133967&d=termly.io&u=DE3164F1A45C1429...	43200.0 s	147 B

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

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 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: 0.0 ms 255.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-TPD6VMTVN7&cx=c&gtm=4e64h1	172.5 KiB	68.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-KJBTQ26D	169.9 KiB	67.3 KiB
www.googletagmanager.com/gtag/js?id=AW-848173323&cx=c&gtm=4e64h1	146.6 KiB	64.7 KiB
/resource-blocker/9598d17a-6c78-437c-83a3-52d50ae899fd?au...	143.3 KiB	54.1 KiB

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,311 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 4 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 60 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 40 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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.

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
Compliance Solutions You Can Trust `body.home > section.py-10 > div.container > h4.text-center`
Policies Created per Day `div.container > div.flex > div.px-2 > h5.opacity-70`
Businesses `div.container > div.flex > div.px-2 > h5.opacity-70`
Countries served `div.container > div.flex > div.px-2 > h5.opacity-70`
Banner Views per Month `div.container > div.flex > div.px-2 > h5.opacity-70`
EU Coverage `div.grid > div.flex > div.w-full > h4.mb-4`
Patrick – France View review `div.lg:px-4 > div.card > div.flex > h6.text-small`
Multiple Business Platforms `div.lg:w-6/12 > div.mb-8 > div.flex > h4`
Consent Management Platform `div.bg-white > div.flex-grow > a.hover:text-deepblue > h5.my-3`
div.container > div.xl:col-span-6 > div.xl:col-span-3 > h6.text-deepblue `div.container > div.xl:col-span-6 > div.xl:col-span-3 > h6.text-deepblue`

These are opportunities to improve keyboard navigation in your application.

Best practices

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-*]` 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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

●Links have a discernible name

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

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

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

●Touch targets have sufficient size and spacing.

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

●`[lang]` attributes have a valid value

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

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

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

○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 display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
termly_solutions_showcase_with_badges `div.flex > div.lg:w-6/12 > div.hidden > img.w-full`	termly.io/wp-content/uploads/termly_solutions_showcase_with_badges.webp	640 x 500 (1.28)	1057 x 820 (1.29)
world-map-background `div.flex > div.lg:w-6/12 > div.block > img.w-full`	termly.io/wp-content/uploads/world-map-background.webp	640 x 500 (1.28)	750 x 500 (1.50)
patrick de grijs `div.card > div.flex > picture.shrink-0 > img.shadow-lg`	termly.io/wp-content/uploads/patrick-de-grijs.png.webp	48 x 48 (1.00)	154 x 164 (0.94)
Elisabeth-C `div.card > div.flex > picture.shrink-0 > img.shadow-lg`	termly.io/wp-content/uploads/Elisabeth-C.png.webp	48 x 48 (1.00)	154 x 164 (0.94)
Joerg Ohle `div.card > div.flex > picture.shrink-0 > img.shadow-lg`	termly.io/wp-content/uploads/Joerg-Ohle.png.webp	48 x 48 (1.00)	154 x 164 (0.94)
Lavana Dawn `div.card > div.flex > picture.shrink-0 > img.shadow-lg`	termly.io/wp-content/uploads/Lavana-Dawn.png.webp	48 x 48 (1.00)	154 x 164 (0.94)
Josh Brust `div.card > div.flex > picture.shrink-0 > img.shadow-lg`	termly.io/wp-content/uploads/Josh-Brust.png.webp	48 x 48 (1.00)	154 x 164 (0.94)
Morgan `div.card > div.flex > picture.shrink-0 > img.shadow-lg`	termly.io/wp-content/uploads/Morgan.png.webp	48 x 48 (1.00)	154 x 164 (0.94)

●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

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
termly.io/products/	Learn More
termly.io/products/	Learn More
termly.io/products/	Learn More

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

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`