ledex.co.uk website review

POWr costs a phone 1.7 s of main-thread work and 442 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

powrcdn.com costs a phone 1.2 s of main-thread work and 4.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

A phone's processor spends 10.6 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,861 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (POWr, powrcdn.com and Google Tag Manager and others), adding 6.9 MB and 3.6 s of main-thread time.

About 3.1 MB of JavaScript is downloaded but never used on this page.

74 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

23 images could be 662 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

About 181 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

20 long tasks block the main thread while loading, the longest for 433 ms. During a long task the page ignores taps.

Shopify costs a phone 245 ms of main-thread work and 1,009 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 277 ms of main-thread work and 355 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

10 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Visually, the page fills in at 15.8 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 57.2 s. Good is under 3.8 s.

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s.

Scripts block taps and scrolling for 800 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

13 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.9 MB in 619 requests on a phone: scripts 5.5 MB (243), images 1.9 MB (47) and stylesheets 1.4 MB (63). Under 2 MB keeps phones on slow connections fast.

16 images (1.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

led-streetlights-banner-ledex_800x.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example Become-a-Partner-footer-ledex-uk.webp at 1,827 px wide, shown at 370 px. Resized copies would save about 152 KiB.

2 images further down the page (323 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 3.10 g of CO₂e: 371.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA commands must have an accessible name: 13 elements on the page fail this check, rated serious by axe-core.

5 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

7 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

Your title is 70 characters, so Google will cut it off around 60: “High-Quality LED Lighting Solutions for Businesses | Ledex Lighting UK”.

Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 330 pages on ledex.co.uk and 2 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

We fetched 15 pages linked from your homepage (of 124 found) and read each the way a search engine does.

10 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

8 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“webkitRequestAnimationFrame is vendor-specific. Please use the standard requestAnimationFrame inste…”).

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'dataset')”.

Chrome logged issues while loading the page (“Cookie”).

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,346 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 14 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.