Skip to content
https://answerthepublic.com

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.

66

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:70.102 source:map[column:64946 line:20 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/0p0_b9yvkv56l.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:0.955 source:map[column:32211 line:1 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/0zhiqmggtic...js urlProvider:network]] map[reflowTime:65.345 source:map[column:69998 line:1 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/0murmkj9cclgg.js urlProvider:network]] map[reflowTime:2.197 source:map[column:2092 line:1 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/0aha8-wl_bw2b.js urlProvider:network]] map[reflowTime:1.605 source:map[column:25197 line:1 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/16pkzoxp1dpwh.js urlProvider:network]] map[reflowTime:0.518 source:map[column:8091 line:1 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/11j3b6y_yv97x.js urlProvider:network]] map[reflowTime:2.5 source:map[column:13881 line:1 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/16pkzoxp1dpwh.js urlProvider:network]] map[reflowTime:11.789 source:map[type:text value:[unattributed]]] map[reflowTime:0.078 source:map[column:25541 line:1 type:source-location url:https://atp-cdn.neilpatelapi.com/live/7c3bef8/_next/static/chunks/16pkzoxp1dpwh.js urlProvider:network]] map[reflowTime:0.37 source:map[column:376 line:763 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-58H425SCBW urlProvider:network]] map[reflowTime:0.485 source:map[column:189824 line:3 type:source-location url:https://script.hotjar.com/modules.6a0f3932cb1341a35c18.js urlProvider:network]] map[reflowTime:0.132 source:map[column:17869 line:21 type:source-location url:https://js-eu1.hs-analytics.net/analytics/1776892500000/25525864.js urlProvider:network]] map[reflowTime:0.566 source:map[column:86058 line:21 type:source-location url:https://js-eu1.hs-analytics.net/analytics/1776892500000/25525864.js 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
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.

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
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step3-frame-07.png...605.7 KiB554.7 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step3-frame-06.png...598.7 KiB547.7 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step3-frame-05.png...592.4 KiB541.4 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step3-frame-04.png...581.5 KiB530.5 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step2-frame-04.png...512.2 KiB461.2 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step3-frame-03.png...481.8 KiB430.8 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step2-frame-03.png...467.4 KiB416.4 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step2-frame-02.png...361.2 KiB316.9 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step4-frame-03.png...305.6 KiB268.2 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step3-frame-02.png...264.2 KiB231.8 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step4-frame-02.png...245.0 KiB215.0 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-08.png...219.3 KiB192.4 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-07.png...209.3 KiB183.6 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-06.png...195.5 KiB171.6 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-05.png...186.2 KiB163.4 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-04.png...174.7 KiB153.3 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step4-frame-05.png...167.8 KiB147.3 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-03.png...159.3 KiB139.8 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-02.png...151.8 KiB133.2 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step4-frame-04.png...94.5 KiB82.9 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step2-frame-01.png...31.0 KiB27.2 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step4-frame-01.png...30.2 KiB26.5 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step1-frame-01.png...30.0 KiB26.3 KiB
div.relative > div.transition-opacity > div.relative > img.h-auto div.relative > div.transition-opacity > div.relative > img.h-auto
/live/7c3bef8/public/home/how-it-works/step3-frame-01.png...29.1 KiB25.5 KiB
BOTTLE PR logo div.relative > div.flex > div.mr-0 > img.mx-auto
/live/7c3bef8/public/marketing-imgs/bottle-logo.png?forma...5.3 KiB4.8 KiB

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

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

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.

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 Evaluation1.7 s
Other955 ms
Style & Layout178 ms
Script Parsing & Compilation175 ms
Garbage Collection68 ms
Rendering55 ms
Parse HTML & CSS16 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 reasonFailure 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

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

●Layout shift culprits
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 10 user timings
●Avoid long main-thread tasks 10 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 70 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 20 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○LCP request discovery
91

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Iniciar sesión Empezar nav.relative > div.flex > div.flex > div#radix-_r_6_
Crea una cuenta GRATIS y obtén: 3 búsquedas diarias más datos de palabras clav… body.flex > div > div#radix-_r_7_

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
Obtén 3 búsquedas gratis al día div.mt-12 > div.-mt-2 > div.m-0 > button.flex
Escribe cualquier tema o ingresa tu sitio web div.grid > div.flex > button.cursor-pointer > p.font-geomanist
cualquier tema div.flex > button.cursor-pointer > p.font-geomanist > span.text-orange-500
sitio web div.flex > button.cursor-pointer > p.font-geomanist > span.text-orange-500
Una palabra clave o URL es todo lo que necesitas. div.grid > div.flex > button.cursor-pointer > p.font-roboto
Convierte preguntas en contenido que posiciona div.grid > div.flex > button.cursor-pointer > p.font-geomanist
contenido que posiciona div.flex > button.cursor-pointer > p.font-geomanist > span.text-orange-500
Selecciona cualquier resultado o tema que valga la pena posicionar y nuestra IA… div.grid > div.flex > button.cursor-pointer > p.font-roboto
Publica sin salir de la plataforma div.grid > div.flex > button.cursor-pointer > p.font-geomanist
Publica div.flex > button.cursor-pointer > p.font-geomanist > span.text-orange-500
Publica con un clic. Posiciona para preguntas reales. Aumenta el tráfico que re… div.grid > div.flex > button.cursor-pointer > p.font-roboto
Obtén 3 búsquedas gratis al día button.font-roboto > div > div.relative > span.font-roboto

These are opportunities to improve the legibility of your content.

○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>`
●`[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
●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.
●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
●ARIA IDs are unique
●Elements with visible text labels have matching accessible names.
○`[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 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
○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
○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
○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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge

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.

SourceDescription
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 401 ()
Failed to load resource: the server responded with a status of 401 ()
ReferenceError: jQuery is not defined at <anonymous>:1:161 at https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:775:429 at vR (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:777:31) at Nd.uR (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:774:92) at Nd.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:280:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:209:466) at gb (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:172:719) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:172:470) at Nd.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:233:473) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:209:466)
TypeError: Cannot read properties of undefined (reading 'experiences') at <anonymous>:1:15 at https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:775:429 at vR (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:777:31) at Nd.uR (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:774:92) at Nd.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:280:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:209:466) at gb (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:172:719) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:172:470) at Nd.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:233:473) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-5RJVDDR:209:466)
●Uses HTTPS
●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 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
85

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

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Why this matters

Performance issues directly impact user engagement and conversion rates.

head > link
head > link
head > link
head > link
head > link
head > link
head > link

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Why this matters

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

Source: MDN Permissions-Policy

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 have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes

Send Feedback