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
connect.facebook.net/en_US/fbevents.js	1200.0 s	97.1 KiB
/signals/config/490624601338237?v=2.9.313&r=stable&domain...	1200.0 s	44.7 KiB
/tr/?id=490624601338237&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	19 B

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.132389] map[node:map[boundingRect:map[bottom:425 height:396 left:22 right:390 top:29 width:369] lhId:page-9-DIV nodeLabel:Discover More Discover More Discover More We've helped CONNECT Aviation to tran… path:1,HTML,1,BODY,1,MAIN,1,SECTION,1,DIV,3,DIV,1,DIV selector:section.splash > div.container > div.row > div.col-md-10 snippet:<div class="col-md-10 maincol"> type:node] score:0.11904] map[node:map[boundingRect:map[bottom:425 height:396 left:22 right:390 top:29 width:369] lhId:page-9-DIV nodeLabel:Discover More Discover More Discover More We've helped CONNECT Aviation to tran… path:1,HTML,1,BODY,1,MAIN,1,SECTION,1,DIV,3,DIV,1,DIV selector:section.splash > div.container > div.row > div.col-md-10 snippet:<div class="col-md-10 maincol"> type:node] score:0.013272] map[node:map[boundingRect:map[bottom:319 height:30 left:47 right:47 top:289 width:0] lhId:page-8-::after nodeLabel:div.owl-item > div.slide > h2.h1 > ::after path:1,HTML,1,BODY,1,MAIN,1,SECTION,1,DIV,3,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,3,DIV,0,DIV,0,H2,0,::after selector:div.owl-item > div.slide > h2.h1 > ::after snippet:<::after> type:node] score:2.9e-05] map[node:map[boundingRect:map[bottom:319 height:30 left:47 right:47 top:289 width:0] lhId:page-8-::after nodeLabel:div.owl-item > div.slide > h2.h1 > ::after path:1,HTML,1,BODY,1,MAIN,1,SECTION,1,DIV,3,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,3,DIV,0,DIV,0,H2,0,::after selector:div.owl-item > div.slide > h2.h1 > ::after snippet:<::after> type:node] score:2.1e-05] map[node:map[boundingRect:map[bottom:319 height:30 left:47 right:47 top:289 width:0] lhId:page-8-::after nodeLabel:div.owl-item > div.slide > h2.h1 > ::after path:1,HTML,1,BODY,1,MAIN,1,SECTION,1,DIV,3,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,3,DIV,0,DIV,0,H2,0,::after selector:div.owl-item > div.slide > h2.h1 > ::after snippet:<::after> type:node] score:1.8e-05]]

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:27.319 source:map[column:16467 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-content/litespeed/js/4c909d09aae2653ff6d35f076456bf86.js?ver=6bf86 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:9.325 source:map[type:text value:[unattributed]]] map[reflowTime:19.331 source:map[column:50335 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-includes/js/jquery/jquery.min.js urlProvider:network]] map[reflowTime:0.217 source:map[column:50393 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-includes/js/jquery/jquery.min.js urlProvider:network]] map[reflowTime:0.137 source:map[column:50457 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-includes/js/jquery/jquery.min.js urlProvider:network]] map[reflowTime:1.178 source:map[column:16214 line:0 type:source-location url:https://cdn.activatedigital.co.uk/wp-content/litespeed/js/ed71eb1efa63b3cef85560edc270b80c.js?ver=0b80c urlProvider:network]] map[reflowTime:5.074 source:map[column:79427 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-includes/js/jquery/jquery.min.js urlProvider:network]] map[reflowTime:0.913 source:map[column:49615 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-includes/js/jquery/jquery.min.js urlProvider:network]] map[reflowTime:0.419 source:map[column:51395 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-includes/js/jquery/jquery.min.js urlProvider:network]] map[reflowTime:0.05 source:map[column:49637 line:1 type:source-location url:https://cdn.activatedigital.co.uk/wp-includes/js/jquery/jquery.min.js urlProvider:network]]]

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
div.owl-stage-outer > div.owl-stage > div.owl-item > img.owl-lazy `div.owl-stage-outer > div.owl-stage > div.owl-item > img.owl-lazy`	/wp-content/uploads/2025/01/sunday-treat-home-splash-min....	80.0 KiB	41.7 KiB
div.owl-stage-outer > div.owl-stage > div.owl-item > img.owl-lazy `div.owl-stage-outer > div.owl-stage > div.owl-item > img.owl-lazy`	/wp-content/uploads/2024/07/stage-security-home-splash-mi...	70.8 KiB	32.5 KiB
Hero-Connect-min `div.owl-stage-outer > div.owl-stage > div.owl-item > img.attachment-home-splash`	/wp-content/uploads/2021/08/Hero-Connect-min-768x316.jpg....	39.3 KiB	25.4 KiB
mockup-st-bolt-min `div.offset-xxxl-1 > div.row > div.d-block > img`	cdn.activatedigital.co.uk/wp-content/uploads/2025/12/mockup-st-bolt-min.png.webp	27.6 KiB	21.7 KiB
we-believe-min `div.owl-stage > div.owl-item > div.item > img`	cdn.activatedigital.co.uk/wp-content/uploads/2021/08/we-believe-min.jpg.webp	22.3 KiB	15.2 KiB
we-deliver-min `div.owl-stage > div.owl-item > div.item > img`	cdn.activatedigital.co.uk/wp-content/uploads/2021/08/we-deliver-min.jpg.webp	14.1 KiB	9.6 KiB
we-are-min `div.owl-stage > div.owl-item > div.item > img`	cdn.activatedigital.co.uk/wp-content/uploads/2021/08/we-are-min.jpg.webp	12.0 KiB	8.2 KiB

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

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: 987 ms

URL	Time Spent
www.activatedigital.co.uk/	987 ms
www.activatedigital.co.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.

Element	Layout shift score
Discover More Discover More Discover More We've helped CONNECT Aviation to tran… `section.splash > div.container > div.row > div.col-md-10`	0.119
Discover More Discover More Discover More We've helped CONNECT Aviation to tran… `section.splash > div.container > div.row > div.col-md-10`	0.013
div.owl-item > div.slide > h2.h1 > ::after `div.owl-item > div.slide > h2.h1 > ::after`	0.000
div.owl-item > div.slide > h2.h1 > ::after `div.owl-item > div.slide > h2.h1 > ::after`	0.000
div.owl-item > div.slide > h2.h1 > ::after `div.owl-item > div.slide > h2.h1 > ::after`	0.000
div.owl-item > div.slide > h2.h1 > ::after `div.owl-item > div.slide > h2.h1 > ::after`	0.000

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 32.6 KiB

URL	Transfer Size	Est Savings
cdn.activatedigital.co.uk/wp-content/themes/activate/dist/styles-dist/core.css	38.7 KiB	32.6 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.

Estimated savings: 330 ms 105.7 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-D1CFN3TWQR&cx=c&gtm=4e6562h1	177.6 KiB	71.6 KiB
connect.facebook.net/en_US/fbevents.js	97.0 KiB	34.1 KiB

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	969 ms
Other	649 ms
Style & Layout	331 ms
Script Parsing & Compilation	146 ms
Rendering	102 ms
Parse HTML & CSS	94 ms
Garbage Collection	19 ms

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 8 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 410 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 20 ms

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

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
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot `div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot`
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot `div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot`
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot `div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot`
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot `div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot`
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot `div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot`

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
Show More `div.block-wrap > div.block > div.inner > a.ts-small-button-tag`
Show More `div.block-wrap > div.block > div.inner > a.ts-small-button-tag`
Show More `div.block-wrap > div.block > div.inner > a.ts-small-button-tag`
Show More `div.block-wrap > div.block > div.inner > a.ts-small-button-tag`
Powered By Dribbble `div.row > div.content-col > div.powered-by > p.mb-0`
Interest `div.navbar-nav-scroll > ul.navbar-nav > li.nav-item > a#funnel1MobLink`
Action `div.navbar-nav-scroll > ul.navbar-nav > li.nav-item > a#funnel2MobLink`
Services `div.menu-footer-container > ul#menu-footer > li#menu-item-1639 > a`
Our Work `div.menu-footer-container > ul#menu-footer > li#menu-item-1637 > a`
Industries `div.menu-footer-container > ul#menu-footer > li#menu-item-1636 > a`
About Us `div.menu-footer-container > ul#menu-footer > li#menu-item-1633 > a`
Blog `div.menu-footer-container > ul#menu-footer > li#menu-item-1632 > a`
Enquire Now `div.menu-footer-container > ul#menu-footer > li#menu-item-1635 > a`

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
Talented Team of Experts `div.block-wrap > div.block > div.inner > h3.h6`
Reaching Your Audience `div.left > div.inbox > div#funnel0Content > h6`

These are opportunities to improve keyboard navigation in your application.

○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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

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

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 / Warning	Source
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 1126

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

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`