Skip to content
https://bustle.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

30

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.

RequestCache TTLTransfer Size
cdn.doubleverify.com/dvbm.js900.0 s101.7 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
cmp.inmobi.com/tcfv2/61/cmp2.js?referer=www.bustle.com172800.0 s133.4 KiB
cdn.id5-sync.com/api/1.0/esp.js3600.0 s34.7 KiB
d15kdpgjg3unno.cloudfront.net/oPS.js84600.0 s60.3 KiB
s0.2mdn.net/879366/express_html_inpage_rendering_lib_200_287.js86400.0 s40.9 KiB
link.rubiconproject.com/magnite/17652.js0.0 ms15.4 KiB
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s14.1 KiB
www.googletagservices.com/dcm/dcmads.js3600.0 s7.8 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js86400.0 s7.8 KiB
cmp.inmobi.com/choice/xPmcrFNGfHkBg/www.bustle.com/choice.js?tag_version=V3900.0 s3.1 KiB
rules.quantcount.com/rules-p-xPmcrFNGfHkBg.js3600.0 s3.0 KiB
d1mkq4fbm7j30i.cloudfront.net/17/oHS-17.js0.0 ms837 B
/pagead/js/r20260420/r20110914/elements/html/omrhp.js1209600.0 s4.7 KiB
/tracker/09f48dbd-cbfe-45c1-a1af-2e22e12029ca/pixel.gif?p...0.0 ms340 B
/tr?id=1636673763227734&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:15.428 source:map[column:288989 line:2 type:source-location url:https://cdn.doubleverify.com/dvbm.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:121.625 source:map[type:text value:[unattributed]]] map[reflowTime:2.142 source:map[column:36170 line:0 type:source-location url:https://cdn2.bustle.com/2026/bustle/main-2a88bb4eb4.js urlProvider:network]] map[reflowTime:0.413 source:map[column:47159 line:0 type:source-location url:https://cdn2.bustle.com/2026/bustle/main-2a88bb4eb4.js urlProvider:network]] map[reflowTime:47.587 source:map[column:134524 line:0 type:source-location url:https://cdn2.bustle.com/2026/bustle/main-2a88bb4eb4.js urlProvider:network]] map[reflowTime:14.153 source:map[column:31437 line:0 type:source-location url:https://cdn2.bustle.com/2026/bustle/HubPage-b8764176d1.js urlProvider:network]] map[reflowTime:3.28 source:map[column:31479 line:0 type:source-location url:https://cdn2.bustle.com/2026/bustle/HubPage-b8764176d1.js urlProvider:network]] map[reflowTime:1.494 source:map[column:102033 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31097946 urlProvider:network]] map[reflowTime:0.637 source:map[column:241846 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31097946 urlProvider:network]] map[reflowTime:1.729 source:map[column:193722 line:1 type:source-location url:https://cdn.doubleverify.com/dvbm.js urlProvider:network]] map[reflowTime:11.624 source:map[column:283889 line:1 type:source-location url:https://cdn.doubleverify.com/dvbm.js urlProvider:network]] map[reflowTime:1.781 source:map[column:709 line:300 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/activeview/current/ufs_web_display.js urlProvider:network]] map[reflowTime:3.804 source:map[column:341092 line:1 type:source-location url:https://cdn.doubleverify.com/dvbm.js urlProvider:network]] map[reflowTime:3.454 source:map[column:1361 line:159 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/activeview/current/ufs_web_display.js urlProvider:network]]]

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: Bustle's fashion editors review the Old Navy x Christopher John Rogers collabor…
path: 1,HTML,1,BODY,2,MAIN,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,A,0,DIV,0,IMG
selector: div.net > a.MKc > div.vmZ > img.EdX
snippet: <img src="https://imgix.bustle.com/uploads/image/2026/4/14/e71fe762/selt6637_2.jpg?w…" srcset="https://imgix.bustle.com/uploads/image/2026/4/14/e71fe762/selt6637_2.jpg?w…" sizes="(min-width:1025px) 216px, (min-width:768px) 206px, 196px" alt="Bustle's fashion editors review the Old Navy x Christopher John Rogers col…" class="EdX">

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

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.

URLEst Savings
/sadbundle/16475458024834687192/EmberModernDisplayStd-Bol...10 ms
/sadbundle/16475458024834687192/EmberModernDisplayStd-Reg...10 ms

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.

URLResource SizeEst Savings
head > meta head > meta
s0.2mdn.net/sadbundle/16475458024834687192/zzquil.jpg55.9 KiB45.4 KiB

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: 759 ms
URLTime Spent
bustle.com/759 ms
www.bustle.com/0.0 ms

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.

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.6 s 467.7 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...187.4 KiB83.5 KiB
www.googletagmanager.com/gtag/js?id=G-C3PETV5ZL1168.1 KiB64.5 KiB
cmp.inmobi.com/tcfv2/61/cmp2.js?referer=www.bustle.com133.0 KiB64.2 KiB
cdn2.bustle.com/2026/bustle/prebid-light-4eb2a90476.js92.0 KiB43.1 KiB
cdn.doubleverify.com/dvbm.js101.4 KiB38.7 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js73.1 KiB31.6 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js73.1 KiB30.9 KiB
cdn.id5-sync.com/api/1.0/esp.js34.4 KiB30.7 KiB
cdn2.bustle.com/2026/bustle/main-2a88bb4eb4.js73.4 KiB28.3 KiB
cdn2.bustle.com/2026/bustle/HubPage-b8764176d1.js53.0 KiB28.3 KiB
d15kdpgjg3unno.cloudfront.net/oPS.js59.8 KiB23.9 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.bustle.com/4.6 s11 ms3.9 ms
Unattributable1.3 s103 ms0.0 ms
/pagead/managed/js/activeview/current/ufs_web_display.js1.2 s841 ms161 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...1.1 s952 ms69 ms
d15kdpgjg3unno.cloudfront.net/oPS.js1.0 s952 ms55 ms
cdn2.bustle.com/2026/bustle/HubPage-b8764176d1.js997 ms686 ms17 ms
cdn.doubleverify.com/dvbm.js701 ms569 ms48 ms
cmp.inmobi.com/tcfv2/61/cmp2.js?referer=www.bustle.com476 ms366 ms58 ms
www.googletagservices.com/dcm/impl_v106.js357 ms187 ms7.3 ms
www.googletagmanager.com/gtag/js?id=G-C3PETV5ZL1349 ms287 ms58 ms
cdn2.bustle.com/2026/bustle/main-2a88bb4eb4.js302 ms136 ms25 ms
cdn2.bustle.com/2026/bustle/prebid-light-4eb2a90476.js262 ms209 ms27 ms
s0.2mdn.net/879366/express_html_inpage_rendering_lib_200_287.js221 ms188 ms17 ms
cdn2.bustle.com/2026/bustle/vendors-5d3a1fdc4f.js204 ms164 ms3.5 ms
/visit.js?gdpr=&gdpr_consent=&flvr=1&ttmms=10&ttfrms=52&b...123 ms121 ms0.8 ms
/ddm/adj/N2464377.4590158BUSTLEBDG/B35375962.443310400;dc...118 ms60 ms43 ms
carbon-cdn.ccgateway.net/script?id=www.bustle.com&parentId=67c7fcd8b0118 ms78 ms9.8 ms
securepubads.g.doubleclick.net/tag/js/gpt.js106 ms94 ms11 ms
cdn.id5-sync.com/api/1.0/esp.js101 ms80 ms13 ms
ep2.adtrafficquality.google/sodar/sodar2.js85 ms69 ms2.3 ms
ep2.adtrafficquality.google/sodar/VFc2VJAc.js70 ms61 ms8.2 ms
secure.quantserve.com/aquant.js?a=p-xPmcrFNGfHkBg65 ms58 ms5.6 ms
link.rubiconproject.com/magnite/17652.js61 ms50 ms7.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.

CategoryTime Spent
Script Evaluation6.4 s
Other3.5 s
Style & Layout2.3 s
Rendering832 ms
Script Parsing & Compilation663 ms
Garbage Collection185 ms
Parse HTML & CSS138 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 reasonFailure type
The page has an unload handler in the main frame.Actionable
The page has an unload handler in a sub frame.Actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
dr58mx4d40r1x.cloudfront.net/461758112/medium.mp41.7 MiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...187.4 KiB
www.googletagmanager.com/gtag/js?id=G-C3PETV5ZL1168.4 KiB
cmp.inmobi.com/tcfv2/61/cmp2.js?referer=www.bustle.com133.4 KiB
cdn.doubleverify.com/dvbm.js101.7 KiB
cdn2.bustle.com/2026/bustle/prebid-light-4eb2a90476.js92.7 KiB
www.bustle.com/80.5 KiB
cmp.inmobi.com/GVL-v3/vendor-list-trimmed-v1.json76.0 KiB
cdn2.bustle.com/2026/bustle/main-2a88bb4eb4.js74.1 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js73.1 KiB

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

●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●User Timing marks and measures 9 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 170 ms
●Server Backend Latencies 160 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
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>`
●`[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
●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
●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.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○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.
77

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 / WarningSource
Topics
cdn2.bustle.com/2026/bustle/prebid-light-4eb2a90476.js
Unload event listeners are deprecated and will be removed.
www.googletagservices.com/dcm/impl_v106.js line 125, col 359
SharedStorage
/pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234
AttributionReporting

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.

SourceDescription
/v1/starV6.gif?evt=hi&pid=26nEsOZ7NCUsCSaKqB3J9aRKBmRd&sr...
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
about:srcdoc
Refused to execute script from 'https://idsync.rlcdn.com/382696.gif?partner_uid=653088fe-e0b0-4517-9a5f-130a4c7a1ab2' because its MIME type ('image/gif') is not executable.
●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 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
92

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 #ContentError
13License: https://rslcollective.org/attribution.xmlUnknown 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`

Send Feedback