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

90

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
loremipsum.io/_next/static/chunks/e9014f26-2a3e0b18e14369e5.js0.0 ms399.4 KiB
loremipsum.io/_next/static/chunks/4bd1b696-c023c6e3521b1417.js0.0 ms169.5 KiB
loremipsum.io/_next/static/chunks/255-102f2e5b2e3dc2ef.js0.0 ms169.3 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...1800.0 s194.2 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...1800.0 s192.7 KiB
loremipsum.io/_next/static/chunks/963-21efee6d45fc58c8.js0.0 ms133.8 KiB
loremipsum.io/_next/static/chunks/151-0a87f2721d0c45ab.js0.0 ms104.6 KiB
cdn.privacy-mgmt.com/Notice.97af9.js3600.0 s92.9 KiB
loremipsum.io/_next/static/media/f7a9b128ae841a36-s.p.woff20.0 ms72.9 KiB
loremipsum.io/_next/static/media/acc997c86979663b-s.p.woff20.0 ms70.1 KiB
loremipsum.io/_next/static/media/cb8d34571a43f897-s.p.woff20.0 ms69.8 KiB
loremipsum.io/_next/static/media/5d39360912ab897b-s.p.woff20.0 ms67.2 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js3600.0 s41.3 KiB
a.pub.network/loremipsum-io/pubfig.min.js1800.0 s33.5 KiB
loremipsum.io/_next/static/css/c2e78001d34219ec.css0.0 ms28.8 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...1800.0 s31.7 KiB
loremipsum.io/_next/static/chunks/759-1a5a3daeac4ca09d.js0.0 ms6.9 KiB
cdn.privacy-mgmt.com/Notice.1c267.css3600.0 s6.9 KiB
loremipsum.io/_next/static/chunks/webpack-88bbb02eab35f835.js0.0 ms3.7 KiB
cdn.privacy-mgmt.com/polyfills.01516.js3600.0 s2.4 KiB
loremipsum.io/_next/static/chunks/app/layout-7c82521a011c0410.js0.0 ms1.2 KiB
loremipsum.io/_next/static/chunks/app/page-cd17934ce6ba7359.js0.0 ms1021 B
loremipsum.io/_next/static/chunks/app/name-generator/page-dad0e5f20a0eacf6.js0.0 ms997 B
loremipsum.io/_next/static/chunks/app/plugins/page-dad0e5f20a0eacf6.js0.0 ms997 B
/_next/static/chunks/app/ultimate-list-of-lorem-ipsum-gen...0.0 ms997 B
loremipsum.io/_next/static/chunks/app/font-generator/page-dad0e5f20a0eacf6.js0.0 ms996 B
/_next/static/chunks/app/21-of-the-best-placeholder-image...0.0 ms996 B
loremipsum.io/_next/static/chunks/main-app-0e767b34c4348844.js0.0 ms906 B

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

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.

URLTransfer SizeDuration
loremipsum.io/_next/static/css/c2e78001d34219ec.css28.8 KiB55 ms

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.

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 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: 220 ms 742.7 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/gpt/m202609240101/pubads_impl.js?cb=12...212.4 KiB161.3 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...192.2 KiB156.5 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...193.7 KiB155.0 KiB
www.googletagmanager.com/gtag/js?id=G-KXPKVKP7EK163.2 KiB70.8 KiB
loremipsum.io/_next/static/chunks/255-102f2e5b2e3dc2ef.js168.7 KiB67.5 KiB
loremipsum.io/_next/static/chunks/4bd1b696-c023c6e3521b1417.js169.0 KiB53.8 KiB
loremipsum.io/_next/static/chunks/963-21efee6d45fc58c8.js133.3 KiB53.5 KiB
loremipsum.io/_next/static/chunks/151-0a87f2721d0c45ab.js104.1 KiB24.2 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.

URLTransfer Size
loremipsum.io/_next/static/chunks/e9014f26-2a3e0b18e14369e5.js399.4 KiB
/pagead/managed/js/gpt/m202609240101/pubads_impl.js?cb=12...212.4 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...194.2 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...192.7 KiB
loremipsum.io/_next/static/chunks/4bd1b696-c023c6e3521b1417.js169.5 KiB
loremipsum.io/_next/static/chunks/255-102f2e5b2e3dc2ef.js169.3 KiB
www.googletagmanager.com/gtag/js?id=G-KXPKVKP7EK163.5 KiB
loremipsum.io/145.2 KiB
loremipsum.io/_next/static/chunks/963-21efee6d45fc58c8.js133.8 KiB
loremipsum.io/_next/static/chunks/151-0a87f2721d0c45ab.js104.6 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
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 60 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 6 user timings
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.7 s
●Avoid long main-thread tasks 3 long tasks found
●Image elements have explicit `width` and `height`
●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 20 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
86

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
© 2015–2026 body.__variable_59b718 > footer.grid > div.flex > span.md:text-base
Sitemap body.__variable_59b718 > footer.grid > div.flex > span.md:text-base
More tools body.__variable_59b718 > footer.grid > div.hidden > span.md:text-base
Language body.__variable_59b718 > footer.grid > div.relative > span.hidden

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
Discover More section.grid > div.sm:hidden > div.hidden > h4.text-md

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.w-full > div.flex > form.flex > input.sm:w-16 div.w-full > div.flex > form.flex > input.sm:w-16

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Paragraphs Sentences Words div.w-full > div.flex > form.flex > select.sm:w-36

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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[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.
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●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
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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.
○No element has a `[tabindex]` value greater than 0
○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.
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
loremipsum.io/_vercel/insights/script.js
Failed to load resource: the server responded with a status of 404 ()
●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 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