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

21

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.353569] map[node:map[boundingRect:map[bottom:837 height:418 left:8 right:405 top:419 width:397] lhId:page-3-DIV nodeLabel:Keep us beating Every 3 minutes, someone in the UK dies from cardiovascular di… path:3,HTML,2,BODY,7,MAIN,1,SECTION,0,DIV,0,DIV,0,DIV selector:section.high-impact-hero__container > div.container > div.row > div.col-12 snippet:<div class="col-12 col-md-6 high-impact-hero__copy-wrapper"> type:node] score:0.318796] map[node:map[boundingRect:map[bottom:837 height:739 left:0 right:412 top:98 width:412] lhId:page-5-SECTION nodeLabel:Keep us beating Every 3 minutes, someone in the UK dies from cardiovascular di… path:3,HTML,2,BODY,7,MAIN,1,SECTION selector:body.with-main-navigation > main.cd-main-content > section.high-impact-hero__container snippet:<section data-tracking-id="homepage-hero-banner" class="high-impact-hero__container container-border--rounded-bottom" style="position: relative; z-index: 10; margin-top: -32px;"> type:node] score:0.034252] map[node:map[boundingRect:map[bottom:130 height:70 left:155 right:392 top:60 width:237] lhId:page-1-UL nodeLabel:Search Sign in/Register Menu path:3,HTML,2,BODY,6,NAV,0,DIV,0,DIV,0,DIV,0,DIV,2,UL selector:div.container > div.row > div.col-12 > ul.main-navigation__container__right snippet:<ul class="main-navigation__container__right"> type:node] score:0.000521]]

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.

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:70.967 source:map[column:65295 line:1 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= 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:111.874 source:map[type:text value:[unattributed]]] map[reflowTime:0.776 source:map[column:122135 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:0.597 source:map[column:87570 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:0.31 source:map[column:87632 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:0.271 source:map[column:87700 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:56.441 source:map[column:87863 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:9.259 source:map[column:467561 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:0.195 source:map[column:374001 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:0.57 source:map[column:89088 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= urlProvider:network]] map[reflowTime:2.548 source:map[column:87885 line:0 type:source-location url:https://www.bhf.org.uk/assets/js/app-mvc.js?v=6snWwysaXYUPvFVemwjQnExtiSaz8ZpjHfBEdtahKaA= 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: A young boy sat on a red bench looking forward
path: 3,HTML,2,BODY,7,MAIN,1,SECTION,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG
selector: div.row > div.col-12 > div.high-impact-hero__image > img.high-impact-hero__image--main
snippet: <img src="/-/media/images/keep-us-beating/bhf-home-keep-us-beating-video-thumbnail-b…" class="high-impact-hero__image--main fallback-image hidden" alt="A young boy sat on a red bench looking forward" style="display: inline;">

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

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
A young boy sat on a red bench looking forward div.row > div.col-12 > div.high-impact-hero__image > img.high-impact-hero__image--main
/-/media/images/keep-us-beating/bhf-home-keep-us-beating-...42.3 KiB35.6 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: 781 ms
URLTime Spent
bhf.org.uk/781 ms
www.bhf.org.uk/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Keep us beating Every 3 minutes, someone in the UK dies from cardiovascular di… section.high-impact-hero__container > div.container > div.row > div.col-12
0.319
Keep us beating Every 3 minutes, someone in the UK dies from cardiovascular di… body.with-main-navigation > main.cd-main-content > section.high-impact-hero__container
0.034
Search Sign in/Register Menu div.container > div.row > div.col-12 > ul.main-navigation__container__right
0.001

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 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: 900 ms 210.3 KiB
URLTransfer SizeEst Savings
/assets/css/styles-with-grid-system.css?v=Ww26qMeXN1L7WZj...195.4 KiB190.1 KiB
23.3 KiB20.2 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.

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.7 s
Other1.5 s
Style & Layout1.0 s
Script Parsing & Compilation780 ms
Garbage Collection234 ms
Parse HTML & CSS187 ms
Rendering122 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
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

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
British Heart Foundation Logo div.g-footer__wrap > section.g-footer__bottom > a > img.left
/-/media/system/logo-white.svg?rev=f07c00ef8c1c41bcb2458b...
Registered with the Fundraising Regulator div.g-footer__wrap > section.g-footer__bottom > a > img.right
/-/media/system/fr-white.svg?rev=a8b55cd0fd5744c69e76938d...
BHF logo div.row > div.masthead > a.masthead__logo > img.masthead__logo--mobile
www.bhf.org.uk/assets/img/BHF-logo.svg

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

●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoid long main-thread tasks 20 long tasks found
●Network Requests
●Network Round Trip Times 0 ms
●Server Backend Latencies 60 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 310 ms
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
cookie policy. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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.
●`[accesskey]` values are unique
●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
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`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
○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
○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.
○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

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
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