Skip to content
https://tkpg.co.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.

63

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.

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
div.homehero__slide-image > a.stretched-link > picture > img.attachment-hero-home div.homehero__slide-image > a.stretched-link > picture > img.attachment-hero-home
/wp-content/uploads/2026/03/Berkeley-Square-Manchester-In...76.7 KiB65.7 KiB
Forum House St Albans London Investment (1) div.homehero__slide-image > a.stretched-link > picture > img.attachment-hero-home
/wp-content/uploads/2025/11/Forum-House-St-Albans-London-...66.7 KiB57.2 KiB
div.homehero__slide-image > a.stretched-link > picture > img.attachment-hero-home div.homehero__slide-image > a.stretched-link > picture > img.attachment-hero-home
/wp-content/uploads/2026/02/The-Quayline-Wirral-Waters-Li...55.3 KiB47.4 KiB
div.card-city__image > span > picture > img.attachment-card-city div.card-city__image > span > picture > img.attachment-card-city
tkpg.co.uk/wp-content/uploads/2025/10/manchester-570x380.jpg44.8 KiB28.4 KiB
Tranquillity Manchester Buy-To-Let Development div.propertycard__imagewrap > a > picture > img.propertycard__img
/wp-content/uploads/2025/10/External-_-Tranquillity-_-TKP...30.2 KiB9.3 KiB
Forum House TKPG div.propertycard__imagewrap > a > picture > img.propertycard__img
/wp-content/uploads/2025/10/External-_-Forum-House-_-TKPG...26.4 KiB5.5 KiB
Contour Manchester external night time div.propertycard__imagewrap > a > picture > img.propertycard__img
/wp-content/uploads/2026/05/Contour-Manchester-external-n...26.0 KiB5.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

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.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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: 450 ms 64.3 KiB
URLTransfer SizeEst Savings
/wp-content/litespeed/css/f88e3679ce972507bf9119682d98bf6...70.1 KiB64.3 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.

CategoryTime Spent
Script Evaluation910 ms
Other656 ms
Style & Layout620 ms
Parse HTML & CSS145 ms
Script Parsing & Compilation105 ms
Rendering91 ms
Garbage Collection38 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 WebSocket cannot enter back/forward cache.Pending browser support

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

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

Max Potential First Input Delay 120 ms
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,913 KiB
JavaScript execution time 0.7 s
Avoid long main-thread tasks 7 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 40 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
83

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.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot
div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot
div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot
div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot
div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot div.services__col--slides > div#services-owl-controls > div.owl-dots > button.owl-dot

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All Cities Birmingham Liverpool Manchester London Nottingham Blackpool Burton-u… div.properties__row > div.properties__formwrap > form#filterProperties > select#filterCity

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.owl-item > div.homehero__slide > div.homehero__slide-image > a.stretched-link div.owl-item > div.homehero__slide > div.homehero__slide-image > a.stretched-link
div.owl-item > div.homehero__slide > div.homehero__slide-image > a.stretched-link div.owl-item > div.homehero__slide > div.homehero__slide-image > a.stretched-link
div.owl-item > div.propertycard > div.propertycard__imagewrap > a div.owl-item > div.propertycard > div.propertycard__imagewrap > a
div.col-lg-4 > div.card-report > div.report-card-img-top > a.stretched-link div.col-lg-4 > div.card-report > div.report-card-img-top > a.stretched-link
div.col-lg-4 > div.card-report > div.report-card-img-top > a.stretched-link div.col-lg-4 > div.card-report > div.report-card-img-top > a.stretched-link
div.col-lg-4 > div.card-report > div.report-card-img-top > a.stretched-link div.col-lg-4 > div.card-report > div.report-card-img-top > a.stretched-link

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
Customise div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Reject All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Accept All div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn
Manchester's div.homehero__slide-inner > div > h2.homehero__title > span.text-gold
Our Portfolio main#main > section.properties > div.container > p.h4
Where To Invest div.container-xxxl > div.row > div.col > p.h4
Stay Up To Date div.container > div.row > div.col > p.h4
Our Services & Resources div.services__row > div.services__col--content > div.services__col__content__content > p.h4
The Best UK Property Developments div.container > div.row > div.col-lg-6 > p.h4
contact us div.row > div.col-lg-6 > p > 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
Units Sold div.content1__stats > div.content1__statcol > div.stat > h5.stat__label
Manchester Buy to Let Property Guide div.col-lg-4 > div.card-report > div.report-card-body > h5.card__title

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
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[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
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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
`[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
`<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.
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

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