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
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js	604800.0 s	123.2 KiB
/p.css?s=1&k=vmh0wjw&ht=tk&f=17007.17008.17013.17016.3163...	604800.0 s	172 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.

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.

URL	Est Savings
/af/aa897e/00000000000000007735a1c8/30/l?primer=7cdcb44be...	25 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.

	URL	Resource Size	Est Savings
Two people on park bench smiling `article.media > div.field > picture > img`	/sites/default/files/styles/hero_xl/public/2026-01/two pe...	139.2 KiB	129.4 KiB
Small Talk Big Change logo on a purple background `div.c-collection-tile > div.field > picture > img`	/sites/default/files/styles/750_x_450_mhf_theme/public/20...	93.6 KiB	81.1 KiB
A group of university students sitting on some stairs `div.c-collection-tile > div.field > picture > img`	/sites/default/files/styles/750_x_450_mhf_theme/public/20...	56.5 KiB	44.0 KiB
MHAW 2026 x action `article.media > div.field > picture > img`	/sites/default/files/styles/750_x_450_mhf_theme/public/20...	50.1 KiB	38.7 KiB
Skydiver `div.c-collection-tile > div.field > picture > img`	/sites/default/files/styles/750_x_450_mhf_theme/public/20...	43.3 KiB	33.4 KiB
Girl Lying on Sofa and Using Smartphone `div.c-collection-tile > div.field > picture > img`	/sites/default/files/styles/750_x_450_mhf_theme/public/20...	26.6 KiB	20.6 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: Two people on park bench smiling

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

selector: article.media > div.field > picture > img

snippet: <img loading="eager" width="320" height="320" src="https://www.mentalhealth.org.uk/sites/default/files/styles/hero_xl/public/…" alt="Two people on park bench smiling">

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

value: no origins were preconnected

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
/sites/default/files/js/js_bcpdrfXnraf3w6hLtKT67bBpGCNymb...	19.7 KiB
use.typekit.net/vmh0wjw.css	1.2 KiB	775 ms
/p.css?s=1&k=vmh0wjw&ht=tk&f=17007.17008.17013.17016.3163...	172 B	752 ms
www.mentalhealth.org.uk/modules/contrib/google_tag/js/gtag.js?tdwbus	965 B	150 ms
/sites/default/files/js/js_s10-Dh-wa11efHL_o6wFmm_VjKm7NA...	642 B
www.mentalhealth.org.uk/modules/contrib/google_tag/js/gtm.js?tdwbus	1.0 KiB
/sites/default/files/css/css_DGBiLh0b8FCGrxO5GjWhATI1FgzL...	15.6 KiB
/sites/default/files/css/css_41CnlorFoF5rGWviyESGk649W0YN...	7.5 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: 815 ms

URL	Time Spent
mentalhealth.org.uk/	815 ms
www.mentalhealth.org.uk/	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.9 s 412.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-HJ268Y8NF0&cx=c&gtm=4e64k0	166.8 KiB	66.1 KiB
www.googletagmanager.com/gtag/destination?id=DC-11797174&cx=c&gtm=4e64k0	129.8 KiB	64.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-KB2K2D	171.8 KiB	64.8 KiB
www.googletagmanager.com/gtag/js?id=AW-1018585103&cx=c&gtm=4e64k0	137.1 KiB	64.3 KiB
www.googletagmanager.com/gtag/js?id=AW-1000813537&cx=c&gtm=4e64k0	137.1 KiB	63.4 KiB
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js	122.8 KiB	57.5 KiB
/sites/default/files/js/js_awi3CNOFOzZnLrxuwkNkEqCzcmZX9U...	44.4 KiB	31.4 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.googletagmanager.com/gtm.js?id=GTM-KB2K2D	389 ms	305 ms	48 ms
www.mentalhealth.org.uk/	338 ms	10 ms	0.9 ms
www.googletagmanager.com/gtag/destination?id=DC-11797174&cx=c&gtm=4e64k0	309 ms	274 ms	33 ms
cc.cdn.civiccomputing.com/9/cookieControl-9.x.min.js	236 ms	193 ms	43 ms
www.googletagmanager.com/gtag/js?id=G-HJ268Y8NF0&cx=c&gtm=4e64k0	215 ms	162 ms	52 ms
Unattributable	214 ms	7.0 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=AW-1018585103&cx=c&gtm=4e64k0	155 ms	115 ms	39 ms
www.googletagmanager.com/gtag/js?id=AW-1000813537&cx=c&gtm=4e64k0	151 ms	111 ms	38 ms
/sites/default/files/js/js_awi3CNOFOzZnLrxuwkNkEqCzcmZX9U...	131 ms	96 ms	9.7 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	1.3 s
Other	292 ms
Script Parsing & Compilation	274 ms
Style & Layout	261 ms
Parse HTML & CSS	55 ms
Rendering	24 ms

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
Home `div.c-header-bottom-container > div.c-branding > a.c-branding__logo > img`	www.mentalhealth.org.uk/themes/custom/mhf_theme/logo.svg

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,538 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 11 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 70 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.

●Select elements have associated label elements.

●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

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

●Identical links have the same purpose.

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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

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

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.mentalhealth.org.uk/explore-mental-health/a-z-topics	Learn more
www.mentalhealth.org.uk/explore-mental-health/publications	Learn more
www.mentalhealth.org.uk/explore-mental-health/your-mental-health	Learn more
/explore-mental-health/support-someone-with-their-mental-...	Learn more

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

○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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`