ttracing.uk website review

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

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

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

29 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Shopify, Clarity and cloudfront.net and others), adding 15.8 MB and 748 ms of main-thread time.

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

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

About 731 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 (377 KiB).

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

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

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

Polyfills for old browsers add 41 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 44.6 s. Good is under 3.8 s.

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Black Friday Monster Sale ends in 02d 09h 38m 00s.”. Most of its time is element render delay (1.4 s).

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

Your homepage downloads 27.9 MB in 723 requests on a phone: media 13.5 MB (2), images 10.8 MB (487) and scripts 1.5 MB (101). Under 2 MB keeps phones on slow connections fast.

DESK_POWER_PACK_-_UK.jpg 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).

6 images are downloaded at several times the size a phone draws them, for example certifications-transbg_1.png at 800 px wide, shown at 30 px. Resized copies would save about 392 KiB.

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

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

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

26 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 → 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).

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 436 pages on ttracing.uk and 16 external pages.

https://ttracing.uk/pages/bundle-sale-13, https://ttracing.uk/pages/bundle-sale-14 and https://ttracing.uk/pages/bundle-sale-15 have no meta description, so Google writes the search snippet from whatever text it finds.

https://ttracing.uk/pages/bundle-deals, https://ttracing.uk/pages/bt21-early-bird-registration, https://ttracing.uk/pages/bundle-sale-2, https://ttracing.uk/pages/bundle-sale-10, https://ttracing.uk/pages/bundle-sale-3 and https://ttracing.uk/pages/bundle-sale-13 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://ttracing.uk/pages/bundle-sale-3, https://ttracing.uk/pages/bundle-sale-15 and https://ttracing.uk/pages/bundle-sale-5 took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (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 6 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.