Skip to content
https://www.retool.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.

55

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:73.691 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:120.656 source:map[type:text value:[unattributed]]] map[reflowTime:31.523 source:map[column:15729 line:7 type:source-location url:https://retool.com/_next/static/chunks/1f06b11aa4346ab6.js urlProvider:network]] map[reflowTime:42.168 source:map[column:94635 line:24 type:source-location url:https://retool.com/_next/static/chunks/08f41d4d5a44766c.js urlProvider:network]] map[reflowTime:16.883 source:map[column:25240 line:7 type:source-location url:https://retool.com/_next/static/chunks/1f06b11aa4346ab6.js urlProvider:network]] map[reflowTime:0.465 source:map[column:47078 line:1 type:source-location url:https://retool.com/_next/static/chunks/b2185d53c1de9941.js urlProvider:network]] map[reflowTime:20.78 source:map[column:105425 line:24 type:source-location url:https://retool.com/_next/static/chunks/08f41d4d5a44766c.js urlProvider:network]] map[reflowTime:1.543 source:map[column:86058 line:22 type:source-location url:https://js.hs-analytics.net/analytics/1775593800000/7660877.js urlProvider:network]] map[reflowTime:0.695 source:map[column:101328 line:22 type:source-location url:https://js.hs-analytics.net/analytics/1775593800000/7660877.js urlProvider:network]] map[reflowTime:1.653 source:map[column:31518 line:1 type:source-location url:https://scripts.clarity.ms/0.8.59/clarity.js urlProvider:network]] map[reflowTime:1.638 source:map[column:255920 line:3 type:source-location url:https://cdn.intellimize.co/snippet/117371543.js urlProvider:network]]]

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
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...142.0 KiB53.0 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.

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

RequestCache TTLTransfer Size
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-03.svg0.0 ms99.6 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s95.0 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-00.svg0.0 ms42.2 KiB
js.hs-analytics.net/analytics/1775593800000/7660877.js300.0 s42.3 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-04.svg0.0 ms40.0 KiB
/signals/config/2798481670371131?v=2.9.291&r=stable&domai...1200.0 s39.2 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-01.svg0.0 ms32.7 KiB
p.retool.com/analytics.js/v1/uTqZjk9nuBRPz3zsAwaa5BvzzN76naLF/analytics.min.js0.0 ms30.2 KiB
dqpcjghenxt8u.cloudfront.net/page-assets/homepage-assist/hero-use-case-02.svg0.0 ms29.2 KiB
js.hs-banner.com/v2/7660877/banner.js300.0 s24.1 KiB
/next-integrations/integrations/vendor/commons.59560acdd6...0.0 ms21.9 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
/next-integrations/integrations/visual-tagger/0.3.5/visua...0.0 ms15.7 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/conagra-white.svg0.0 ms11.5 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
static.hotjar.com/c/hotjar-3118933.js?sv=760.0 s6.2 KiB
cdn.cr-relay.com/v1/site/e31b3274-5e9a-4b31-9208-4c77a04b9ed1/signals.js3600.0 s7.1 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/quest-diagnostics-white.svg0.0 ms5.5 KiB
/next-integrations/integrations/google-analytics/2.18.6/g...0.0 ms5.1 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/amazon-white.svg0.0 ms4.4 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/burgerking-white.svg0.0 ms3.4 KiB
/next-integrations/integrations/facebook-pixel/2.11.5/fac...0.0 ms3.4 KiB
/analytics-next/bundles/ajs-destination.bundle.8e6b895db7...0.0 ms3.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/orange-theory-white.svg0.0 ms3.0 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/pernod%20ricard-white.svg0.0 ms2.4 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/taco-bell-white.svg0.0 ms2.4 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/postgresql.svg0.0 ms2.4 KiB
/next-integrations/integrations/twitter-ads/2.5.4/twitter...0.0 ms2.4 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/gong-white.svg0.0 ms2.3 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/salesforce.svg0.0 ms2.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/reckitt-white.svg0.0 ms2.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/amazon-bedrock.svg0.0 ms2.0 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/pinterest-white.svg0.0 ms1.9 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/boeing-white.svg0.0 ms1.9 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/doordash-white.svg0.0 ms1.8 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/adobe-white.svg0.0 ms1.8 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/nvidia-white.svg0.0 ms1.8 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/microsoft-teams.svg0.0 ms1.7 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/electronic-arts-white.svg0.0 ms1.7 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/mysql.svg0.0 ms1.5 KiB
/next-integrations/integrations/google-tag-manager/2.5.3/...0.0 ms1.5 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/pfizer-white.svg0.0 ms1.5 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/snowflake.svg0.0 ms1.4 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/openai.svg0.0 ms1.3 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/ramp-white.svg0.0 ms1.3 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/airtable.svg0.0 ms1.3 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/openai-white.svg0.0 ms1.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/lyft-white.svg0.0 ms1.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/slack.svg0.0 ms1.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/intercom.svg0.0 ms1.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/stripe-white.svg0.0 ms1.2 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/unity-white.svg0.0 ms1.2 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/stripe.svg0.0 ms1.1 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/brex-white.svg0.0 ms1.1 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/google-gemini.svg0.0 ms1.1 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/google-sheets.svg0.0 ms1.0 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/bigquery.svg0.0 ms1.0 KiB
dqpcjghenxt8u.cloudfront.net/customer-logos/philips-white.svg0.0 ms1.0 KiB
dqpcjghenxt8u.cloudfront.net/api-integration-logos/hubspot.svg0.0 ms1009 B
js.hs-scripts.com/7660877.js90.0 s1014 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/workday.svg0.0 ms996 B
p.retool.com/analytics-next/bundles/schemaFilter.bundle.1b218d13fed021531d4e.js0.0 ms910 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/mongodb.svg0.0 ms882 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/zendesk.svg0.0 ms864 B
dqpcjghenxt8u.cloudfront.net/api-integration-logos/anthropic.svg0.0 ms665 B
/rp.gif?ts=1775593990616&id=t2_60j2xevv&event=PageVisit&m...0.0 ms637 B
/collect?v=2&fmt=js&pid=2414948&time=1775593990595&li_ads...0.0 ms272 B
/tr/?id=2798481670371131&ev=PageView&dl=https%3A%2F%2Fret...0.0 ms16 B
/tr/?id=2798481670371131&ev=Experiment%20Viewed&dl=https%...0.0 ms16 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.

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

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: 229 ms
URLTime Spent
www.retool.com/229 ms
retool.com/0.0 ms

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: 40 ms 68.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.

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
Other30.6 s
Script Evaluation4.9 s
Rendering1.3 s
Style & Layout739 ms
Script Parsing & Compilation208 ms
Garbage Collection195 ms
Parse HTML & CSS48 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 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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 9 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 730 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
82

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Add more integrations span.relative > span#toollist > span.CursorBox-module__BbHciq__cursorBox > button.absolute

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
compliance dashboard div.group/hero-mad-lib-text > span.relative > div#variable-word-text-outer > span#variable-word-text-inner
tracks SLA compliance by region and team div.group/hero-mad-lib-text > span.relative > div#variable-word-text-outer > span#variable-word-text-inner

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
span.relative > span#toollist > span.CursorBox-module__BbHciq__cursorBox > button.absolute span.relative > span#toollist > span.CursorBox-module__BbHciq__cursorBox > button.absolute

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.

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
GET ANY MODEL div.flex > div.flex > div.text-caption > h4.text-string
USE YOUR DATA div.flex > div.flex > div.text-caption > h4.text-string
BRING YOUR APIS div.flex > div.flex > div.text-caption > h4.text-string
CONNECT YOUR APPS div.flex > div.flex > div.text-caption > h4.text-string

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-*]` 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
●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
●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
●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
○Links are distinguishable without relying on color.
○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.
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
AttributionReporting

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

Send Feedback