Lighthouse Desktop

· 0 checks — Desktop 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
m.servedby-buysellads.com/monetization.js	0.0 ms	16.8 KiB
cdn.carbonads.com/carbon.js?serve=CW7DC2JY&placement=jsfiddlenet&format=cover	0.0 ms	10.1 KiB
jsfiddle.net/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	12.0 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 KiB
srv.carbonads.net/static/30242/098773e74d968c8e0edcdad13b1d1d7b5a51b54b	604800.0 s	5.6 KiB
srv.carbonads.net/static/30242/2225443300037de2b6936e88f489d946d41150f7	604800.0 s	2.9 KiB

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:27.118 source:map[column:39 line:155 type:source-location url:https://jsfiddle.net/ 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.905 source:map[column:1391 line:0 type:source-location url:https://jsfiddle.net/js/_dist-editor.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:1.913 source:map[column:2534 line:0 type:source-location url:https://jsfiddle.net/js/_dist-editor.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:0.927 source:map[column:5769 line:0 type:source-location url:https://jsfiddle.net/js/_dist-editor.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:9.92 source:map[column:40726 line:600 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:10.986 source:map[column:5348 line:74 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:1.091 source:map[column:91604 line:121 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:0.132 source:map[column:2952 line:632 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:0.909 source:map[column:34648 line:0 type:source-location url:https://jsfiddle.net/js/_dist-editor.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:0.335 source:map[column:20748 line:0 type:source-location url:https://jsfiddle.net/js/_dist-editor.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:48.522 source:map[type:text value:[unattributed]]] map[reflowTime:0.825 source:map[column:85579 line:121 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:4.08 source:map[column:8474 line:668 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:0.226 source:map[column:4213 line:6 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d urlProvider:network]] map[reflowTime:0.499 source:map[column:54972 line:600 type:source-location url:https://jsfiddle.net/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b050a5a2ca908634e556824833385a8472d 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-A

nodeLabel: Start building with your free plan Meet our new Free Plan: 25K MAUs, agentic AI…

path: 1,HTML,1,BODY,1,FORM,2,ASIDE,3,SECTION,0,DIV,3,DIV,0,DIV,0,A

selector: div.twitterCont > div#carbonads > div#carbon-cover > a.carbon-reveal

snippet: <a href="https://srv.carbonads.net/ads/click/x/GTND427UCYADK23UCKS4YKQUCASDC537CYSD…" rel="noopener sponsored" target="_blank" class="carbon-reveal">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b...	1.1 MiB	1.2 s
/js/lib/monaco-editor/min/vs/editor/editor.main.css?a5d18...	25.9 KiB	294 ms
/js/lib/monaco-editor/min/vs/loader.js?a5d18b050a5a2ca908...	10.6 KiB	236 ms
jsfiddle.net/js/_dist-editor.js?a5d18b050a5a2ca908634e556824833385a8472d	23.6 KiB	294 ms
jsfiddle.net/css/dist-editor.css?a5d18b050a5a2ca908634e556824833385a8472d	14.1 KiB	236 ms
jsfiddle.net/css/dist-skeleton.css?a5d18b050a5a2ca908634e556824833385a8472d	4.4 KiB	64 ms
m.servedby-buysellads.com/monetization.js	16.8 KiB	289 ms
cdn.carbonads.com/carbon.js?serve=CW7DC2JY&placement=jsfiddlenet&format=cover	10.1 KiB	245 ms

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 520 ms 616.1 KiB

URL	Transfer Size	Est Savings
/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b...	1.1 MiB	616.1 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 24.6 KiB

URL	Transfer Size	Est Savings
/js/lib/monaco-editor/min/vs/editor/editor.main.css?a5d18...	25.4 KiB	24.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
jsfiddle.net/js/lib/monaco-editor/min/vs/language/typescript/tsWorker.js	1.4 MiB
/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b...	1.1 MiB
jsfiddle.net/js/lib/monaco-editor/min/vs/language/css/cssWorker.js	180.9 KiB
jsfiddle.net/font/MonaspaceArgonVarVF[wght,wdth,slnt].woff2	140.6 KiB
jsfiddle.net/js/lib/monaco-editor/min/vs/base/worker/workerMain.js	124.9 KiB
jsfiddle.net/js/lib/monaco-editor/min/vs/language/html/htmlWorker.js	119.6 KiB
jsfiddle.net/cf-fonts/v/inter/5.0.16/latin/wght/normal.woff2	47.6 KiB
cdn.jsdelivr.net/npm/emmet-monaco-es@5.5.0/+esm	32.4 KiB
jsfiddle.net/	31.3 KiB
/js/lib/monaco-editor/min/vs/editor/editor.main.css?a5d18...	25.9 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Auth0 `div#carbonads > div#carbon-cover > a.carbon-reveal > img.carbon-large-image`	srv.carbonads.net/static/30242/098773e74d968c8e0edcdad13b1d1d7b5a51b54b
a.carbon-reveal > div.carbon-main > div.carbon-logo > img `a.carbon-reveal > div.carbon-main > div.carbon-logo > img`	srv.carbonads.net/static/30242/2225443300037de2b6936e88f489d946d41150f7

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

●Time to Interactive 2.4 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 1 animated element found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

○User Timing marks and measures

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
AN `ul.headerActions > li.fiddleAuthor > div#author-info > span.pseudoAvatar`
Run `ul#actions > li.runButton > a#run > span`
JSFIDDLE APPS `aside#sidebar > section#sidebar-main > div#apps > h4`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI Code Completion `aside#sidebar > section#sidebar-main > div.sidebarItem > h3.toggler`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#header > ul#actions > li.saveButton > a#save `header#header > ul#actions > li.saveButton > a#save`
header#header > ul#actions > li.collaborateButton > a#collaborate `header#header > ul#actions > li.collaborateButton > a#collaborate`
header#header > ul#actions > li.gridButton > a#switch-grid `header#header > ul#actions > li.gridButton > a#switch-grid`
header#header > ul#actions > li.settingsButton > a.showModalTrigger `header#header > ul#actions > li.settingsButton > a.showModalTrigger`
header#header > ul#actions > li.themeButton > a#switch-theme `header#header > ul#actions > li.themeButton > a#switch-theme`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●Form elements have associated labels

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

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

○Buttons have an accessible name

○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 a valid value for its `[lang]` attribute

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

○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

User Experience

Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Editor content `div#panel-code-html > div.monaco-editor > div.overflow-guard > textarea.inputarea`
Editor content `div#panel-code-js > div.monaco-editor > div.overflow-guard > textarea.inputarea`
Editor content `div#panel-code-css > div.monaco-editor > div.overflow-guard > textarea.inputarea`

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
SharedStorage	jsfiddle.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	jsfiddle.net/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	jsfiddle.net/cdn-cgi/challenge-platform/scripts/jsd/main.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
jsfiddle.net/ line 1211, col 0	`Error while parsing the 'sandbox' attribute: 'allow-clipboard-read', 'allow-clipboard-write' are invalid sandbox flags.`
jsfiddle.net/ line 1232, col 0	`Error while parsing the 'sandbox' attribute: 'allow-clipboard-read', 'allow-clipboard-write' are invalid sandbox flags.`
jsfiddle.net/ line 1253, col 0	`Error while parsing the 'sandbox' attribute: 'allow-clipboard-read', 'allow-clipboard-write' are invalid sandbox flags.`
jsfiddle.net/js/_dist-editor.js?a5d18b050a5a2ca908634e556824833385a8472d	`Error while parsing the 'sandbox' attribute: 'allow-clipboard-read', 'allow-clipboard-write' are invalid sandbox flags.`
jsfiddle.net/ line 1944, col 0	`Error: <svg> attribute width: Unexpected end of attribute. Expected length, "".`
jsfiddle.net/ line 1945, col 0	`Error: <svg> attribute width: Unexpected end of attribute. Expected length, "".`
jsfiddle.net/ line 1946, col 0	`Error: <svg> attribute width: Unexpected end of attribute. Expected length, "".`
jsfiddle.net/ line 1947, col 0	`Error: <svg> attribute width: Unexpected end of attribute. Expected length, "".`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
/js/lib/monaco-editor/min/vs/editor/editor.main.js?a5d18b...	jsfiddle.net/js/lib/monaco-editor/min-maps/vs/editor/editor.main.js.map
unpkg.com/external-svg-loader@latest/svg-loader.min.js	unpkg.com/external-svg-loader@latest/svg-loader.min.js.map
/js/lib/monaco-editor/min/vs/loader.js?a5d18b050a5a2ca908...	jsfiddle.net/js/lib/monaco-editor/min-maps/vs/loader.js.map
cdn.jsdelivr.net/npm/tippy.js@6.3.7/+esm	/sm/f01260027d9034517d6dec7fd98884deb7cb37d6dbdb43b154dbd...
cdn.jsdelivr.net/npm/emmet-monaco-es@5.5.0/+esm	/sm/49f6f9d898b1f33fd923c381b669ed9255a7c76e9d59194834ecc...
cdn.jsdelivr.net/npm/@popperjs/core@2.11.8/+esm	/sm/409fef989cd90652f608452ec8df964dde541c6fe8eefcca7783f...
cdn.jsdelivr.net/npm/@popperjs/core@2.10.2/+esm	/sm/e6df2a4e345f19cb7243018f74477a7694a8388e6eecd207317c0...

●Uses HTTPS

●Avoids third-party cookies

●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

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
section#fiddle-info > ul.headerActions > li.sidebarToggle > a `section#fiddle-info > ul.headerActions > li.sidebarToggle > a`
div.panel-v > div.panel-h > div.windowLabelCont > a.panelTidy `div.panel-v > div.panel-h > div.windowLabelCont > a.panelTidy`
div.panel-v > div.panel-h > div.windowLabelCont > a.panelTidy `div.panel-v > div.panel-h > div.windowLabelCont > a.panelTidy`
div.panel-v > div.panel-h > div.windowLabelCont > a.panelTidy `div.panel-v > div.panel-h > div.windowLabelCont > a.panelTidy`

To appear in search results, crawlers need access to your app.

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`