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

53

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:91.478 source:map[column:7635 line:625 type:source-location url:https://www.jotform.com/ 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:162.251 source:map[column:3605 line:624 type:source-location url:https://www.jotform.com/ urlProvider:network]] map[reflowTime:107.251 source:map[type:text value:[unattributed]]] map[reflowTime:24.953 source:map[column:68 line:98 type:source-location url:https://www.jotform.com/ urlProvider:network]] map[reflowTime:0.323 source:map[column:65286 line:1680 type:source-location url:https://cdn.jotfor.ms/s/umd/d05b4da7ad0/for-embedded-agent.js urlProvider:network]] map[reflowTime:7.926 source:map[column:187043 line:1705 type:source-location url:https://cdn.jotfor.ms/s/umd/d05b4da7ad0/for-embedded-agent.js urlProvider:network]] map[reflowTime:4.969 source:map[column:208856 line:1 type:source-location url:https://consent.cookiebot.com/cf30eb23-2bcc-45fa-ac25-f84b23f37aa9/cc.js?renew=false&referer=www.jotform.com&dnt=false&init=false&culture=en urlProvider:network]] map[reflowTime:2.91 source:map[column:535 line:0 type:source-location url: urlProvider:network]] map[reflowTime:0.411 source:map[column:82434 line:1 type:source-location url:https://consent.cookiebot.com/uc.js?cbid=cf30eb23-2bcc-45fa-ac25-f84b23f37aa9&implementation=gtm&consentmode-dataredaction=dynamic&culture=en urlProvider:network]] map[reflowTime:0.411 source:map[column:376 line:884 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-TDFT5J urlProvider:network]] map[reflowTime:0.232 source:map[column:159106 line:111 type:source-location url:https://cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/index.ee321a88.js urlProvider:network]] map[reflowTime:23.555 source:map[column:22215 line:4026 type:source-location url:https://cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/index.ee321a88.js urlProvider:network]] map[reflowTime:0.471 source:map[column:159206 line:111 type:source-location url:https://cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/index.ee321a88.js urlProvider:network]] map[reflowTime:3.596 source:map[column:20255 line:4026 type:source-location url:https://cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/index.ee321a88.js urlProvider:network]] map[reflowTime:0.987 source:map[column:196745 line:2133 type:source-location url:https://cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/index.ee321a88.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: section.hero > div.things-wrapper > div.things-animate > div.things-line
path: 5,HTML,2,BODY,19,MAIN,0,SECTION,3,DIV,1,DIV,1,DIV
selector: section.hero > div.things-wrapper > div.things-animate > div.things-line
snippet: <div class="things-line">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
cdn.jotfor.ms/fonts/circular/fonts/Circular-Book.woff2http/1.1
cdn.jotfor.ms/fonts/?family=Circularhttp/1.1
cdn.jotfor.ms/s/headerapp/40707c1d2a1/static/css/index.csshttp/1.1
cdn.jotfor.ms/p/_lib/modules/assets/js/jfActions.min.js?v=1.0.0.0.ahttp/1.1
cdn.jotfor.ms/p/_lib/modules/assets/js/CommonLanding.js?ver=3.27http/1.1
/p/homepage/homepage_2021/assets/js/site/logger-factory.m...http/1.1
cdn.jotfor.ms/s/umd/d05b4da7ad0/for-embedded-agent.jshttp/1.1
cdn.jotfor.ms/p/homepage/homepage_2021/assets/img-min/line-sprite-6.pnghttp/1.1
cdn.jotfor.ms/fonts/circular/fonts/Circular-Medium.woff2http/1.1
cdn.jotfor.ms/fonts/circular/fonts/Circular-Bold.woff2http/1.1
cdn.jotfor.ms/p/homepage/homepage_2021/assets/img-min/integrations-2.svghttp/1.1
cdn.jotfor.ms/p/homepage/homepage_2021/assets/img-min/features/payments-2.svghttp/1.1
/p/homepage/homepage_2021/assets/img-min/features/customi...http/1.1
cdn.jotfor.ms/fonts/?family=Inter&display=swaphttp/1.1
cdn.jotfor.ms/s/umd/latest/for-actions.jshttp/1.1
cdn.jotfor.ms/assets/img/ai-agent/autopilot/podo-raising-paw.pnghttp/1.1
cdn.jotfor.ms/assets/img/ai-agent/autopilot/gradient.svghttp/1.1
cdn.jotfor.ms/fonts/inter/fonts/Inter-Regular.woff2http/1.1
cdn.jotfor.ms/fonts/inter/fonts/Inter-SemiBold.woff2http/1.1
cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/jotform.css.9a46f63e.jshttp/1.1
cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/52.5774f904.jshttp/1.1
cdn.jotfor.ms/s/ai-agent/f06051d792f/static/js/index.ee321a88.jshttp/1.1
cdn.jotfor.ms/s/ai-agent/f06051d792f/static/css/jotform.css.csshttp/1.1
cdn.jotfor.ms/s/ai-agent/f06051d792f/static/css/index.csshttp/1.1
cdn.jotfor.ms/s/module-federation/f06051d792f/mf-manifest.jsonhttp/1.1
cdn.jotfor.ms/assets/img/favicons/favicon-2021-light.png?v=0.2http/1.1
cdn.jotfor.ms/s/module-federation/f06051d792f/remoteEntry.jshttp/1.1
cdn.jotfor.ms/s/module-federation/f06051d792f/static/js/2067.b885f3a0.jshttp/1.1
cdn.jotfor.ms/s/module-federation/f06051d792f/static/js/4229.6fa3e6ea.jshttp/1.1
cdn.jotfor.ms/s/module-federation/f06051d792f/static/js/7492.94745aec.jshttp/1.1
/s/module-federation/f06051d792f/static/js/__federation_e...http/1.1
cdn.jotfor.ms/fonts/inter/fonts/Inter-Medium.woff2http/1.1
cdn.jotfor.ms/assets/img/ai-agent/autopilot/podo_welcome.pnghttp/1.1

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

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
/uc.js?cbid=cf30eb23-2bcc-45fa-ac25-f84b23f37aa9&implemen...204.0 s27.0 KiB

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.

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

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 523 ms
URLTime Spent
www.jotform.com/623 ms

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.

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 Evaluation2.3 s
Other999 ms
Script Parsing & Compilation647 ms
Style & Layout458 ms
Parse HTML & CSS185 ms
Rendering87 ms
Garbage Collection80 ms

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 12.0 KiB
URLTransfer SizeEst Savings
cdn.jotfor.ms/p/_lib/modules/assets/js/CommonLanding.js?ver=3.2750.1 KiB12.0 KiB

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
●Improve image delivery
●LCP breakdown
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 9 user timings
●Avoid long main-thread tasks 17 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 10 ms
●Server Backend Latencies 160 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid large layout shifts 6 layout shifts found
○INP breakdown
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
Sign Up for Free nav.sc-jRQBWg > ul.jfRHeader--nav-action > li.jfRHeader--nav-action-item > a.jfRHeader--nav-action-list-signup
EASIEST ONLINE FORM BUILDER body.homepage > main > section.hero > h1.page-title
OR div.trio-wrapper > div.introSection-buttons > div.auth-or > span.locale
Sign Up with an email section.bottomsignup > div.trio-wrapper > div.introSection-buttons > a.trioButton

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
●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.
●Select elements have associated label elements.
●`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
●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 are distinguishable without relying on color.
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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
○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.
○`<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.
96

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.

SourceDescription
Error fetching presentations: [object eb]
Failed to load resource: the server responded with a status of 401 ()
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Uncaught Error: Minified React error #425; visit https://reactjs.org/docs/error-decoder.html?invariant=425 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
●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 DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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.

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

Send Feedback