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
www.clickcease.com/monitor/stat.js	0.0 ms	44.0 KiB
cdn.mouseflow.com/projects/242d7e04-4250-4fe4-ab39-ea2d4358cad3.js	86400.0 s	52.0 KiB

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
/wp-content/litespeed/css/a6c7cb2be5809813c71f5f1586d2fb2...	20.3 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: 4.1 s

URL	Time Spent
pcpclaim-uk.co.uk/	4.1 s
pcpclaim-uk.co.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

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
Style & Layout	1.2 s
Script Evaluation	1.0 s
Other	615 ms
Rendering	226 ms
Script Parsing & Compilation	226 ms
Parse HTML & CSS	141 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 reason	Failure 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

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

URL	Transfer Size	Est Savings
/wp-content/litespeed/css/a6c7cb2be5809813c71f5f1586d2fb2...	20.2 KiB	16.1 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: 0.0 ms 213.0 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-2TCKQTQ3ZZ&cx=c&gtm=4e6562h1	174.8 KiB	69.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-KNK35TM	150.0 KiB	64.0 KiB
cdn.mouseflow.com/projects/242d7e04-4250-4fe4-ab39-ea2d4358cad3.js	51.3 KiB	40.6 KiB
www.clickcease.com/monitor/stat.js	43.3 KiB	38.8 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 887 KiB

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 13 long tasks found

●Avoid non-composited animations 14 animated elements found

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

●Network Requests

●Network Round Trip Times 190 ms

●Server Backend Latencies 80 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
High Interest Rates `div.col-lg-9 > div#v-pills-tabContent > div#v-pills-high-interest-rates > div#v-collapse-heading-high-interest-rates`
Unfair Commission Fees `div.col-lg-9 > div#v-pills-tabContent > div#v-pills-unfair-commission-fees > div#v-collapse-heading-unfair-commission-fees`
Lack of Affordability Checks `div.col-lg-9 > div#v-pills-tabContent > div#v-pills-lack-of-affordability-checks > div#v-collapse-heading-lack-of-affordability-checks`
Not Disclosing Relationships `div.col-lg-9 > div#v-pills-tabContent > div#v-pills-not-disclosing-relationships > div#v-collapse-heading-not-disclosing-relationships`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot`
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot `div.owl-wrap > div#newsCarousel > 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
CHECK NOW `div.container > div.row > div.content-col > a.cta`
CHECK NOW `div.point > div.content-col > div.in > a.cta`
car finance claims `div.in > p > a > strong`
CHECK NOW `div.point > div.content-col > div.in > a.cta`
confirmed `div.in > p > a > strong`
CHECK NOW `div.point > div.content-col > div.in > a.cta`
Unfair Commission Fees `div#v-pills-tabContent > div#v-pills-unfair-commission-fees > div#v-collapse-heading-unfair-commission-fees > a`
Lack of Affordability Checks `div#v-pills-tabContent > div#v-pills-lack-of-affordability-checks > div#v-collapse-heading-lack-of-affordability-checks > a`
Not Disclosing Relationships `div#v-pills-tabContent > div#v-pills-not-disclosing-relationships > div#v-collapse-heading-not-disclosing-relationships > a`
Check if you’re eligible to claim in minutes `section.missold > div.container > div.missold__ctawrap > h3.headline`
PCP Claim UK is a trading style of AM1 Claims Management Limited (AM1); this si… `div.container > div.footer__whitebox > div.footer__disclaimer > p`
AM1 Claims Management Limited uses Elmwood Law Limited (ELL) to fulfil claims s… `div.container > div.footer__whitebox > div.footer__disclaimer > p`
You can claim for free without using a claims management company by contacting … `div.container > div.footer__whitebox > div.footer__disclaimer > p`
For more information on the FCA's car finance investigation, click here. `div.container > div.footer__whitebox > div.footer__disclaimer > p`
AM1 Claims Management Limited does not charge customers for its free eligibilit… `div.container > div.footer__whitebox > div.footer__disclaimer > p`
AM1 Claims Management may refer your claim to a third party, such as a law firm… `div.container > div.footer__whitebox > div.footer__disclaimer > p`
*In successful cases, Elmwood Law Limited charges fees of 18% to 36% (including… `div.container > div.footer__whitebox > div.footer__disclaimer > p`

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
No Win, No Fee Read More `div.owl-item > div.usp > div.top > h3`
Can I claim on my own? `div.col-xl-8 > div.faq-loop > div.faq-card > h4.--header`
Early Mis-Selling And Ombudsman Limitations `div.col-md-10 > div.timeline > div.timeline-item > h5.my20`

These are opportunities to improve keyboard navigation in your application.

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
Read More `body.home > main.page-wrap > div.section-timeline > button.readmore-toggle`

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

●`button`, `link`, and `menuitem` elements have accessible names

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

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

○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

○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

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○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

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.fca.org.uk/consumers/car-finance-complaints	click here

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`