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
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	73.1 KiB
cmp.inmobi.com/tcfv2/61/cmp2.js?referer=www.mic.com	172800.0 s	116.8 KiB
cdn.id5-sync.com/api/1.0/esp.js	3600.0 s	34.8 KiB
d15kdpgjg3unno.cloudfront.net/oPS.js	84600.0 s	60.5 KiB
s0.2mdn.net/879366/express_html_inpage_rendering_lib_200_287.js	86400.0 s	40.9 KiB
link.rubiconproject.com/magnite/17652.js	0.0 ms	15.2 KiB
ep2.adtrafficquality.google/sodar/VFc2VJAc.js	3000.0 s	14.0 KiB
script-api.ccgateway.net/script/bundle?id=www.mic.com&parentId=67c7fcd8b0	1200.0 s	4.7 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js	86400.0 s	7.8 KiB
cmp.inmobi.com/choice/xPmcrFNGfHkBg/www.mic.com/choice.js?tag_version=V3	900.0 s	3.2 KiB
rules.quantcount.com/rules-p-xPmcrFNGfHkBg.js	3600.0 s	3.0 KiB
pagead2.googlesyndication.com/pagead/js/r20260421/r20110914/abg_lite.js	1209600.0 s	10.5 KiB
/pagead/js/r20260421/r20110914/client/qs_click_protection...	1209600.0 s	8.6 KiB
d1mkq4fbm7j30i.cloudfront.net/17/oHS-17.js	0.0 ms	840 B
/pagead/js/r20260421/r20110914/elements/html/omrhp.js	1209600.0 s	4.7 KiB
/pagead/js/r20260421/r20110914/client/window_focus_fy2021.js	1209600.0 s	1.6 KiB
/v1.0/parent/67c7fcd8b0/engagement/trigger/user_sync?src=...	0.0 ms	154 B
/v1.0/parent/67c7fcd8b0/engagement/trigger/user_sync?src=...	0.0 ms	153 B
/tr?id=1636673763227734&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	19 B

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.

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:69.04 source:map[type:text value:[unattributed]]]]

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
Reconstruction of an extinct Dodo bird. (Photo by: David Tipling/Education Imag… `a.xRG > div.pxF > picture > img.N4z`	/uploads/getty/2023/1/31/8bf527ce-0b62-4fe5-9fa9-ee195ee6...	86.4 KiB	30.9 KiB
Billie Eilish and Jesse Rutherford attend the 11th Annual LACMA Art + Film Gala… `a.xRG > div.pxF > picture > img.N4z`	/uploads/image/2023/1/20/2a9966b1-884c-4e73-9b19-00e0aff9...	81.2 KiB	25.8 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: a.xRG > div.pxF > picture > img.N4z

path: 1,HTML,1,BODY,2,MAIN,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,A,0,DIV,1,PICTURE,3,IMG

selector: a.xRG > div.pxF > picture > img.N4z

snippet: <img alt="" src="https://imgix.bustle.com/uploads/image/2023/1/26/8a95114b-83f1-473f-b252-7…" class="N4z">

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

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

URL	Time Spent
mic.com/	754 ms
www.mic.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 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.8 s 353.0 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...	187.5 KiB	86.7 KiB
cmp.inmobi.com/tcfv2/61/cmp2.js?referer=www.mic.com	116.3 KiB	64.1 KiB
www.googletagmanager.com/gtag/js?id=G-F6C0PLEVJH	170.4 KiB	56.3 KiB
cdn2.bustle.com/2026/mic/prebid-light-d257e6fd86.js	92.2 KiB	43.0 KiB
cdn.id5-sync.com/api/1.0/esp.js	34.4 KiB	30.8 KiB
cdn2.bustle.com/2026/mic/main-87466c9f5e.js	67.9 KiB	27.0 KiB
d15kdpgjg3unno.cloudfront.net/oPS.js	60.0 KiB	24.0 KiB
cdn2.bustle.com/2026/mic/HubPage-7230f74a13.js	37.9 KiB	21.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
www.mic.com/	1.7 s	9.1 ms	1.8 ms
/pagead/managed/js/gpt/m202604210101/pubads_impl.js?cb=31...	798 ms	664 ms	82 ms
Unattributable	770 ms	169 ms	0.0 ms
cdn2.bustle.com/2026/mic/HubPage-7230f74a13.js	643 ms	457 ms	16 ms
www.googletagmanager.com/gtag/js?id=G-F6C0PLEVJH	484 ms	407 ms	70 ms
cmp.inmobi.com/tcfv2/61/cmp2.js?referer=www.mic.com	374 ms	258 ms	78 ms
d15kdpgjg3unno.cloudfront.net/oPS.js	339 ms	309 ms	26 ms
cdn2.bustle.com/2026/mic/prebid-light-d257e6fd86.js	323 ms	278 ms	39 ms
cdn2.bustle.com/2026/mic/main-87466c9f5e.js	192 ms	145 ms	26 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	118 ms	99 ms	18 ms
carbon-cdn.ccgateway.net/script?id=www.mic.com&parentId=67c7fcd8b0	97 ms	66 ms	8.8 ms
cdn2.bustle.com/2026/mic/vendors-6113da10bd.js	93 ms	88 ms	4.0 ms
secure.quantserve.com/aquant.js?a=p-xPmcrFNGfHkBg	77 ms	71 ms	4.2 ms
cdn.id5-sync.com/api/1.0/esp.js	71 ms	51 ms	16 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	3.2 s
Other	1.4 s
Style & Layout	972 ms
Script Parsing & Compilation	418 ms
Rendering	197 ms
Parse HTML & CSS	74 ms
Garbage Collection	28 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
The page has an unload handler in a sub frame.	Actionable

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

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 7 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 250 ms

●Server Backend Latencies 260 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 0 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.

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
The Grace and Frankie star talked to Mic about pro-vaccine thirst traps, buildi… `div.bw8 > div.Uz3 > a.L_P > p.qLW`
Grace and Frankie `div.Uz3 > a.L_P > p.qLW > i`
The wrestling entertainment company has a history of bigotry, but Belair — and … `div.bw8 > div.Uz3 > a.L_P > p.qLW`

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.K8W > div.YxB > div.izh > a.xkd `div.K8W > div.YxB > div.izh > a.xkd`

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

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

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

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

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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 have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○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

○Select elements have associated label elements.

○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
Topics	cdn2.bustle.com/2026/mic/prebid-light-d257e6fd86.js
Unload event listeners are deprecated and will be removed.	d15kdpgjg3unno.cloudfront.net/oPS.js line 231, col 309

●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

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
13	`License: https://rslcollective.org/attribution.xml`	`Unknown directive`

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

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`