Skip to content
https://swagger.io

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.

89

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.

RequestCache TTLTransfer Size
static1.smartbear.co/smartbear/react/search/search.js?t=0.18335281211252140.0 ms164.8 KiB
cdn-4.convertexperiments.com/js/1004798-1004841.js300.0 s101.2 KiB
static1.smartbear.co/swagger/media/images/tools/api-spec-ring.png0.0 ms84.4 KiB
static1.smartbear.co/swagger/media/images/tools/open-source-ring.png0.0 ms83.0 KiB
static1.smartbear.co/swagger/media/images/tools/swaggerhub-ring.png0.0 ms80.4 KiB
static1.smartbear.co/swagger/media/images/logos/national-geographic-logo-clr.png0.0 ms49.6 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
cdn.cookiehub.eu/c2/28d45b26.js86400.0 s37.2 KiB
static1.smartbear.co/swagger/media/images/logos/microsoft-logo-clr.png0.0 ms11.4 KiB
static1.smartbear.co/swagger/media/assets/images/swagger_logo.svg0.0 ms7.3 KiB
/PVooPtpJE-25QaNkbEuXvw/0117d73b-b327-45ff-f333-0af511c52...172800.0 s20.6 KiB
static1.smartbear.co/swagger/media/images/logos/oas_original-01.svg0.0 ms5.7 KiB
cookiehub.net/c2/css/28d45b26.css86400.0 s9.5 KiB
static1.smartbear.co/swagger/media/images/backgrounds/grn-abstract-code-left.png0.0 ms3.2 KiB
/swagger/media/images/backgrounds/grn-abstract-code-right...0.0 ms2.8 KiB
static1.smartbear.co/swagger/media/images/logos/zuora-logo-alt-clr.svg0.0 ms2.3 KiB
static1.smartbear.co/swagger/media/images/icon/sw-grn-ta-icon.svg0.0 ms2.0 KiB
static1.smartbear.co/swagger/media/images/sb_horizontal_clr.svg0.0 ms1.9 KiB
static1.smartbear.co/swagger/media/images/icon/sw-grn-doc-icon.svg0.0 ms1.1 KiB
static1.smartbear.co/swagger/media/images/icon/sw-grn-code-icon.svg0.0 ms1.1 KiB
static1.smartbear.co/swagger/media/images/icon/sw-grn-design-icon.svg0.0 ms1.0 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:4.996 source:map[column:51393 line:1 type:source-location url:https://code.jquery.com/jquery-3.3.1.min.js urlProvider:network]] map[reflowTime:38.602 source:map[column:50673 line:1 type:source-location url:https://code.jquery.com/jquery-3.3.1.min.js urlProvider:network]] map[reflowTime:0.204 source:map[column:50731 line:1 type:source-location url:https://code.jquery.com/jquery-3.3.1.min.js urlProvider:network]] map[reflowTime:0.122 source:map[column:50793 line:1 type:source-location url:https://code.jquery.com/jquery-3.3.1.min.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
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute
static1.smartbear.co/swagger/media/images/tools/api-spec-ring.png83.9 KiB69.3 KiB
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute
static1.smartbear.co/swagger/media/images/tools/open-source-ring.png82.5 KiB68.2 KiB
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute
static1.smartbear.co/swagger/media/images/tools/swaggerhub-ring.png80.0 KiB66.1 KiB
National Geographic logo div.row > div.col-md-5 > div._flex > img.img-fluid
static1.smartbear.co/swagger/media/images/logos/national-geographic-logo-clr.png49.2 KiB49.1 KiB
Microsoft logo div.row > div.col-md-5 > div._flex > img.img-fluid
static1.smartbear.co/swagger/media/images/logos/microsoft-logo-clr.png11.0 KiB10.7 KiB

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-5-IMG
nodeLabel: Bleeding Image
path: 1,HTML,1,BODY,4,FORM,10,MAIN,1,SECTION,0,DIV,0,DIV,1,DIV,0,IMG
selector: div.container > div.row > div.col-md-5 > img.rounded-lg
snippet: <img src="https://imagedelivery.net/PVooPtpJE-25QaNkbEuXvw/0117d73b-b327-45ff-f333-0…" alt="Bleeding Image" style="max-height:525px;width:auto;" class="rounded-lg border">

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
value: No additional origins are good candidates for preconnecting

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

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: 200 ms 236.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.

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.3 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
National Geographic logo div.row > div.col-md-5 > div._flex > img.img-fluid
static1.smartbear.co/swagger/media/images/logos/national-geographic-logo-clr.png
Bleeding Image div.container > div.row > div.col-md-5 > img.rounded-lg
/PVooPtpJE-25QaNkbEuXvw/0117d73b-b327-45ff-f333-0af511c52...
Microsoft logo div.row > div.col-md-5 > div._flex > img.img-fluid
static1.smartbear.co/swagger/media/images/logos/microsoft-logo-clr.png
OpenAPI Initiative logo section._container > div.lg:_flex > div._basis-1/6 > img._w-[150px]
static1.smartbear.co/swagger/media/images/logos/oas_original-01.svg
SmartBear Logo main._antialiased > section._overflow-hidden > div._container > img._pb-4
static1.smartbear.co/swagger/media/images/sb_horizontal_clr.svg
Zuora logo div.row > div.col-md-5 > div._flex > img.img-fluid
static1.smartbear.co/swagger/media/images/logos/zuora-logo-alt-clr.svg

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify JavaScript
●User Timing marks and measures 14 user timings
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.8 s
●Avoid long main-thread tasks 3 long tasks found
●Network Requests
●Network Round Trip Times 60 ms
●Server Backend Latencies 100 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 220 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○Avoid non-composited animations
79

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
ALLOW ALL COOKIES div.ch2-container > div#ch2-dialog > div.ch2-dialog-actions > button.ch2-btn
Explore the API Specifications div.panel > div._p-[30px] > p._mt-[15px] > a._font-semibold
Specifications div._p-[30px] > p._mt-[15px] > a._font-semibold > span.text-nowrap
See how we do it div.lg:_flex > div._basis-4/6 > p._text-clr-neutral-14 > a._font-bold

These are opportunities to improve the legibility of your content.

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-1hwfws3 > div.css-1g6gooi > div > input#react-select-2-input div.css-1hwfws3 > div.css-1g6gooi > div > input#react-select-2-input

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
  nav.main > ul.nav > li.nav-item > a.nav-link

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.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○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
○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.
○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.
100

Best Practices

●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 browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
82

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.

Link destinationLink Text
smartbear.com/privacy/Learn more
swagger.io/tools/Learn More

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute
section._container > div._flex > div._hidden > img.position-absolute section._container > div._flex > div._hidden > img.position-absolute

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
●Document has a valid `hreflang`
○robots.txt is valid
○Document has a valid `rel=canonical`

Send Feedback