loros.co.uk website review

6 images could be 430 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.

4 third-party services load with your homepage (cloudflare.com, Fathom Analytics and org.uk and others), adding 171 KiB and 17 ms of main-thread time.

About 26 KiB of CSS is downloaded but never applied on this page.

About 24 KiB of JavaScript is downloaded but never used on this page.

10 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”. Most of its time is element render delay (1.3 s).

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

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

pics011-bw-159167.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).

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

1 button has no accessible name, so screen readers announce just “button”.

All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

The homepage links to 223 pages on loros.co.uk and 7 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.

There is no https://loros.co.uk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://loros.co.uk/about-loros/news, https://loros.co.uk/podcast, https://loros.co.uk/contact/faqs, https://loros.co.uk/contact/media-enquiries, https://loros.co.uk/about-loros/board-of-trustees and https://loros.co.uk/about-loros/annual-reports have no meta description, so Google writes the search snippet from whatever text it finds.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.cqc.org.uk/_dp/build/widget/cleanslate.css' from origin 'https://loros.co.uk' …”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 950 words of visible text.

Opening the homepage sets 2 cookies (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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.