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
consent.cookiebot.com/uc.js	548.0 s	35.7 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 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: Glasgow skyline at night with reflection in Clyde river

path: 1,HTML,1,BODY,6,DIV,0,DIV,2,MAIN,2,DIV,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,1,DIV,0,ARTICLE,0,A,1,DIV,0,IMG

selector: article.c-teaser > a.h-full > div.image-container > img.w-full

snippet: <img width="200" height="113" class="w-full h-full aspect-[16/9] object-cover lazyautosizes lazyloaded" loading="lazy" data-sizes="auto" data-srcset="/sites/default/files/styles/16_9_media_2xs/public/2026-04/Glasgow-skyline.…" alt="Glasgow skyline at night with reflection in Clyde river" sizes="388px" srcset="/sites/default/files/styles/16_9_media_2xs/public/2026-04/Glasgow-skyline.…">

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

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
consent.cookiebot.com/uc.js	35.7 KiB	1.4 s
/sites/default/files/css/css_HZUYmcBk-xep5jxvzjmxAJ8YfKVB...	598 B	186 ms
/sites/default/files/css/css_K_97nM_iJvTIWk8DJA9yXRTPh-yS...	14.2 KiB	506 ms

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.

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
Glasgow skyline at night with reflection in Clyde river `article.c-teaser > a.h-full > div.image-container > img.w-full`	/sites/default/files/styles/16_9_media_sm/public/2026-04/...	34.9 KiB	25.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: 1.4 s

URL	Time Spent
ncsc.gov.uk/	753 ms
www.ncsc.gov.uk/	630 ms
www.ncsc.gov.uk/	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: 900 ms 149.6 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-P53HXRL7	136.4 KiB	66.3 KiB
/41122ea9-38a1-4f2b-8115-6804e417cddb/cc.js?renew=false&r...	544.5 KiB	60.4 KiB
consent.cookiebot.com/uc.js	35.5 KiB	22.8 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
/41122ea9-38a1-4f2b-8115-6804e417cddb/cc.js?renew=false&r...	1.1 s	556 ms	116 ms
Unattributable	608 ms	65 ms	0.0 ms
www.ncsc.gov.uk/	315 ms	24 ms	1.4 ms
www.googletagmanager.com/gtm.js?id=GTM-P53HXRL7	274 ms	200 ms	70 ms
consent.cookiebot.com/uc.js	138 ms	117 ms	15 ms
www.ncsc.gov.uk/themes/custom/lakes/dist//main-site-BQlwULPI.js	116 ms	68 ms	0.1 ms
www.ncsc.gov.uk/themes/custom/lakes/dist//gsap-core-DxSJLJiy.js	95 ms	18 ms	0.5 ms
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	54 ms	35 ms	4.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.1 s
Other	683 ms
Parse HTML & CSS	399 ms
Style & Layout	327 ms
Script Parsing & Compilation	211 ms
Rendering	48 ms
Garbage Collection	30 ms

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: 0.0 ms 11.2 KiB

URL	Transfer Size	Est Savings
	13.5 KiB	11.2 KiB

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●Avoid long main-thread tasks 6 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 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 70 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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.

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
Experienced a cyber attack? `div.bg-notification > div.c-container > a.flex > h4.mb-0`

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
Experienced a cyber attack? `div.bg-notification > div.c-container > a.flex > h4.mb-0`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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 > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`

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.

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
NEW TODAY NEWS Cyber chief: UK faces "perfect storm" for cyber security As the… `div.py-fl-lg > div.mt-fl-sm > article.c-teaser > a.h-full`
BLOG POST Preparing for severe cyber threat: why leaders must act now A call t… `div.mt-fl-sm > div.h-full > article.@container > a.w-full`
NEW TODAY BLOG POST New cross domain guidance for government, industry and the … `div.mt-fl-sm > div.h-full > article.@container > a.w-full`
GUIDANCE Cyber Assessment Framework The CAF is a collection of cyber security … `div.py-fl-lg > div.grid > article.c-teaser > a.h-full`
GUIDANCE Cyber Security Toolkit for Boards Resources to help Boards implement … `div.py-fl-lg > div.grid > article.c-teaser > a.h-full`
GUIDANCE Recovering a hacked account A step by step guide to recovering online… `div.py-fl-lg > div.grid > article.c-teaser > a.h-full`
GUIDANCE Managing your passwords Why you should use a password manager to ‘rem… `div.py-fl-lg > div.grid > article.c-teaser > a.h-full`
GUIDANCE Data breaches: guidance for individuals and families How to protect y… `div.py-fl-lg > div.grid > article.c-teaser > a.h-full`

○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

●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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●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

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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

○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

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 > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div > div.px-fl-sm > div.relative > img.w-32 `div > div.px-fl-sm > div.relative > img.w-32`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`
div.c-container > div.grid > div.relative > img.w-full `div.c-container > div.grid > div.relative > img.w-full`

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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`