toretark.uk website review

About 989 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

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

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

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

8 third-party services load with your homepage (Shopify, Klarna and seel.com and others), adding 1.7 MB and 442 ms of main-thread time.

Shopify costs a phone 251 ms of main-thread work and 1.1 MB 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.

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

23 images could be 225 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 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.

32 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

8 KiB could be saved by minifying CSS.

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

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

11 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

The layout shifts by 0.113 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.7 MB in 272 requests on a phone: scripts 1.7 MB (73), images 901 KiB (39) and other files 862 KiB (122). Under 2 MB keeps phones on slow connections fast.

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

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

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

4 images have no alt text, which hurts accessibility and image search.

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 11 characters: “toretark.uk”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Your Car Deserves A ‘SPA’”). One clear main headline is easier for people and search engines.

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

The homepage links to 61 pages on toretark.uk and 7 external pages.

https://toretark.uk/collections/all, https://toretark.uk/collections/curated, https://toretark.uk/collections/cleaning-kits, https://toretark.uk/collections/exterior, https://toretark.uk/collections/interior and https://toretark.uk/collections/hot-sale and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://toretark.uk/products/carceracot1 and https://toretark.uk/products/headlight-restoration have no <h1> headline, so visitors and search engines get no clear main topic.

https://toretark.uk/collections/curated, https://toretark.uk/collections/cleaning-kits, https://toretark.uk/collections/interior, https://toretark.uk/collections/hot-sale, https://toretark.uk/collections/summer-cleaning-campaign and https://toretark.uk/products/carceracot1 and 6 others took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'dispatchEvent')”.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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

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

Before a visitor clicks anything, the page loads Meta Pixel (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 12 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.