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
bordeaux.futurecdn.net/bordeaux.js	0.0 ms	179.0 KiB
t.contentsquare.net/uxa/e4c8fee5bc338.js	900.0 s	123.3 KiB
cdn.privacy-mgmt.com/Notice.8f529.js	3600.0 s	91.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	1800.0 s	64.9 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
freyr.futurecdn.net/freyr.js	0.0 ms	22.3 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	3600.0 s	24.4 KiB
champagne.futurecdn.net/champagne.js	0.0 ms	16.2 KiB
cdn.debugbear.com/HHVQPB2aFABK.js?v=1	14400.0 s	14.3 KiB
cdn.privacy-mgmt.com/Notice.30929.css	3600.0 s	6.7 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=2262	3600.0 s	4.3 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js	86400.0 s	7.8 KiB
uk-script.dotmetrics.net/Scripts/ncs-script.js?v=362	0.0 ms	2.9 KiB
cdn.privacy-mgmt.com/polyfills.01516.js	3600.0 s	2.3 KiB
cdn.mos.cms.futurecdn.net/flexiimages/bpdttrhkb11736938217.svg	0.0 ms	1.6 KiB
/hit.gif?id=5202&url=https%3A%2F%2Fwww.imore.com%2F&dom=w...	86400.0 s	1.2 KiB

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.687274] map[score:0.687274]]

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.

URL	Est Savings
vanilla.futurecdn.net/imore/1611212/media/shared/fonts/OpenSans-700-Bold.woff2	120 ms

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:48.04 source:map[type:text value:[unattributed]]] map[reflowTime:11.576 source:map[column:1579 line:0 type:source-location url:https://www.imore.com/vite/assets/Nav/Nav.ts-agSe9QHG.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.

	URL	Resource Size	Est Savings
iPad Pro 12.9-inch in iMore freelancer's office `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/hC67Z5uAEUGDRAyEcpyi8a-800-80.jpg.webp	53.9 KiB	50.5 KiB
iPad (2022) with Notes app open to a cocktail recipe sitting next to a cocktail… `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/G6DP7VDisCDooN6hgN8jaU-800-80.jpg.webp	36.6 KiB	34.3 KiB
iMore Logo `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/8kts3gvMKEK9MsJtLxS83Q-768-80.jpg.webp	28.8 KiB	20.5 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-2-IMG

nodeLabel: iMore Logo

path: 1,HTML,1,BODY,11,DIV,4,DIV,0,DIV,2,UL,0,LI,0,A,0,DIV,0,DIV,0,PICTURE,1,IMG

selector: div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img

snippet: <img src="https://cdn.mos.cms.futurecdn.net/8kts3gvMKEK9MsJtLxS83Q-768-80.jpg.webp" alt="iMore Logo" class="v2-listing-image-img block-image-ads manual-image-sizes" srcset="https://cdn.mos.cms.futurecdn.net/8kts3gvMKEK9MsJtLxS83Q-1920-80.jpg 1920w…" sizes="412px" data-original-mos="https://cdn.mos.cms.futurecdn.net/8kts3gvMKEK9MsJtLxS83Q.jpg" data-pin-media="https://cdn.mos.cms.futurecdn.net/8kts3gvMKEK9MsJtLxS83Q.jpg" data-pin-nopin="true">

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

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

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.

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: 751 ms

URL	Time Spent
imore.com/	751 ms
www.imore.com/	0.0 ms

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.

Layout shift score
0.687

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: 3.0 s 559.3 KiB

URL	Transfer Size	Est Savings
bordeaux.futurecdn.net/bordeaux.js	178.6 KiB	101.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64k1	165.9 KiB	83.3 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/responsive.js	140.4 KiB	80.7 KiB
www.googletagmanager.com/gtag/js?id=G-PG4257SNE2&cx=c&gtm=4e64k1	143.6 KiB	60.3 KiB
t.contentsquare.net/uxa/e4c8fee5bc338.js	122.7 KiB	51.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL	143.0 KiB	47.4 KiB
vanilla.futurecdn.net/imore/1611212/media/shared/js/main.DcB9tpsv.bundle.js	104.0 KiB	44.3 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	64.6 KiB	23.9 KiB
www.imore.com/vite/assets/vendor-DH-HcC7C.js	40.4 KiB	22.7 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/hawklinks.js	38.4 KiB	22.2 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	23.9 KiB	22.1 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	1.6 s	619 ms	0.0 ms
t.contentsquare.net/uxa/e4c8fee5bc338.js	1.4 s	1.2 s	34 ms
www.imore.com/	553 ms	124 ms	25 ms
cdn.privacy-mgmt.com/unified/4.40.1/usnat-uspapi.090eccada574d39af6f8.bundle.js	478 ms	405 ms	30 ms
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64k1	369 ms	331 ms	35 ms
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL	345 ms	305 ms	35 ms
bordeaux.futurecdn.net/bordeaux.js	226 ms	166 ms	50 ms
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/responsive.js	206 ms	161 ms	43 ms
vanilla.futurecdn.net/imore/1611212/media/shared/js/main.DcB9tpsv.bundle.js	194 ms	160 ms	32 ms
www.googletagmanager.com/gtag/js?id=G-PG4257SNE2&cx=c&gtm=4e64k1	180 ms	145 ms	34 ms
www.imore.com/vite/assets/vendor-DH-HcC7C.js	166 ms	162 ms	0.6 ms
sb.scorecardresearch.com/cs/10055482/beacon.js	126 ms	85 ms	2.2 ms
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	122 ms	100 ms	11 ms
freyr.futurecdn.net/freyr.js	93 ms	78 ms	6.7 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	75 ms	64 ms	0.9 ms
slice.vanilla.futurecdn.net/13-4-20/js/externals.js	75 ms	62 ms	12 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	4.4 s
Other	1.1 s
Script Parsing & Compilation	395 ms
Style & Layout	355 ms
Garbage Collection	232 ms
Parse HTML & CSS	146 ms
Rendering	15 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
The page has an unload handler in the main frame.	Actionable
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 19.2 KiB

URL	Transfer Size	Est Savings
@layer hawk { .hawk-affiliate-link-container{height:inherit;line-height:1.2} …	19.2 KiB	19.2 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
flag of US `div.relative > div.flex > button.h-fit > img.w-5`	vanilla.futurecdn.net/imore/media/shared/img/flags/nosize/US.svg
iPad (2022) with Notes app open to a cocktail recipe sitting next to a cocktail… `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/G6DP7VDisCDooN6hgN8jaU-800-80.jpg.webp
iPad Pro 12.9-inch in iMore freelancer's office `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/hC67Z5uAEUGDRAyEcpyi8a-800-80.jpg.webp
iPhone 15 Pro review back handheld angled camera `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/XTQbCDZqYPNMDZUmZc9EVQ-800-80.jpg.webp
A half and half image of a rose gold aluminum watch and a stainless steel model `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/a7zdThWA4BkxZgwxxk7MLa-800-80.jpg.webp
Apple Watch SE on a wrist, the person is wearing a blue shirt `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/ujmXwTBUsTWXbTiDeaPyYF-800-80.jpg.webp
How to reset your Apple ID password `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/jZnypb9YhQtmxyc7muDcqV-800-80.jpg.webp
Logitech Circle View camera on a wooden ledge `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/X53Sdau9wFZ4YdBbLn6suk-800-80.jpg.webp
Eve HomeKit Secure Video camera on a bookshelf `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/36WJ6ZUGSMWFKBEb94J8Ef-800-80.jpg.webp
Level Touch Plus smart lock in use with an Apple Watch `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/yWnHvDpaxShPbTyerEQKNQ-800-80.jpg.webp
iMore `div#publisherDetails > a.relative > picture.block > img.max-w-32`	cdn.mos.cms.futurecdn.net/flexiimages/bpdttrhkb11736938217.svg

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

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 29 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 930 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

100

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.

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●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

●Background and foreground colors have a sufficient contrast ratio

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

○`[accesskey]` values are unique

○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 buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○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

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
Unload event listeners are deprecated and will be removed.	bordeaux.futurecdn.net/bordeaux.js line 31, col 6976

●Uses HTTPS

●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

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`