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
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	91.1 KiB
pub.doubleverify.com/dvtag/29287203/DV1106009/pub.js	900.0 s	33.5 KiB
api.receptivity.io/v1/prebid/ASCP250505/connector/rxConnector.js	3600.0 s	8.7 KiB
tags.crwdcntrl.net/lt/c/16576/sync.min.js	86400.0 s	13.1 KiB
config.aps.amazon-adsystem.com/configs/c9db8c50-566c-4cc8-bec8-2dfdd68f67d1	3600.0 s	2.0 KiB
/hadron.js?url=https%3A%2F%2Fdailydot.com%2F&ref=&_it=ama...	432000.0 s	186 B

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:49.478 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
div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/lana-del-rey-husband...	199.3 KiB	160.5 KiB
lets get this place humid `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/lets-get-this-place-...	52.9 KiB	47.7 KiB
olaf malfunctions disney `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/olaf-malfunctions-di...	45.4 KiB	40.1 KiB
leann rimes jaw therapy release crying `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/leann-rimes-jaw-ther...	39.6 KiB	34.4 KiB
kid rock army helicopter flyover `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/kid-rock-army-helico...	36.7 KiB	31.5 KiB
Stacks of old books in different colors. `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/gen-z-first-person-1...	29.6 KiB	24.3 KiB
horseshoe theory of male haircuts `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/horseshoe-theory-of-...	29.5 KiB	24.3 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-0-IMG

nodeLabel: div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p

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

selector: div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p

snippet: <img alt="" width="725" height="408" decoding="async" data-nimg="1" class="image_image__Tzd4p" style="color:transparent;aspect-ratio:16 / 9" sizes="(max-width: 30rem) 440px, (min-width: 30rem) and (max-width: 40rem) 600px,…" srcset="https://lede-admin.dailydot.com/wp-content/uploads/sites/69/2026/03/lana-d…" src="https://lede-admin.dailydot.com/wp-content/uploads/sites/69/2026/03/lana-d…">

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
/css2?family=Mulish:ital,wght@0,200..1000;1,200..1000&dis...	1.1 KiB	817 ms

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

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: 300 ms 37.3 KiB

URL	Transfer Size	Est Savings
dailydot.com/_next/static/css/01d954090589a7ed.css	27.6 KiB	23.2 KiB
dailydot.com/_next/static/css/ed60127db3fd768b.css	15.6 KiB	14.1 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: 1.8 s 549.7 KiB

URL	Transfer Size	Est Savings
hb-dailydot.s3.us-east-2.amazonaws.com/asc_prebid.js	219.6 KiB	147.2 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	142.2 KiB
mercuryace.com/public/pssweki29mewfm_3e/ConsentManager,Sticky2	195.4 KiB	84.7 KiB
dailydot.com/_next/static/chunks/6071-28b6034731af5875.js	113.2 KiB	61.6 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.6 KiB	49.7 KiB
mercuryace.com/public/rfund9/ft3zyl.min.js	62.3 KiB	22.3 KiB
dailydot.com/_next/static/chunks/framework-75738a6c54ac7ad3.js	56.3 KiB	21.4 KiB
dailydot.com/_next/static/chunks/main-2564581cee2552bf.js	39.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
dailydot.com/_next/static/chunks/framework-75738a6c54ac7ad3.js	1.3 s	1.2 s	13 ms
Unattributable	938 ms	348 ms	0.0 ms
mercuryace.com/public/pssweki29mewfm_3e/ConsentManager,Sticky2	711 ms	510 ms	59 ms
dailydot.com/	572 ms	62 ms	2.6 ms
hb-dailydot.s3.us-east-2.amazonaws.com/asc_prebid.js	409 ms	350 ms	54 ms
dailydot.com/_next/static/chunks/pages/_sites/%5BsiteSlug%5D-77b1d82a9b4bbe0f.js	237 ms	236 ms	0.3 ms
mercuryace.com/public/rfund9/ft3zyl.min.js	175 ms	80 ms	20 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	172 ms	124 ms	46 ms
c.amazon-adsystem.com/aax2/apstag.js	170 ms	128 ms	29 ms
dailydot.com/_next/static/chunks/main-2564581cee2552bf.js	134 ms	109 ms	11 ms
api.receptivity.io/v1/prebid/ASCP250505/connector/rxConnector.js	68 ms	36 ms	2.1 ms
pub.doubleverify.com/dvtag/29287203/DV1106009/pub.js	62 ms	50 ms	10.0 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	61 ms	53 ms	7.5 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.4 s
Other	716 ms
Style & Layout	507 ms
Script Parsing & Compilation	326 ms
Garbage Collection	121 ms
Parse HTML & CSS	96 ms
Rendering	59 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

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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 120 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 270 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
ENTERTAINMENT `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
See all posts `div.PostRiver_wrapper__7Mk_l > div.PostList_threeAcrossWrapper__lF_fc > div.PostList_header__6fpl3 > a.PostList_link__3FMIL`
CULTURE `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
TRENDING `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
TRENDING `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
TRENDING `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
CULTURE `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
TRENDING `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
VIRAL POLITICS `div.PostCard_left__N7nXY > div.PostCard_eyebrowWrapper__JvnGi > a.Eyebrow_wrapper__92RAO > span`
PURPOSES `div.Card-buoy__sc-1s2p2gv-0 > div.Frame-buoy__sc-1d4hofp-0 > div.Pills__StyledPills-buoy__sc-pti2cl-0 > button.Pills__StyledPill-buoy__sc-pti2cl-1`
999 PARTNERS `div.Card-buoy__sc-1s2p2gv-0 > div.Frame-buoy__sc-1d4hofp-0 > div.Pills__StyledPills-buoy__sc-pti2cl-0 > button.Pills__StyledPill-buoy__sc-pti2cl-1`

These are opportunities to improve the legibility of your content.

○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

●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

●Document has a `<title>` element

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○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

○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

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
leann rimes jaw therapy release crying `div.PostCard_right__rSqvG > a.PostCard_cardImage__C9Ww7 > figure > img.image_image__Tzd4p`	/wp-content/uploads/sites/69/2026/03/leann-rimes-jaw-ther...	372 x 248	220 x 147	558 x 372

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
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.	dailydot.com/

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
api.rlcdn.com/api/identity/envelope?pid=13934	`Failed to load resource: the server responded with a status of 451 ()`

●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

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