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.

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
Two people repairing electronics together `a.group > div.relative > picture > img.size-full`	assets.cdn.ifixit.com/static/images/home/cta/right/720w.avif	156.9 KiB	108.9 KiB
div.entry-content > div.wp-block-ifixit-banner > div.wp-block-cover > img.show-on-mobile `div.entry-content > div.wp-block-ifixit-banner > div.wp-block-cover > img.show-on-mobile`	/media/2025/11/28045209/FixBot-App_Valkyrie-Banner_Mobile...	82.5 KiB	52.8 KiB
Assortment of quality parts and tools `a.group > div.relative > picture > img.size-full`	assets.cdn.ifixit.com/static/images/home/cta/center/720w.avif	77.1 KiB	52.4 KiB
A person repairing a laptop `a.group > div.relative > picture > img.size-full`	assets.cdn.ifixit.com/static/images/home/cta/left/720w.avif	36.1 KiB	24.3 KiB
Yellow gloved hand turns a faucet handle with a wrench `a.group > article.flex > div.relative > img.h-full`	/media/2026/04/13160738/faucet_wrench_3x2_small-768x512.jpg	51.4 KiB	13.1 KiB
Dewalt Repair `div.homepage-hero-placeholder > div.hero-image > picture > img`	/static/images/home/search-hero-backgrounds/dewalt_driver...	11.8 KiB	6.2 KiB
Medical Device `a.card > div.flex > div.relative > img.absolute`	guide-images.cdn.ifixit.com/igi/yy4PBEHTeUqChV3B.standard	15.2 KiB	4.2 KiB

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

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
assets.cdn.ifixit.com/Assets/scripts/home-page.js.87c6b5c8e5e4cba6f693.css	2.4 KiB
assets.cdn.ifixit.com/Assets/scripts/7397.d29ccdce1e2394c6a74b.css	23.3 KiB	151 ms

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
www.redditstatic.com/ads/pixel.js	60.0 s	19.0 KiB
scripts.clarity.ms/0.8.59-beta/clarity.js	86400.0 s	26.2 KiB
diffuser-cdn.app-us1.com/diffuser/diffuser.js	300.0 s	7.8 KiB
bat.bing.com/p/insights/s/0.8.59	86400.0 s	15.6 KiB
tag.rmp.rakuten.com/127111.ct.js	86400.0 s	14.5 KiB
/rp.gif?ts=1776808561303&id=a2_gka97g83kzyx&event=PageVis...	0.0 ms	666 B

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.

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: 1.7 s

URL	Time Spent
ifixit.com/	930 ms
www.ifixit.com/	765 ms
www.ifixit.com/	0.0 ms

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: 1.7 s 394.6 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-59NVBFN	155.3 KiB	77.8 KiB
www.googletagmanager.com/gtag/js?id=AW-732988910&cx=c&gtm=4e64h1	145.2 KiB	55.2 KiB
www.googletagmanager.com/gtag/js?id=AW-732988613&cx=c&gtm=4e64h1	145.2 KiB	55.1 KiB
www.googletagmanager.com/gtag/js?id=AW-842816056&cx=c&gtm=4e64h1	145.1 KiB	54.7 KiB
www.googletagmanager.com/gtag/js?id=G-5ZXNWJ73GK	180.4 KiB	48.6 KiB
assets.cdn.ifixit.com/Assets/scripts/6404.c168c485ce4f7b0bb0db.js	38.2 KiB	33.3 KiB
assets.cdn.ifixit.com/Assets/scripts/3952.becc5dbb48fc24b9c72a.js	30.7 KiB	24.9 KiB
assets.cdn.ifixit.com/Assets/scripts/4730.581ac91f510c49278d57.js	28.5 KiB	23.8 KiB
assets.cdn.ifixit.com/Assets/scripts/9330.a5b73a593720f1776cc7.js	55.6 KiB	21.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
assets.cdn.ifixit.com/Assets/scripts/9330.a5b73a593720f1776cc7.js	2.0 s	1.9 s	24 ms
www.ifixit.com/	1.9 s	653 ms	10 ms
assets.cdn.ifixit.com/Assets/scripts/home-page.js.4194254d691f07eea677.js	1.1 s	1.0 s	9.6 ms
Unattributable	968 ms	224 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-5ZXNWJ73GK	926 ms	825 ms	85 ms
www.googletagmanager.com/gtag/js?id=AW-842816056&cx=c&gtm=4e64h1	410 ms	314 ms	56 ms
www.googletagmanager.com/gtag/js?id=AW-732988910&cx=c&gtm=4e64h1	389 ms	329 ms	55 ms
assets.cdn.ifixit.com/Assets/scripts/945.94445a3979df39d08782.js	389 ms	115 ms	2.6 ms
www.googletagmanager.com/gtag/js?id=AW-732988613&cx=c&gtm=4e64h1	384 ms	321 ms	60 ms
assets.cdn.ifixit.com/Assets/scripts/error-capture.js.57f7ce4fba7e377f1be3.js	375 ms	313 ms	13 ms
scripts.clarity.ms/0.8.59-beta/clarity.js	210 ms	195 ms	10 ms
www.googletagmanager.com/gtm.js?id=GTM-59NVBFN	197 ms	116 ms	66 ms
bat.bing.com/p/insights/s/0.8.59	62 ms	53 ms	6.1 ms
diffuser-cdn.app-us1.com/diffuser/diffuser.js	51 ms	45 ms	5.3 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	7.0 s
Other	1.2 s
Style & Layout	1.2 s
Script Parsing & Compilation	682 ms
Garbage Collection	131 ms
Parse HTML & CSS	128 ms
Rendering	107 ms

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 reason	Failure 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

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 48.8 KiB

URL	Transfer Size	Est Savings
valkyrie.cdn.ifixit.com/assets/css/app.b0a869.css	30.7 KiB	29.7 KiB
assets.cdn.ifixit.com/Assets/Guide/ifixit/guide-all-oZ2Sj6FaW8SjfkKT9PosZg.css	19.5 KiB	19.1 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
Get it on Google Play `ul.css-1cq2g21 > div.flex > a.group > img.transition-all`	/static/images/app-landing/GetItOnGooglePlay_Badge_Web_co...

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

●Font display

●Forced reflow

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,519 KiB

●User Timing marks and measures 35 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 220 ms

●Server Backend Latencies 320 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Download the app `div.css-1oxagfj > div.css-kzvh2p > div.css-k9csqw > ul.css-1cq2g21`

These are opportunities to improve the usage of ARIA in your application which 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
Apr 16, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 6, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 14, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 13, 2026 `a.group > article.flex > div.flex > p.m-0`
Apr 6, 2026 `a.group > article.flex > div.flex > p.m-0`
Let me read it first! `section.container-content-home > div.grid > div.newsletter-sub > a.mt-3`

These are opportunities to improve the legibility of your content.

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
div.wp > article.post-114682 > div.entry-content > a.block-link `div.wp > article.post-114682 > div.entry-content > a.block-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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

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

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Skip links are focusable.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

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

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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

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

●Use a strong HSTS policy

●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

○Mitigate clickjacking with XFO or CSP

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
div.sc-hXGFlK > div.sc-gXEjlL > div.sc-eddAHl > a.sc-bsshXr `div.sc-hXGFlK > div.sc-gXEjlL > div.sc-eddAHl > a.sc-bsshXr`
DEDeutsch `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
ESEspañol `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
ITItaliano `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
PTPortuguês `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
TRTürkçe `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
JP日本語 `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
ENEnglish `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
FRFrançais `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
NLNederlands `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
RUPусский `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
ZH中文 `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
KO한국어 `div.sc-efgocT > div.sc-dDvxFM > div.sc-jqVXSH > a.sc-gTrWKq`
div.sc-hXGFlK > div.sc-gXEjlL > div.sc-eddAHl > a.sc-bsshXr `div.sc-hXGFlK > div.sc-gXEjlL > div.sc-eddAHl > a.sc-bsshXr`
Cookie Consent `div.css-k9csqw > ul.css-1cq2g21 > li.css-1chydhc > a.css-1n2agjd`

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`