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 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:43.868 source:map[type:text value:[unattributed]]]]

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
js.qualified.com/qualified.js?token=nCX52tz3bqE643Qo	60.0 s	370.4 KiB
assets.qualified.com/packs/media/Inter-SemiBold.fcb100c7.woff2	0.0 ms	103.9 KiB
assets.qualified.com/packs/media/Inter-Regular.f1f0c35b.woff2	0.0 ms	96.9 KiB
js.storylane.io/js/v2/storylane.js	0.0 ms	5.6 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
/attribution_tracking/conversions/5277.js?p=https%3A%2F%2...	0.0 ms	2.2 KiB
/d/track/event?upid=110873&url=https%3A%2F%2Fwww.contentf...	0.0 ms	327 B

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
www.contentful.com/_next/static/css/df7557465dfb48e5.css	2.3 KiB
www.contentful.com/_next/static/css/ad6b6489dddc76eb.css	6.2 KiB
www.contentful.com/_next/static/css/b6f0caca70a7fd5b.css	968 B
www.contentful.com/_next/static/css/baa087f66929edb8.css	1.5 KiB
www.contentful.com/_next/static/css/f232577bc990b90f.css	838 B
www.contentful.com/_next/static/css/d96c085fb077f2be.css	1.1 KiB
www.contentful.com/_next/static/css/2e1c3f99b96dfeac.css	3.1 KiB
www.contentful.com/_next/static/css/e2de6c620a60607b.css	860 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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.contentful.com/_next/static/chunks/3196-4440c14d92fe2cb9.js	1.2 s	772 ms	7.1 ms
www.googletagmanager.com/gtm.js?id=GTM-W94TVR6G	616 ms	550 ms	22 ms
www.contentful.com/	417 ms	8.5 ms	101 ms
Unattributable	298 ms	20 ms	0.0 ms
www.contentful.com/_next/static/chunks/1397-949ba7995b8c03e2.js	147 ms	128 ms	6.5 ms
/16BcqiRsJId123ATa/39239078-882d-46c6-9235-dcd4318a5c73/o...	138 ms	125 ms	6.5 ms
www.contentful.com/_next/static/chunks/26164011-df8e1479e3c9182b.js	134 ms	120 ms	2.0 ms
www.googletagmanager.com/gtag/js?id=G-REC62920H6&cx=c&gtm=4e6460h1	86 ms	75 ms	10 ms
js.qualified.com/qualified.js?token=nCX52tz3bqE643Qo	85 ms	55 ms	29 ms
www.googletagmanager.com/gtag/js?id=G-SCQH3CZTQ5&cx=c&gtm=4e6460h1	60 ms	44 ms	15 ms
www.googletagmanager.com/gtag/js?id=G-RWVEEBSKZ3&cx=c&gtm=4e6460h1	54 ms	45 ms	8.8 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.1 s
Other	639 ms
Script Parsing & Compilation	272 ms
Rendering	229 ms
Style & Layout	197 ms
Parse HTML & CSS	73 ms
Garbage Collection	63 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable
Back/forward cache is disabled because WebSocket has been used.	Not actionable

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

URL	Transfer Size	Est Savings
js.qualified.com/qualified.js?token=nCX52tz3bqE643Qo	366.5 KiB	307.3 KiB
www.contentful.com/_next/static/chunks/1397-949ba7995b8c03e2.js	102.7 KiB	75.5 KiB
www.googletagmanager.com/gtag/destination?id=AW-788978041&cx=c&gtm=4e6460h1	145.5 KiB	69.9 KiB
www.googletagmanager.com/gtag/js?id=G-REC62920H6&cx=c&gtm=4e6460h1	179.0 KiB	66.7 KiB
www.googletagmanager.com/gtag/js?id=G-SCQH3CZTQ5&cx=c&gtm=4e6460h1	156.4 KiB	66.3 KiB
www.googletagmanager.com/gtag/js?id=G-RWVEEBSKZ3&cx=c&gtm=4e6460h1	154.8 KiB	65.4 KiB
www.googletagmanager.com/gtag/destination?id=DC-14131340&cx=c&gtm=4e6460h1	128.7 KiB	64.2 KiB
www.contentful.com/_next/static/chunks/3196-4440c14d92fe2cb9.js	120.1 KiB	56.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-W94TVR6G	192.3 KiB	53.2 KiB
www.contentful.com/_next/static/chunks/9571-b24846206502ac56.js	90.4 KiB	49.4 KiB
www.contentful.com/_next/static/chunks/00719cef-959202ea7838ffab.js	56.1 KiB	48.5 KiB
www.contentful.com/_next/static/chunks/2d1400c4.90c8c179baa192c7.js	78.2 KiB	47.2 KiB
www.contentful.com/_next/static/chunks/3128-5ac1c1a085868eda.js	65.9 KiB	33.7 KiB
/16BcqiRsJId123ATa/39239078-882d-46c6-9235-dcd4318a5c73/o...	73.4 KiB	21.5 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.contentful.com/	1.0 MiB
assets.qualified.com/packs/js/widget/sandboxed/messenger-5f040460.js	803.5 KiB
js.qualified.com/qualified.js?token=nCX52tz3bqE643Qo	370.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W94TVR6G	192.6 KiB
www.googletagmanager.com/gtag/js?id=G-REC62920H6&cx=c&gtm=4e6460h1	179.0 KiB
www.googletagmanager.com/gtag/js?id=G-SCQH3CZTQ5&cx=c&gtm=4e6460h1	156.4 KiB
www.googletagmanager.com/gtag/js?id=G-RWVEEBSKZ3&cx=c&gtm=4e6460h1	154.8 KiB
www.googletagmanager.com/gtag/destination?id=AW-788978041&cx=c&gtm=4e6460h1	145.5 KiB
www.googletagmanager.com/gtag/destination?id=DC-14131340&cx=c&gtm=4e6460h1	128.7 KiB
www.contentful.com/_next/static/chunks/3196-4440c14d92fe2cb9.js	120.4 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 20 user timings

●Avoid long main-thread tasks 15 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 100 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 20 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Loading video... `div > div.media_block_assetWrapper__A9Lft > div.media_block_video_video__UzAmu > div.media_block_video_videoSkeleton__QVovV`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Accept All `div.osano-cm-window > div#cf1be2eb-49ca-4b2c-ac3c-86bc871043c6 > div.osano-cm-dialog__buttons > button.osano-cm-accept-all`
Reject Non-Essential `div.osano-cm-window > div#cf1be2eb-49ca-4b2c-ac3c-86bc871043c6 > div.osano-cm-dialog__buttons > button.osano-cm-denyAll`

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
78% increased CVR via personalization `section.logo_metric_root__WDRSB > div.logo_metric_metricsWrapper__aGoT2 > div.logo_metric_metricItem__bQSKp > h4.typography_heading__msTWL`
Modular content, max impact `div.col-span-full > div.copy_block_rootContainer__GVl78 > div.copy_block_container__BcpwE > h4.typography_heading__msTWL`
Manage content `div.icon_with_text_row_root__CPtUb > div.icon_with_text_row_textContainer__RVjUi > span.icon_with_text_row_titleTagContainer__RAwa2 > h4.typography_heading__msTWL`
Growth Marketing `div.icon_with_text_row_root__CPtUb > div.icon_with_text_row_textContainer__RVjUi > span.icon_with_text_row_titleTagContainer__RAwa2 > h4.typography_heading__msTWL`
Professional Services `a.copy_block_link__bsyzV > div.copy_block_rootContainer__GVl78 > div.copy_block_container__BcpwE > h4.typography_heading__msTWL`

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.logo_metric_metricsWrapper__aGoT2 > div.logo_metric_metricItem__bQSKp > div.logo_metric_logoContainer__ZNiK9 > a `div.logo_metric_metricsWrapper__aGoT2 > div.logo_metric_metricItem__bQSKp > div.logo_metric_logoContainer__ZNiK9 > a`
div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI `div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI`
div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI `div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI`
div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI `div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI`
div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI `div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI`
div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI `div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI`
div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI `div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI`
div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI `div.footer_section__5hXz0 > ul.footer_linksList__VNldd > li > a.footer_link__bkRpI`

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

●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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●Document has a `<title>` element

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

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○No form fields have multiple labels

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○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

○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

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.contentful.com/_next/static/chunks/3196-4440c14d92fe2cb9.js line 16, col 5700	`Missing ninetailed_profile_id, cannot track impression [object Object]`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
www.contentful.com/
www.contentful.com/
/16BcqiRsJId123ATa/39239078-882d-46c6-9235-dcd4318a5c73/o...	/16BcqiRsJId123ATa/39239078-882d-46c6-9235-dcd4318a5c73/o...

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

○Redirects HTTP traffic to HTTPS

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`