rcgeeks.co.uk website review

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

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

8 third-party services load with your homepage (Shopify, naviplus.app and Klaviyo and others), adding 1.8 MB and 941 ms of main-thread time.

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

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

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

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

Shopify costs a phone 505 ms of main-thread work and 352 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.

About 105 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.

naviplus.app costs a phone 155 ms of main-thread work and 526 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.

Klaviyo costs a phone 92 ms of main-thread work and 312 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.

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

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

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

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

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LIMITED EDITION KEVIN TALBOT MT banner image”.

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

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

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

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

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

11 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.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.8 MB in 493 requests on a phone: images 1.6 MB (85), other files 1.5 MB (284) and scripts 1.4 MB (90). Under 2 MB keeps phones on slow connections fast.

Untitled_design_15.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).

3 images (244 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.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 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: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (30 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found (HobbyShop, Organization, Store and WebSite) but with 2 problems, for example “Organization: url points at a different host (https://www.rcgeeks.co.uk)”.

The homepage links to 177 pages on rcgeeks.co.uk and 6 external pages.

https://www.rcgeeks.com/products/rcg-racing-1-10-brushed-monster-truck-red declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://www.rcgeeks.com/?shpxid=382dc25c-f0a5-4fba-83b0-91e340341f72 and https://www.rcgeeks.com/products/rcg-racing-1-10-brushed-monster-truck-red all use the title “RC Geeks® | Remote Control Cars, Planes & Helicopters”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rcgeeks.com/pages/support-centre, https://www.rcgeeks.com/collections/rcg-racing-18-series-off-road-rc-cars, https://www.rcgeeks.com/collections/micro-drift-cars, https://www.rcgeeks.com/products/rcg-racing-1-10-brushed-monster-truck-red, https://www.rcgeeks.com/collections/drift-cars and https://www.rcgeeks.com/collections/off-road-cars and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.rcgeeks.com/pages/support-centre has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

6 errors were logged to the browser console while the page loaded, for example “Framing 'https://widget.reviews.co.uk/' violates the following report-only Content Security Policy directive: "frame-an…”.

Chrome logged issues while loading the page (“Content security policy”).

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 383 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 22 cookies, 6 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 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.