robertsradio.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and gd-commerce-services.net and others), adding 3.6 MB and 2.7 s of main-thread time.

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

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

Your mobile performance score is 52 (desktop: 60). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 801 ms of main-thread work and 931 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.

3 images could be 547 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.

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

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

Google CDN costs a phone 385 ms of main-thread work and 734 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.

gd-commerce-services.net costs a phone 331 ms of main-thread work and 659 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.

Bazaarvoice costs a phone 306 ms of main-thread work and 410 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.

squeezely.tech costs a phone 297 ms of main-thread work and 210 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.

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

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

Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB JavaScript is shipped twice across bundles.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 286 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Revere”.

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

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

Your homepage downloads 5.4 MB in 157 requests on a phone: scripts 3.6 MB (53), images 918 KiB (35) and other files 456 KiB (51). Under 2 MB keeps phones on slow connections fast.

1--card-2Pemdc6h.png weighs 529 KiB. On a phone connection a single image that size takes seconds.

2 images (575 KiB) 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.

1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

11 buttons have no accessible name, so screen readers announce just “button”.

Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

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

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

Some list items are not inside a list.

1 tap target is too small or too close together to hit reliably with a finger.

Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

All page content should be contained by landmarks: 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.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“Introducing Revere” and “British Audio Designed to Excite the Senses.”). One clear main headline is easier for people and search engines.

Structured data found (ElectronicsStore) but with 1 problem, for example “ElectronicsStore: url is not an absolute URL ("robertsradio.com")”.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 197 pages on robertsradio.com and 9 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://www.robertsradio.com/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://www.robertsradio.com/en-gb and https://www.robertsradio.com/en-gb/node/1 all use the title “Official Roberts Radio Online Shop | British Audio”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.robertsradio.com/en-gb/node/1, whose canonical is https://www.robertsradio.com/en-gb. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://display.ugc.bazaarvoice.com/static/robertsradio/main_site/294/13397/en_GB/styleshe…”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 21 cookies (measured from a US location before any click).

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