tnuck.com website review

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

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

Signyfyd costs a phone 1.1 s of main-thread work and 257 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Shopify and others), adding 2.2 MB and 3.3 s of main-thread time.

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

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

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

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

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

Yotpo costs a phone 277 ms of main-thread work and 327 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 images could be 253 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 507 requests on a phone: scripts 3.9 MB (212), images 1.3 MB (62) and other files 1.2 MB (200). Under 2 MB keeps phones on slow connections fast.

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

Heading levels should only increase by one: 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.

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

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

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

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 536 pages on tnuck.com and 8 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.

https://tnuck.com/pages/about-us, https://tnuck.com/blogs/inspiration, https://tnuck.com/pages/sport, https://tnuck.com/pages/home and https://tnuck.com/pages/gents-kids have no meta description, so Google writes the search snippet from whatever text it finds.

https://tnuck.com/pages/about-us, https://tnuck.com/collections/ladies-new-arrivals, https://tnuck.com/blogs/inspiration, https://tnuck.com/collections/best-sellers-this-week, https://tnuck.com/collections/ladies-clothing and https://tnuck.com/collections/ladies-dresses and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://tnuck.com/collections/ladies-new-arrivals, https://tnuck.com/collections/best-sellers-this-week, https://tnuck.com/collections/ladies-clothing, https://tnuck.com/collections/ladies-dresses and https://tnuck.com/collections/ladies-shoes have 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.

https://tnuck.com/pages/about-us, https://tnuck.com/collections/ladies-new-arrivals, https://tnuck.com/blogs/inspiration, https://tnuck.com/collections/best-sellers-this-week, https://tnuck.com/collections/ladies-accessories and https://tnuck.com/collections/beauty and 1 other took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 1 trust badge. 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.

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

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