Skip to content
https://ladbible.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.

47

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

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
value: No additional origins are good candidates for preconnecting

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.

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
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
silo66.p7cloud.net/as1.js?uri=https%3A%2F%2Fwww.ladbible.com3600.0 s89.3 KiB
pagead2.googlesyndication.com/pagead/js/lidar.js?fcd=true3600.0 s83.1 KiB
ats.rlcdn.com/ats.js0.0 ms36.7 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=86041800.0 s41.6 KiB
consent.ladbible.com/unified/wrapperMessagingWithoutDetection.js3600.0 s40.4 KiB
cp.ladbible.com/now.js600.0 s35.2 KiB
cdn.id5-sync.com/api/1.0/id5-api.js3600.0 s34.4 KiB
static.chartbeat.com/js/chartbeat_video.js7200.0 s24.8 KiB
/2b03064a-e5c4-45db-bee9-7cf48527580b.js?pbxd=https%3A%2F...3600.0 s18.7 KiB
api.receptivity.io/v1/prebid/LADP250610/connector/rxConnector.js3600.0 s8.6 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYHDFg5L...7200.0 s7.5 KiB
tags.crwdcntrl.net/lt/c/16589/sync.min.js86400.0 s13.5 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8KTCefA...7200.0 s6.7 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FkJdTn6v...7200.0 s6.2 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBfI0PuD...7200.0 s6.1 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1SvTApm...7200.0 s6.0 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_4B2Ko7...7200.0 s5.7 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FikJXJvJ...7200.0 s4.9 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgggPtFR...7200.0 s4.6 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgXW9YFf...7200.0 s4.4 KiB
/_next/image?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fe_MEFex...7200.0 s4.1 KiB
cdn.edkt.io/tA07x6/edgekit.min.js86400.0 s6.9 KiB
silo66.p7cloud.net/l.js?uri=https://www.ladbible.com0.0 ms1.8 KiB
config.aps.amazon-adsystem.com/configs/39203600.0 s2.0 KiB
/c/361/0/8/1.gif?gdpr=0&gdpr_consent=&gpp=DBAA&gpp_sid=-1...0.0 ms1.0 KiB
applets.ebxcdn.com/ebx.js7200.0 s1.0 KiB
www.ladbible.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js2867.0 s737 B
/p.png?visit=page&arcid=0b3f0fb0-46e0-4d29-9a6f-7fb706fd5...0.0 ms533 B
ua.p7cloud.net/asp?aspan=YXJjc3Bhbi11c2VyOmFyY3NwYW4tZHJvd3NzYXA0.0 ms329 B
/13333?uri=0b3f0fb0-46e0-4d29-9a6f-7fb706fd5092&region=eu0.0 ms286 B
/track/cmb/generic?ttd_pid=tapad&ttd_tpi=1&ttd_puid=900bc...0.0 ms254 B
/hadron.js?url=https%3A%2F%2Fwww.ladbible.com%2F&ref=&_it...432000.0 s187 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.

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: 802 ms
URLTime Spent
ladbible.com/802 ms
www.ladbible.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: 160 ms 28.0 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.ladbible.com/_next/static/chunks/1517-7fdef48b9c3f2303.js1.8 s1.6 s30 ms
Unattributable1.4 s311 ms0.0 ms
www.ladbible.com/_next/static/chunks/8606-b62fbe487961dfc5.js980 ms427 ms3.5 ms
www.ladbible.com/690 ms60 ms50 ms
micro.rubiconproject.com/prebid/dynamic/13128.js592 ms490 ms85 ms
fundingchoicesmessages.google.com/i/106213651?ers=3459 ms352 ms29 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js356 ms265 ms80 ms
config.aps.amazon-adsystem.com/configs/3920255 ms238 ms6.0 ms
silo66.p7cloud.net/as1.js?uri=https%3A%2F%2Fwww.ladbible.com248 ms184 ms59 ms
www.googletagmanager.com/gtag/destination?id=G-XXXXXXXXXX&cx=c&gtm=4e64k1244 ms191 ms52 ms
consent.ladbible.com/unified/4.40.1/usnat.f12613136193900e32e2.bundle.js201 ms146 ms55 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=8604198 ms182 ms1.2 ms
www.ladbible.com/_next/static/chunks/b536a0f1-d45603aa3caf459b.js196 ms152 ms43 ms
cdn.id5-sync.com/api/1.0/id5-api.js191 ms124 ms50 ms
c.amazon-adsystem.com/aax2/apstag.js188 ms115 ms51 ms
www.googletagmanager.com/gtag/js?id=G-ZSZ528CV9S170 ms106 ms63 ms
ats.rlcdn.com/ats.js166 ms117 ms45 ms
www.ladbible.com/_next/static/chunks/8554-7364b063c52f6ecc.js147 ms145 ms1.1 ms
securepubads.g.doubleclick.net/tag/js/gpt.js131 ms104 ms22 ms
api.receptivity.io/v1/prebid/LADP250610/connector/rxConnector.js128 ms104 ms3.3 ms
static.chartbeat.com/js/chartbeat_video.js119 ms107 ms9.8 ms
metrics.rapidedge.io/gamera.js?ltv=1&audience=1&tpcs=1&partner=magnite112 ms90 ms15 ms
www.ladbible.com/_next/static/chunks/4bd1b696-584e3c556642bbc3.js110 ms41 ms22 ms
cdn1.anonymised.io/light/bundle.js?v=1.8.54105 ms87 ms11 ms
pagead2.googlesyndication.com/pagead/js/lidar.js?fcd=true102 ms62 ms37 ms
consent.ladbible.com/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js81 ms55 ms26 ms
consent.ladbible.com/unified/wrapperMessagingWithoutDetection.js77 ms53 ms24 ms
tags.crwdcntrl.net/lt/c/16589/sync.min.js75 ms62 ms6.7 ms
cdn.edkt.io/tA07x6/edgekit.min.js66 ms60 ms3.1 ms
cp.ladbible.com/now.js63 ms48 ms13 ms
static.anonymised.io/light/loader.js?ref=aps&d=www.ladbible.com55 ms37 ms2.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.5 s
Other1.9 s
Script Parsing & Compilation1.0 s
Style & Layout349 ms
Parse HTML & CSS178 ms
Garbage Collection124 ms
Rendering104 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

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
●Improve image delivery
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,439 KiB
●User Timing marks and measures 11 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 240 ms
●Server Backend Latencies 850 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 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>`
●`[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.
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●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 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.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
81

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
Unload event listeners are deprecated and will be removed.
●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 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`

Send Feedback