Lighthouse Mobile

· 0 checks — Mobile 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
loremipsum.io/_next/static/chunks/e9014f26-2a3e0b18e14369e5.js	0.0 ms	399.4 KiB
loremipsum.io/_next/static/chunks/4bd1b696-c023c6e3521b1417.js	0.0 ms	169.5 KiB
loremipsum.io/_next/static/chunks/255-102f2e5b2e3dc2ef.js	0.0 ms	169.3 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	1800.0 s	194.6 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	1800.0 s	192.1 KiB
loremipsum.io/_next/static/chunks/963-21efee6d45fc58c8.js	0.0 ms	133.8 KiB
loremipsum.io/_next/static/chunks/151-0a87f2721d0c45ab.js	0.0 ms	104.6 KiB
cdn.privacy-mgmt.com/Notice.97af9.js	3600.0 s	92.9 KiB
loremipsum.io/_next/static/media/f7a9b128ae841a36-s.p.woff2	0.0 ms	72.9 KiB
loremipsum.io/_next/static/media/acc997c86979663b-s.p.woff2	0.0 ms	70.1 KiB
loremipsum.io/_next/static/media/cb8d34571a43f897-s.p.woff2	0.0 ms	69.8 KiB
loremipsum.io/_next/static/media/5d39360912ab897b-s.p.woff2	0.0 ms	67.2 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600.0 s	41.3 KiB
a.pub.network/loremipsum-io/pubfig.min.js	1800.0 s	33.5 KiB
loremipsum.io/_next/static/css/c2e78001d34219ec.css	0.0 ms	28.8 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	1800.0 s	31.7 KiB
loremipsum.io/_next/static/chunks/759-1a5a3daeac4ca09d.js	0.0 ms	6.9 KiB
cdn.privacy-mgmt.com/Notice.1c267.css	3600.0 s	6.9 KiB
loremipsum.io/_next/static/chunks/webpack-88bbb02eab35f835.js	0.0 ms	3.7 KiB
cdn.privacy-mgmt.com/polyfills.01516.js	3600.0 s	2.4 KiB
loremipsum.io/_next/static/chunks/app/layout-7c82521a011c0410.js	0.0 ms	1.2 KiB
loremipsum.io/_next/static/chunks/app/page-cd17934ce6ba7359.js	0.0 ms	1022 B
loremipsum.io/_next/static/chunks/app/name-generator/page-dad0e5f20a0eacf6.js	0.0 ms	999 B
loremipsum.io/_next/static/chunks/app/font-generator/page-dad0e5f20a0eacf6.js	0.0 ms	997 B
/_next/static/chunks/app/ultimate-list-of-lorem-ipsum-gen...	0.0 ms	997 B
/_next/static/chunks/app/21-of-the-best-placeholder-image...	0.0 ms	996 B
loremipsum.io/_next/static/chunks/app/plugins/page-dad0e5f20a0eacf6.js	0.0 ms	995 B
loremipsum.io/_next/static/chunks/main-app-0e767b34c4348844.js	0.0 ms	908 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.1482705046164556] map[node:map[boundingRect:map[bottom:1913 height:1142 left:16 right:396 top:771 width:380] lhId:page-1-SECTION nodeLabel:What is Lorem Ipsum? From its medieval origins to the digital era, learn every… path:2,HTML,1,BODY,2,MAIN,2,SECTION selector:body.__variable_59b718 > main.xl:max-w-[1296px] > section.grid snippet:<section class="grid grid-cols-12 grid-auto-rows gap-4 sm:gap-8 lg:gap-4 xl:gap-8 mt-16 sm…"> type:node] score:0.1482705046164556]]

items: [map[node:map[type:text value:Total] score:0.01944106925880923] map[node:map[boundingRect:map[bottom:14435 height:14435 left:0 right:412 top:0 width:412] lhId:page-3-BODY nodeLabel:body.__variable_59b718 path:2,HTML,1,BODY selector:body.__variable_59b718 snippet:<body class="__variable_59b718 __variable_c35935 bg-neutral-900 font-sans"> type:node] score:0.01944106925880923]]

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.

URL	Transfer Size	Duration
loremipsum.io/_next/static/css/c2e78001d34219ec.css	28.8 KiB	333 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.

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.

	URL	Resource Size	Est Savings
Typesetter selecting type `section.grid > div.lg:col-span-9 > figure.relative > img.col-span-2`	/7mySwtfCu3UO8RUPO7Vmad/b9aff766c6e30627ac3c9633be9b3cd4/...	68.0 KiB	36.8 KiB
Cicero `section.grid > div.lg:col-span-9 > figure.relative > img.col-span-2`	/5vCfGucT8waG1ErycNnTOo/c3277113e4a0bbe6e522813001653cf6/...	49.2 KiB	26.6 KiB
Lorem Ipsum Magazine Layout `section.grid > div.lg:col-span-9 > figure.relative > img.col-span-2`	/CZhWYZJ3UEpUrYOwBqZZ3/846c9c7fdc261fe79205833c6787f3fc/l...	34.5 KiB	18.6 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
What is Lorem Ipsum? From its medieval origins to the digital era, learn every… `body.__variable_59b718 > main.xl:max-w-[1296px] > section.grid`	0.148
body.__variable_59b718 `body.__variable_59b718`	0.019

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.

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: 1.5 s 744.1 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202609220101/pubads_impl.js	212.2 KiB	163.0 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	191.6 KiB	156.0 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	194.1 KiB	155.3 KiB
www.googletagmanager.com/gtag/js?id=G-KXPKVKP7EK	163.3 KiB	70.7 KiB
loremipsum.io/_next/static/chunks/255-102f2e5b2e3dc2ef.js	168.7 KiB	67.5 KiB
loremipsum.io/_next/static/chunks/4bd1b696-c023c6e3521b1417.js	169.0 KiB	53.8 KiB
loremipsum.io/_next/static/chunks/963-21efee6d45fc58c8.js	133.3 KiB	53.5 KiB
loremipsum.io/_next/static/chunks/151-0a87f2721d0c45ab.js	104.1 KiB	24.2 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	382 ms	71 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-KXPKVKP7EK	276 ms	213 ms	59 ms
loremipsum.io/_next/static/chunks/255-102f2e5b2e3dc2ef.js	255 ms	208 ms	27 ms
loremipsum.io/	253 ms	11 ms	13 ms
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	234 ms	159 ms	72 ms
/pagead/managed/js/gpt/m202609220101/pubads_impl.js	213 ms	146 ms	64 ms
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	205 ms	161 ms	42 ms
loremipsum.io/_next/static/chunks/4bd1b696-c023c6e3521b1417.js	191 ms	171 ms	18 ms
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	170 ms	142 ms	9.4 ms
loremipsum.io/_next/static/chunks/963-21efee6d45fc58c8.js	129 ms	117 ms	12 ms
cdn.privacy-mgmt.com/unified/4.40.3/usnat.17801fe5e33dd6698495.bundle.js	117 ms	87 ms	29 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	76 ms	65 ms	11 ms
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	67 ms	59 ms	6.0 ms
a.pub.network/loremipsum-io/pubfig.min.js	63 ms	52 ms	8.9 ms
loremipsum.io/_next/static/chunks/webpack-88bbb02eab35f835.js	56 ms	33 ms	0.7 ms

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.

Category	Time Spent
Script Evaluation	1.7 s
Script Parsing & Compilation	433 ms
Other	402 ms
Style & Layout	129 ms
Rendering	43 ms
Parse HTML & CSS	33 ms
Garbage Collection	28 ms

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
loremipsum.io/_next/static/chunks/e9014f26-2a3e0b18e14369e5.js	399.4 KiB
/pagead/managed/js/gpt/m202609220101/pubads_impl.js	212.2 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	194.6 KiB
/loremipsum-io/ab_test/history/dec49155-6b61-493f-9faa-98...	192.1 KiB
loremipsum.io/_next/static/chunks/4bd1b696-c023c6e3521b1417.js	169.5 KiB
loremipsum.io/_next/static/chunks/255-102f2e5b2e3dc2ef.js	169.3 KiB
www.googletagmanager.com/gtag/js?id=G-KXPKVKP7EK	163.6 KiB
loremipsum.io/	145.2 KiB
loremipsum.io/_next/static/chunks/963-21efee6d45fc58c8.js	133.8 KiB
loremipsum.io/_next/static/chunks/151-0a87f2721d0c45ab.js	104.6 KiB

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

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 6 user timings

●Avoid long main-thread tasks 12 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

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

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
div.md:col-span-8 > div.w-full > div.flex > button.flex `div.md:col-span-8 > div.w-full > div.flex > button.flex`

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.

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`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Font Generator `div.flex > ul.sm:col-span-3 > li > a.md:text-base`
Name Generator `div.flex > ul.sm:col-span-3 > li > a.md:text-base`
Placeholders `div.flex > ul.sm:col-span-3 > li > a.md:text-base`
Generators `div.flex > ul.sm:col-span-3 > li > a.md:text-base`

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

●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

●Heading elements appear in a sequentially-descending order

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

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.

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