tarro.co.uk website review

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and appstle.com and others), adding 1.5 MB and 557 ms of main-thread time.

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

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

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

Klaviyo costs a phone 195 ms of main-thread work and 532 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 1,545 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

12 KiB could be saved by minifying JavaScript.

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

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

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

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

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

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.1 MB in 352 requests on a phone: scripts 1.5 MB (188), other files 825 KiB (128) and images 464 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 4f94fa8b-582e-45a3-9ffe-57affd3790b7.jpeg at 1,501 px wide, shown at 195 px. Resized copies would save about 167 KiB.

1 image (197 KiB) is 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.

3 images further down the page (68 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 0.87 g of CO₂e: 104.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious 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.

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

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 49 pages on tarro.co.uk and 16 external pages.

The HTML your server sends has 686 of the 1,438 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://tarro.co.uk/collections/accessories/gua-sha+facial-accessories+gua-sha-tool has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://tarro.co.uk/collections/accessories/gua-sha+facial-accessories+gua-sha-tool, whose canonical is https://tarro.co.uk/collections/accessories. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://tarro.co.uk/collections has no <h1> headline, so visitors and search engines get no clear main topic.

https://tarro.co.uk/collections/accessories/gua-sha+facial-accessories+gua-sha-tool took over 3 s to send its HTML from our server.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

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