Skip to content
https://netlify.app

Lighthouse Mobile

· 0 checks — Mobile 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.

45

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:9.759 source:map[column:69646 line:7 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:46.14 source:map[column:81 line:177 type:source-location url:https://www.netlify.com/ urlProvider:network]] map[reflowTime:141.892 source:map[type:text value:[unattributed]]] map[reflowTime:0.882 source:map[column:6737 line:62 type:source-location url:https://www.netlify.com/_astro/preact.DuZyKc4a.js urlProvider:network]] map[reflowTime:9.759 source:map[column:349419 line:6 type:source-location url:https://cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js urlProvider:network]] map[reflowTime:0.959 source:map[column:86058 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1776798000000/7477936.js urlProvider:network]] map[reflowTime:0.82 source:map[column:380 line:580 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.453 source:map[column:47 line:303 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.751 source:map[column:55 line:947 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-X2FMMZSSS9&cx=c&gtm=4e64h1 urlProvider:network]] map[reflowTime:2.815 source:map[column:332 line:412 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:6.927 source:map[column:17869 line:44 type:source-location url:https://js.hs-analytics.net/analytics/1776798000000/7477936.js urlProvider:network]] map[reflowTime:1.443 source:map[column:391 line:1 type:source-location url: urlProvider:network]]]

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.

URLTransfer SizeDuration
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js6.9 KiB774 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js9.1 KiB153 ms
www.netlify.com/_astro/convince-your-boss.Bd6jOyPR.css26.2 KiB305 ms
www.netlify.com/_astro/index._tGI3oyO.css1.3 KiB
www.netlify.com/_astro/index.CswAyQBw.css7.9 KiB152 ms
www.netlify.com/_astro/index.DEYu2GN_.css1.5 KiB

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.

RequestCache TTLTransfer Size
js.hsforms.net/forms/v2.js300.0 s193.8 KiB
js.hs-analytics.net/analytics/1776798000000/7477936.js300.0 s43.1 KiB
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js86400.0 s103.0 KiB
/analytics.js/v1/7f8W9mAxost9lRWyMuVR8xaMv9kHxBsy/analyti...120.0 s30.0 KiB
js.hubspot.com/web-interactives-embed.js600.0 s28.0 KiB
js.hs-banner.com/v2/7477936/banner.js300.0 s24.1 KiB
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js0.0 ms9.2 KiB
cdn.cookielaw.org/logos/static/ot_company_logo.png86400.0 s19.1 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s9.1 KiB
js.hsadspixel.net/pixels.js600.0 s3.9 KiB
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js86400.0 s6.9 KiB
/next-integrations/actions/amplitude-plugins/f12a4347e108...0.0 ms2.7 KiB
join.netlify.com/pr/js14400.0 s3.5 KiB
js.hs-scripts.com/7477936.js90.0 s1.1 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg86400.0 s2.6 KiB
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
www.gstatic.com/recaptcha/api2/info_2x.png604800.0 s689 B
www.gstatic.com/recaptcha/api2/refresh_2x.png604800.0 s624 B
www.gstatic.com/recaptcha/api2/audio_2x.png604800.0 s554 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s0 B

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.

URLEst Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff210 ms

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

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 763 ms
URLTime Spent
netlify.app/763 ms
www.netlify.com/0.0 ms

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: 300 ms 883.2 KiB
URLTransfer SizeEst Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB244.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB161.9 KiB
www.googletagmanager.com/gtag/js?id=AW-957669464145.7 KiB106.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-T7WNFLD165.9 KiB79.8 KiB
js.hsforms.net/forms/v2.js186.4 KiB71.9 KiB
www.googletagmanager.com/gtag/js?id=G-X2FMMZSSS9&cx=c&gtm=4e64h1178.6 KiB66.6 KiB
www.googletagmanager.com/gtag/js?id=AW-957669464&cx=c&gtm=4e64h1146.0 KiB55.5 KiB
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js102.8 KiB52.5 KiB
www.netlify.com/_astro/preact.DuZyKc4a.js96.0 KiB44.7 KiB

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.

URLTotal CPU TimeScript EvaluationScript Parse
www.netlify.com/4.0 s78 ms13 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js3.2 s2.5 s549 ms
Unattributable1.4 s360 ms0.0 ms
js.hs-analytics.net/analytics/1776798000000/7477936.js1.0 s675 ms22 ms
www.googletagmanager.com/gtag/js?id=G-X2FMMZSSS9&cx=c&gtm=4e64h1902 ms661 ms74 ms
www.googletagmanager.com/gtm.js?id=GTM-T7WNFLD514 ms444 ms53 ms
js.hsforms.net/forms/v2.js492 ms405 ms59 ms
www.googletagmanager.com/gtag/js?id=AW-957669464&cx=c&gtm=4e64h1417 ms350 ms64 ms
cdn.cookielaw.org/scripttemplates/202311.1.0/otBannerSdk.js410 ms305 ms44 ms
cdn.cookielaw.org/consent/5dec0507-5e89-4bb4-8f2d-0872be7dd9dd/OtAutoBlock.js181 ms167 ms9.0 ms
cdn.segment.com/next-integrations/actions/3962/1faa179dfb20d0a3f5a0.js158 ms149 ms3.2 ms
www.googletagmanager.com/gtag/js?id=AW-957669464113 ms51 ms62 ms
js.hubspot.com/web-interactives-embed.js104 ms90 ms9.7 ms
www.netlify.com/_astro/preact.DuZyKc4a.js83 ms26 ms1.4 ms
/analytics.js/v1/7f8W9mAxost9lRWyMuVR8xaMv9kHxBsy/analyti...61 ms43 ms16 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js58 ms35 ms2.5 ms
www.netlify.com/_astro/preact.module.YZDSOCcU.js53 ms46 ms0.2 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.

CategoryTime Spent
Script Evaluation6.7 s
Other2.7 s
Style & Layout2.1 s
Script Parsing & Compilation1.0 s
Rendering744 ms
Garbage Collection176 ms
Parse HTML & CSS157 ms

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: 0.0 ms 16.3 KiB
URLTransfer SizeEst Savings
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …19.1 KiB16.3 KiB

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

●Layout shift culprits
●Optimize DOM size
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,654 KiB
●User Timing marks and measures 10 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 4 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 120 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
97

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
KUBERNETES CONTRIBUTOR, HEAD OF PROJECTS AT CNCF figure > figcaption > div.n-blockquote-author-info > span.n-blockquote-title

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read our Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●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
●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 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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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 type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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
●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
○Use a strong HSTS policy
92

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 destinationLink Text
cookiepedia.co.uk/giving-consent-to-cookiesMore information

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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback