tfglondon.com website review

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, equalweb.com and jQuery CDN and others), adding 482 KiB and 893 ms of main-thread time.

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

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

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

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

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

About 21 KiB of CSS is downloaded but never applied on this page.

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

4 KiB could be saved by minifying CSS.

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Fashion, lifestyle and homeware”.

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

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

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

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

6 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 8.6 MB in 58 requests on a phone: media 6.6 MB (3), images 1,016 KiB (22) and scripts 475 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 7 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.

Your title is 91 characters, so Google will cut it off around 60: “TFG London - fashion retail group including Hobbs, Phase Eight and Whistles designer bran…”.

No XML sitemap at https://tfglondon.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 10 pages on tfglondon.com and 0 external pages.

There is no https://tfglondon.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://tfglondon.com/brands/inside-story.html, whose canonical is https://tfglondon.com/brands/damsel-in-a-dress.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://tfglondon.com/brands/phase-eight.html, https://tfglondon.com/brands/hobbs.html, https://tfglondon.com/brands/whistles.html, https://tfglondon.com/brands/inside-story.html and https://tfglondon.com/brands/white-stuff.html 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.

We fetched 5 pages linked from your homepage and read each the way a search engine does.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage has only about 116 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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