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.

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.

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

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

URL	Time Spent
instagram.com/	823 ms
www.instagram.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

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 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: 510 ms 183.2 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/y4/l/0,cross/dVzjbm6f69NWCNCFWkqK38PtT8xyvjG...	176.8 KiB	172.5 KiB
:root, .__ig-light-mode:root, .__ig-light-mode {--fds-black:#000000;--fds-black-alpha-05:rgba(0, 0,…	16.1 KiB	10.7 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.

Estimated savings: 7.9 s 1.5 MiB

URL	Transfer Size	Est Savings
/rsrc.php/v4iRwq4/yV/l/en_US/ODdrm1k2rE0YVIET9B4DPJ7FaOWA...	878.7 KiB	595.3 KiB
/rsrc.php/v4igBN4/yh/l/en_US/tXQjfua0sy18v_r9dr3X36b7-ua_...	211.1 KiB	178.3 KiB
/rsrc.php/v4iDWR4/y3/l/en_US/MqZbzkQuezRa364Frzae8yfx_jVp...	164.6 KiB	128.8 KiB
static.cdninstagram.com/rsrc.php/v4i1kT4/yQ/l/en_US/_oQSZVVeyji.js	126.0 KiB	111.5 KiB
static.cdninstagram.com/rsrc.php/v4ix-z4/y9/l/en_US/jjsRJE-Y85l.js	186.8 KiB	80.8 KiB
static.cdninstagram.com/rsrc.php/v4iRyB4/ye/l/en_US/WHOopEPm5Ed.js	87.1 KiB	80.0 KiB
static.cdninstagram.com/rsrc.php/v4i4884/y_/l/en_US/dnok0zgcBWI.js	62.0 KiB	58.0 KiB
static.cdninstagram.com/rsrc.php/v4iVv04/y9/l/en_US/HPVHUNAlhEX.js	55.0 KiB	51.4 KiB
static.cdninstagram.com/rsrc.php/v4/yA/r/MuNp3ftYOj5.js	56.0 KiB	51.3 KiB
/rsrc.php/v4iWPu4/yA/l/en_US/HUrPRMPbjNhiN4bKk4bl3W3EJHxY...	60.5 KiB	46.5 KiB
static.cdninstagram.com/rsrc.php/v4/yr/r/UcCSHUeio1A.js	43.5 KiB	42.6 KiB
static.cdninstagram.com/rsrc.php/v4iQvT4/yE/l/en_US/M-LBWHhsGRV.js	43.4 KiB	39.5 KiB
static.cdninstagram.com/rsrc.php/v4/yD/r/pwR47Z3NJfs.js	75.4 KiB	31.3 KiB
static.cdninstagram.com/rsrc.php/v4/yZ/r/QKYCsWGn8pv.js	24.5 KiB	23.9 KiB
static.cdninstagram.com/rsrc.php/v4i7M54/ye/l/en_US/biTxlS5uJ7X.js	21.8 KiB	20.7 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
static.cdninstagram.com/rsrc.php/v4/yD/r/pwR47Z3NJfs.js	1.8 s	1.5 s	24 ms
/rsrc.php/v4iRwq4/yV/l/en_US/ODdrm1k2rE0YVIET9B4DPJ7FaOWA...	424 ms	61 ms	339 ms
www.instagram.com/	354 ms	30 ms	0.5 ms
static.cdninstagram.com/rsrc.php/v4ix-z4/y9/l/en_US/jjsRJE-Y85l.js	348 ms	20 ms	73 ms
Unattributable	291 ms	21 ms	0.0 ms
/rsrc.php/v4igBN4/yh/l/en_US/tXQjfua0sy18v_r9dr3X36b7-ua_...	145 ms	10 ms	126 ms
	82 ms	63 ms	16 ms
static.cdninstagram.com/rsrc.php/v4i1kT4/yQ/l/en_US/_oQSZVVeyji.js	69 ms	8.1 ms	55 ms
/rsrc.php/v4iDWR4/y3/l/en_US/MqZbzkQuezRa364Frzae8yfx_jVp...	61 ms	5.8 ms	55 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.8 s
Script Parsing & Compilation	882 ms
Other	713 ms
Style & Layout	191 ms
Parse HTML & CSS	132 ms
Garbage Collection	92 ms
Rendering	17 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

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
from Meta `main.xvbhtw8 > div.html-div > div.html-div > img`	static.cdninstagram.com/rsrc.php/yb/r/SxCWlJznXoy.svg

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 63 user timings

●Avoid long main-thread tasks 16 long tasks found

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta#viewport `head > meta#viewport`

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

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links have a discernible name

●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

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○Form elements have associated labels

○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

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

○`<object>` elements have alternate text

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

○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.	static.cdninstagram.com/rsrc.php/v4/yD/r/pwR47Z3NJfs.js line 246, col 362

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
static.cdninstagram.com/rsrc.php/v4ix-z4/y9/l/en_US/jjsRJE-Y85l.js
static.cdninstagram.com/rsrc.php/v4iRyB4/ye/l/en_US/WHOopEPm5Ed.js
/rsrc.php/v4iRwq4/yV/l/en_US/ODdrm1k2rE0YVIET9B4DPJ7FaOWA...
/rsrc.php/v4igBN4/yh/l/en_US/tXQjfua0sy18v_r9dr3X36b7-ua_...
/rsrc.php/v4iDWR4/y3/l/en_US/MqZbzkQuezRa364Frzae8yfx_jVp...
static.cdninstagram.com/rsrc.php/v4i1kT4/yQ/l/en_US/_oQSZVVeyji.js

●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

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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`