Skip to content
https://thisismoney.co.uk

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.

40

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.

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:39.908 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.

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

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
div.article-preview > a > div.article-preview-image > img div.article-preview > a > div.article-preview-image > img
i.dailymail.com/1s/2026/04/22/13/108072355-0-image-a-2_1776860445431.jpg57.9 KiB18.4 KiB
I'm selling all 70 of my buy-to-lets - and buying a boat: Former Royal Navy man… div.article-preview > a > div.article-preview-image > img
i.dailymail.com/1s/2026/04/21/21/108054971-0-image-a-3_1776802397122.jpg52.9 KiB13.4 KiB
div.article-preview > a > div.article-preview-image > img div.article-preview > a > div.article-preview-image > img
i.dailymail.com/1s/2026/04/22/10/108068147-0-image-a-4_1776851157360.jpg47.8 KiB8.2 KiB

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

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: 1.5 s

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.

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.

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 Evaluation3.2 s
Other1.1 s
Style & Layout802 ms
Script Parsing & Compilation624 ms
Parse HTML & CSS206 ms
Rendering110 ms
Garbage Collection88 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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 9.9 KiB
URLTransfer SizeEst Savings
scripts.dailymail.com/rta2/v2-mol-3.14.4.js18.7 KiB9.9 KiB

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
div#infinite-list > div.infinite-scroll > a > img div#infinite-list > div.infinite-scroll > a > img
i.dailymail.com/i/pix/2026/03/30/IsaInvesting.svg
This is Money Home footer.footerContainer_AquJM997 > div.titleContainer_RMzId0G6 > a.logoContainer_YspMM2T3 > img.thisisMoneyLogo_ANldK7_n
/static/mol-fe/static/mol-fe-xpmodule-footer/1.8.3/thisIs...

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
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 20 long tasks found
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 190 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 510 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
62

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section > div.header-market-and-toggler > div.search-form-toggle > button.toggle-search-form section > div.header-market-and-toggler > div.search-form-toggle > button.toggle-search-form

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#infinite-list > div.infinite-scroll > a > img div#infinite-list > div.infinite-scroll > a > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.infinite-scroll > section > div.header-market-and-toggler > iframe div.infinite-scroll > section > div.header-market-and-toggler > iframe
div.scrollable-content > div#infinite-list > div.infinite-scroll > iframe div.scrollable-content > div#infinite-list > div.infinite-scroll > iframe

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.header-container > div.header-buttons > div.icon-mailsubscription-mobile-nav > a div.header-container > div.header-buttons > div.icon-mailsubscription-mobile-nav > a

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.

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
EXCLUSIVE div.article-preview > a > h2.headline > span.is-exclusive
Sponsored div#infinite-list > div.infinite-scroll > div.article-preview-sponsored > small
SPONSORED div.article-preview > div.article-preview-description > p > span.sponsored
Ad Feature div#infinite-list > div.infinite-scroll > div.article-preview-sponsored > small
AD FEATURE div.article-preview > div.article-preview-description > p > span.sponsored
EXCLUSIVE div.article-preview > a > h2.headline > span.is-exclusive
Ad Feature div#infinite-list > div.infinite-scroll > div.article-preview-sponsored > small
AD FEATURE div.article-preview > div.article-preview-description > p > span.sponsored
EXCLUSIVE div.article-preview > a > h2.headline > span.is-exclusive
EXCLUSIVE div.article-preview > a > h2.headline > span.is-exclusive
Ad Feature div#infinite-list > div.infinite-scroll > div.article-preview-sponsored > small
AD FEATURE div.article-preview > div.article-preview-description > p > span.sponsored
Sponsored div#infinite-list > div.infinite-scroll > div.article-preview-sponsored > small
SPONSORED div.article-preview > div.article-preview-description > p > span.sponsored
Ad Feature div#infinite-list > div.infinite-scroll > div.article-preview-sponsored > small
AD FEATURE div.article-preview > div.article-preview-description > p > span.sponsored
Ad Feature div#infinite-list > div.infinite-scroll > div.article-preview-sponsored > small
AD FEATURE div.article-preview > div.article-preview-description > p > span.sponsored
Reject and Purchase This is Money Essential div.option_A8417 > div.button-container_detg9 > button.button_cVc76 > span
Accept div.options_fXX5X > div.option_A8417 > div.button-container_detg9 > button.button_cVc76

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BUSINESS & MARKETS div#infinite-list > div.infinite-scroll > div.thick-split > h6
MONEY NEWS & ADVICE div#infinite-list > div.infinite-scroll > div.thick-split > h6
MORE BUSINESS & MARKETS NEWS div#infinite-list > div.infinite-scroll > div.thick-split > h6
YOUR MONEY ESSENTIALS div#infinite-list > div.infinite-scroll > div.thick-split > h6
SAVE MONEY, MAKE MONEY: TIPS AND GUIDES div#infinite-list > div.infinite-scroll > div.thick-split > h6

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.waiting-on-comments html.waiting-on-comments

These are opportunities to improve the interpretation of your content by users in different locales.

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 head > meta

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Prize Area Value of bond £1,000,000 Hampshire And Isle Of Wight £34,650 £1,000,… div#infinite-list > div.infinite-scroll > section.container-ArnVJCcM > table
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
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
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
Touch targets have sufficient size and spacing.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Document has a main landmark.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[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-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
`[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 a valid value for its `[lang]` attribute
`<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
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
`<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
Elements with visible text labels have matching accessible names.
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
Unload event listeners are deprecated and will be removed.

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
[mol-fe] ERROR: [videoTranscript] Required elements not found
Failed to load resource: the server responded with a status of 403 ()
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 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
77

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.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#infinite-list > div.infinite-scroll > a > img div#infinite-list > div.infinite-scroll > a > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Click here div.paragraphs_w60dD > div.paragraph_K0khv > span.login_AdWql > a.anchor_wIcyo
partners div.footnote_q_Agb > div.footnote-marker_Y7tXb > div.paragraph_K0khv > a.anchor_wIcyo
Privacy Settings div.footnotes_GrAYf > div.footnote_q_Agb > div.paragraph_K0khv > a.anchor_wIcyo
Privacy Settings div.footnote_q_Agb > div.footnote-marker_Y7tXb > div.paragraph_K0khv > a.anchor_wIcyo

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
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback