Website review, no card needed
tfsdirect.co.uk website review
Visit site (opens in a new tab)Reviewed 22 October 202648 issues · 98 checks
This review found 48 issues worth fixing on tfsdirect.co.uk, 19 of them high impact, across 98 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #87,545 of 125,493 reviewed websitesbeats 26%
- #54,777 of 70,189 online storesbeats 18%
- #323 of 728 Magento storesbeats 51%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 141 ms |
| May 9, 2026 | 133 ms |
| May 16, 2026 | 129 ms |
| May 23, 2026 | 134 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 132 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 132 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 127 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 136 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 140 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 136 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.8 s
Speed
Use efficient cache lifetimes
9.5 s · 38.5 MB345 files are served with short cache lifetimes, so returning visitors download them again (38.5 MB).
Improve image delivery
18.5 s · 7.5 MB34 images could be 7.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 18.5 s faster on a phone.
Reduce unused CSS
1.1 s · 181 KiBAbout 181 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.0 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 62). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.9 s
A phone's processor spends 7.9 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,255 HTML elements
The page has 5,255 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
740 ms · 348 KiBAbout 348 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 740 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and ksrndkehqnwntyxlhgto.com and others), adding 877 KiB and 824 ms of main-thread time.
Minify JavaScript
450 ms · 240 KiB240 KiB could be saved by minifying JavaScript.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Google Tag Manager adds 387 ms
387 msGoogle Tag Manager costs a phone 387 ms of main-thread work and 521 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Duplicated JavaScript
25 KiB25 KiB JavaScript is shipped twice across bundles.
Phones get a much slower page than desktops
Desktop scores 62 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 127 ms
127 msYour server sent the HTML in 127 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 29.2 s
29.2 sYour largest element takes 29.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “TFS_DIRECT_eCommerce_Store_Website_Banner_2_”.
Speed Index: 18.1 s
18.1 sVisually, the page fills in at 18.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 45.7 s
45.7 sThe page becomes fully interactive after 45.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.308
0.308The layout shifts by 0.308 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 360 ms
360 msScripts block taps and scrolling for 360 ms in total while the page loads. Good is under 200 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 141 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 47.0 MB in 424 requests
47.0 MBYour homepage downloads 47.0 MB in 424 requests on a phone: media 35.4 MB (13), images 9.1 MB (61) and scripts 1.7 MB (267). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
2.3 MB3 images are downloaded at several times the size a phone draws them, for example 2.png at 848 px wide, shown at 174 px. Resized copies would save about 2.3 MB.
12 images in older formats
12 images (4.6 MB) are 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.
6 images below the first screen load straight away
6 images further down the page (798 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 13.3 g of CO₂ per visit
13.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 13.33 g of CO₂e: 1599.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
29 buttons without a name
29 buttons have no accessible name, so screen readers announce just “button”.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Orphan list items
Some list items are not inside a list.
2 form fields without a label
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 (11 elements)
Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
ARIA role should be appropriate for the element (10 elements)
ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (10 elements)
Elements marked as presentational should be consistently ignored: 10 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 67 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 8 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
206 internal links, 22 external
The homepage links to 206 pages on tfsdirect.co.uk and 22 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Shop TFS Direct for quality gate hardware, gate locks, fencing, and access control. Trusted UK supplier with expert sup…”.
One H1 headline
Your main headline reads: “Popular Product Categories”.
Title: 57 characters
Your title is a healthy 57 characters: “TFS | TFS Direct | Gate Hardware | Gate Locks and Fencing”.
Canonical URL set
The canonical URL is https://www.tfsdirect.co.uk/.
Structured data in place
Structured data found: WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.tfsdirect.co.uk/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.tfsdirect.co.uk/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.
Opted out of AI training for 2 crawlers
robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,299 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://www.tfsdirect.co.uk/shop-by.html, https://www.tfsdirect.co.uk/shop-by/brands.html, https://www.tfsdirect.co.uk/shop-by/brands/gatemaster-gate-hardware.html, https://www.tfsdirect.co.uk/shop-by/brands/d-d-gate-hardware.html, https://www.tfsdirect.co.uk/shop-by/brands/codelocks-gate-hardare.html and https://www.tfsdirect.co.uk/shop-by/brands/exidor-gate-hardware.html and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.tfsdirect.co.uk/shop-by/spring-savings-sale.html, whose canonical is https://www.tfsdirect.co.uk/shop-by/special-offers.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
13 pages slow to respond
https://www.tfsdirect.co.uk/shop-by/spring-savings-sale.html, https://www.tfsdirect.co.uk/shop-by/brands/locinox.html, https://www.tfsdirect.co.uk/shop-by/brands/borg.html, https://www.tfsdirect.co.uk/shop-by/brands/squire.html, https://www.tfsdirect.co.uk/shop-by/brands/cais.html and https://www.tfsdirect.co.uk/shop-by/brands/gatemaster-gate-hardware.html and 7 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 153 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://www.tfsdirect.co.uk/.
30 small tap targets
30 of 105 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “document.addEventListener(...) is not a function”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,305 words of copy
The homepage carries about 1,305 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop today's special offers” and “Apply Now”.
12 calls to action
The homepage has 12 calls to action, for example “Shop today's special offers”, “Shop By” and “Exclusive Trade Portal & Pricing”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
25 cookies set on arrival
25Opening the homepage sets 25 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tfsdirect.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- E-commerce
- Magento
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on tfsdirect.co.uk, including 24 speed issues, 1 SEO issue and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.