Lighthouse Mobile

· 0 checks — Mobile 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
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-03.svg	0.0 ms	99.6 KiB
connect.facebook.net/en_US/fbevents.js	1200.0 s	95.0 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-00.svg	0.0 ms	42.2 KiB
js.hs-analytics.net/analytics/1775593800000/7660877.js	300.0 s	42.3 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-04.svg	0.0 ms	40.0 KiB
/signals/config/2798481670371131?v=2.9.291&r=stable&domai...	1200.0 s	39.2 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-01.svg	0.0 ms	32.7 KiB
p.retool.com/analytics.js/v1/uTqZjk9nuBRPz3zsAwaa5BvzzN76naLF/analytics.min.js	0.0 ms	30.2 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-02.svg	0.0 ms	29.2 KiB
js.hs-banner.com/v2/7660877/banner.js	300.0 s	24.1 KiB
/next-integrations/integrations/vendor/commons.59560acdd6...	0.0 ms	21.9 KiB
www.redditstatic.com/ads/pixel.js	60.0 s	19.0 KiB
/next-integrations/integrations/visual-tagger/0.3.5/visua...	0.0 ms	15.7 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/conagra-white.svg	0.0 ms	11.5 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.7 KiB
static.hotjar.com/c/hotjar-3118933.js?sv=7	60.0 s	6.2 KiB
cdn.cr-relay.com/v1/site/e31b3274-5e9a-4b31-9208-4c77a04b9ed1/signals.js	3600.0 s	7.1 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/quest-diagnostics-white.svg	0.0 ms	5.5 KiB
/next-integrations/integrations/google-analytics/2.18.6/g...	0.0 ms	5.1 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/amazon-white.svg	0.0 ms	4.4 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/burgerking-white.svg	0.0 ms	3.4 KiB
/next-integrations/integrations/facebook-pixel/2.11.5/fac...	0.0 ms	3.4 KiB
/analytics-next/bundles/ajs-destination.bundle.8e6b895db7...	0.0 ms	3.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/orange-theory-white.svg	0.0 ms	3.0 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/pernod%20ricard-white.svg	0.0 ms	2.4 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/taco-bell-white.svg	0.0 ms	2.4 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/postgresql.svg	0.0 ms	2.4 KiB
/next-integrations/integrations/twitter-ads/2.5.4/twitter...	0.0 ms	2.4 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/gong-white.svg	0.0 ms	2.3 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/salesforce.svg	0.0 ms	2.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/reckitt-white.svg	0.0 ms	2.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/amazon-bedrock.svg	0.0 ms	2.0 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/pinterest-white.svg	0.0 ms	1.9 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/boeing-white.svg	0.0 ms	1.9 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/doordash-white.svg	0.0 ms	1.8 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/adobe-white.svg	0.0 ms	1.8 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/nvidia-white.svg	0.0 ms	1.8 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/microsoft-teams.svg	0.0 ms	1.7 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/electronic-arts-white.svg	0.0 ms	1.7 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/mysql.svg	0.0 ms	1.5 KiB
/next-integrations/integrations/google-tag-manager/2.5.3/...	0.0 ms	1.5 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/pfizer-white.svg	0.0 ms	1.5 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/openai.svg	0.0 ms	1.3 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/ramp-white.svg	0.0 ms	1.3 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/airtable.svg	0.0 ms	1.3 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/openai-white.svg	0.0 ms	1.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/lyft-white.svg	0.0 ms	1.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/slack.svg	0.0 ms	1.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/intercom.svg	0.0 ms	1.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/stripe-white.svg	0.0 ms	1.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/unity-white.svg	0.0 ms	1.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/stripe.svg	0.0 ms	1.1 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/brex-white.svg	0.0 ms	1.1 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/google-gemini.svg	0.0 ms	1.0 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/google-sheets.svg	0.0 ms	1.0 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/bigquery.svg	0.0 ms	1.0 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/philips-white.svg	0.0 ms	1.0 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/hubspot.svg	0.0 ms	1010 B
js.hs-scripts.com/7660877.js	90.0 s	1018 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/workday.svg	0.0 ms	998 B
p.retool.com/analytics-next/bundles/schemaFilter.bundle.1b218d13fed021531d4e.js	0.0 ms	910 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/mongodb.svg	0.0 ms	882 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/zendesk.svg	0.0 ms	863 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/anthropic.svg	0.0 ms	663 B
/rp.gif?ts=1775593958357&id=t2_60j2xevv&event=PageVisit&m...	0.0 ms	637 B
/collect?v=2&fmt=js&pid=2414948&time=1775593958385&li_ads...	0.0 ms	454 B
/tr/?id=2798481670371131&ev=PageView&dl=https%3A%2F%2Fret...	0.0 ms	16 B
/tr/?id=2798481670371131&ev=Experiment%20Viewed&dl=https%...	0.0 ms	16 B

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:96.148 source:map[column:22089 line:2 type:source-location url:https://retool.com/_next/static/chunks/255d11a380c0e2b5.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:78.688 source:map[type:text value:[unattributed]]] map[reflowTime:28.92 source:map[column:15729 line:7 type:source-location url:https://retool.com/_next/static/chunks/1f06b11aa4346ab6.js urlProvider:network]] map[reflowTime:28.797 source:map[column:94635 line:24 type:source-location url:https://retool.com/_next/static/chunks/08f41d4d5a44766c.js urlProvider:network]] map[reflowTime:16.525 source:map[column:14657 line:7 type:source-location url:https://retool.com/_next/static/chunks/1f06b11aa4346ab6.js urlProvider:network]] map[reflowTime:21.906 source:map[column:105425 line:24 type:source-location url:https://retool.com/_next/static/chunks/08f41d4d5a44766c.js urlProvider:network]] map[reflowTime:0.472 source:map[column:86058 line:22 type:source-location url:https://js.hs-analytics.net/analytics/1775593800000/7660877.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:47.179 label:Time to first byte subpart:timeToFirstByte] map[duration:2487.131 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-H1

nodeLabel: Build how you want. Ship on a platform you can trust.

path: 1,HTML,1,BODY,1,DIV,0,DIV,3,MAIN,0,DIV,0,SECTION,0,DIV,1,DIV,1,DIV,0,H1

selector: div.grid-wrapper > div.grid-span-start-inner-to-end-inner > div.flex > h1.headline-md

snippet: <h1 class="headline-md lg:headline-lg text-surface-text-primary text-center">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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.

URL	Transfer Size	Duration
retool.com/_next/static/chunks/3517f4bd16ff63db.css	14.4 KiB	303 ms
retool.com/_next/static/chunks/77466b1bebd9b1ec.css	2.4 KiB
retool.com/_next/static/chunks/e0b3fb2a0d2fe518.css	588 B
retool.com/_next/static/chunks/01c248daf9e05b4f.css	301 B

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
An illustration of a lush app layer dreamscape with structures covered in plant… `div.relative > div.absolute > picture.absolute > img.absolute`	/_next/image?url=https%3A%2F%2Fdqpcjghenxt8u.cloudfront.n...	34.7 KiB	24.2 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: 765 ms

URL	Time Spent
www.retool.com/	765 ms
retool.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

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

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: 450 ms 72.5 KiB

URL	Transfer Size	Est Savings
retool.com/_next/static/chunks/6a1e75717a24d786.css	64.2 KiB	58.7 KiB
retool.com/_next/static/chunks/3517f4bd16ff63db.css	14.3 KiB	13.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: 1.8 s 538.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-WHDC2N5&l=dataLayer	156.9 KiB	107.9 KiB
retool.com/_next/static/chunks/0659e107baf05443.js	91.3 KiB	86.5 KiB
www.googletagmanager.com/gtag/js?id=G-Y9141XKQB4&cx=c&gtm=4e6461h2	176.0 KiB	69.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHDC2N5	157.0 KiB	64.5 KiB
cdn.intellimize.co/snippet/117371543.js	124.5 KiB	44.4 KiB
retool.com/_next/static/chunks/9a0bb78c98ed5400.js	43.2 KiB	43.1 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	37.8 KiB
retool.com/_next/static/chunks/1e0b84fcd5f11d4b.js	61.4 KiB	32.6 KiB
connect.facebook.net/en_US/fbevents.js	94.8 KiB	29.9 KiB
retool.com/_next/static/chunks/255d11a380c0e2b5.js	71.9 KiB	22.2 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.

URL	Total CPU Time	Script Evaluation	Script Parse
retool.com/_next/static/chunks/1e0b84fcd5f11d4b.js	3.9 s	1.2 s	18 ms
retool.com/_next/static/chunks/255d11a380c0e2b5.js	3.8 s	3.1 s	34 ms
retool.com/	3.5 s	24 ms	41 ms
Unattributable	2.6 s	225 ms	0.0 ms
js.hs-analytics.net/analytics/1775593800000/7660877.js	960 ms	732 ms	10 ms
scripts.clarity.ms/0.8.59/clarity.js	705 ms	644 ms	22 ms
www.googletagmanager.com/gtm.js?id=GTM-WHDC2N5	543 ms	466 ms	45 ms
cdn.intellimize.co/snippet/117371543.js	438 ms	367 ms	61 ms
www.googletagmanager.com/gtag/js?id=G-Y9141XKQB4&cx=c&gtm=4e6461h2	407 ms	341 ms	54 ms
retool.com/_next/static/chunks/8c85ef5c5e11eff8.js	388 ms	386 ms	0.6 ms
www.googletagmanager.com/gtm.js?id=GTM-WHDC2N5&l=dataLayer	298 ms	214 ms	72 ms
connect.facebook.net/en_US/fbevents.js	215 ms	170 ms	42 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	197 ms	154 ms	35 ms
/signals/config/2798481670371131?v=2.9.291&r=stable&domai...	196 ms	158 ms	37 ms
/next-integrations/integrations/vendor/commons.59560acdd6...	144 ms	127 ms	6.5 ms
/analytics-next/bundles/ajs-destination.bundle.8e6b895db7...	135 ms	125 ms	1.0 ms
static.ads-twitter.com/uwt.js	118 ms	95 ms	20 ms
retool.com/_next/static/chunks/a09c2e3574ddda50.js	106 ms	88 ms	7.5 ms
www.google-analytics.com/analytics.js	89 ms	67 ms	20 ms
retool.com/_next/static/chunks/e3f6e70112f5c4bf.js	57 ms	45 ms	9.5 ms
snap.licdn.com/li.lms-analytics/insight.min.js	54 ms	47 ms	5.7 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	9.8 s
Other	5.9 s
Rendering	1.6 s
Style & Layout	1.5 s
Script Parsing & Compilation	820 ms
Parse HTML & CSS	401 ms
Garbage Collection	234 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 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

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

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 7 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 3 animated elements found

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

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 830 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 0 ms

○INP breakdown

○LCP request discovery

○Avoid large layout shifts

100

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.

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

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

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

●ARIA input fields 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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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 / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

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
/api/4509255529791488/envelope/?sentry_version=7&sentry_k...	`Failed to load resource: the server responded with a status of 429 ()`

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

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`