Website review, no card needed

tmlewin.co.uk logo

tmlewin.co.uk website review

Visit site (opens in a new tab)Reviewed 5 November 202630 issues · 77 checks

This review found 30 issues worth fixing on tmlewin.co.uk, 10 of them high impact, across 77 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
164 ms129 msMay 16Oct 31160 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026133 ms
May 23, 2026134 ms
May 30, 2026138 ms
Jun 6, 2026144 ms
Jun 13, 2026145 ms
Jun 20, 2026146 ms
Jun 27, 2026146 ms
Jul 4, 2026149 ms
Jul 11, 2026152 ms
Jul 18, 2026153 ms
Jul 25, 2026154 ms
Aug 1, 2026155 ms
Aug 8, 2026157 ms
Aug 15, 2026160 ms
Aug 22, 2026160 ms
Aug 29, 2026157 ms
Sep 5, 2026156 ms
Sep 12, 2026155 ms
Sep 19, 2026154 ms
Sep 26, 2026153 ms
Oct 3, 2026147 ms
Oct 10, 2026150 ms
Oct 17, 2026153 ms
Oct 24, 2026156 ms
Oct 31, 2026160 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

Full-page screenshot of tmlewin.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tmlewin.co.uk at 0.4 s0.4 s
  2. tmlewin.co.uk at 0.8 s0.8 s
  3. tmlewin.co.uk at 1.1 s1.1 s
  4. tmlewin.co.uk at 1.5 s1.5 s
  5. tmlewin.co.uk at 1.9 s1.9 s
  6. tmlewin.co.uk at 2.3 s2.3 s
  7. tmlewin.co.uk at 2.6 s2.6 s
  8. tmlewin.co.uk at 3.0 s3.0 s

Speed

8 to fix63
  • Improve image delivery

    3.6 s · 1.0 MB

    11 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

  • 5,789 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, ContentSquare and Google Tag Manager and others), adding 2.5 MB and 777 ms of main-thread time.

  • Mobile performance score: 63

    63/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused JavaScript

    683 KiB

    About 683 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.8 s

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

  • Shopify adds 206 ms

    206 ms

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

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    88 KiB

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

  • Legacy JavaScript

    30 KiB

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

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    11 KiB

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

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

1 checks passed
  • Server response: 13 ms

    13 ms

    Your server sent the HTML in 13 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • 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.

  • Time to Interactive: 25.2 s

    25.2 s

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

  • Largest Contentful Paint: 9.0 s

    9.0 s

    Your largest element takes 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A man wearing a navy blue suit”.

  • Speed Index: 9.1 s

    9.1 s

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

  • Real-user INP: 221 ms

    221 ms

    Real visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 4 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

7 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

    Real visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 359 ms

    359 ms

    Real visitors wait 359 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Total Blocking Time: 176 ms

    176 ms

    Scripts block the page for only 176 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

3 to fix43
  • Page weight: 4.6 MB in 387 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 387 requests on a phone: scripts 1.7 MB (102), images 1.3 MB (18) and other files 1.3 MB (231). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    496 KiB

    4 images are downloaded at several times the size a phone draws them, for example homepage__category__image--suits.png at 1,795 px wide, shown at 370 px. Resized copies would save about 496 KiB.

  • 5 images below the first screen load straight away

    5 images further down the page (866 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.31 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

1 to fixGoogle 10098
  • 132 links without text

    132 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 29 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • One H1 headline

    Your <h1> is empty.

  • 347 internal links, 10 external

    The homepage links to 347 pages on tmlewin.co.uk and 10 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Refresh your workwear with T.M.Lewin. For ultimate style, fit and comfort discover our range of expertly tailored shirt…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “T.M.Lewin | Shop Online Men’s Shirts, Suits & Accessories”.

  • Canonical URL set

    The canonical URL is https://tmlewin.co.uk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://tmlewin.co.uk/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,163 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://tmlewin.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 pages share a title

    https://tmlewin.co.uk/collections/mens-casual-shirts and https://tmlewin.co.uk/collections/mens-overshirts all use the title “Men's Smart Casual Shirts | T.M.Lewin”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://tmlewin.co.uk/collections/new-in, https://tmlewin.co.uk/collections/mens-new-shirts-copy, https://tmlewin.co.uk/collections/2-for-120-knitwear, https://tmlewin.co.uk/collections/2-for-80-knitwear, https://tmlewin.co.uk/collections/mens-new-knitwear-copy and https://tmlewin.co.uk/collections/2-for-80 and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://tmlewin.co.uk/collections/mens-casual-shirts and https://tmlewin.co.uk/collections/mens-overshirts use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://tmlewin.co.uk/collections/new-in, https://tmlewin.co.uk/collections/mens-new-shirts, https://tmlewin.co.uk/collections/mens-new-shirts-copy, https://tmlewin.co.uk/collections/mens-formal-shirts, https://tmlewin.co.uk/collections/mens-casual-shirts and https://tmlewin.co.uk/collections/2-for-120-knitwear and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://tmlewin.co.uk/collections/mens-formal-shirts has 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=97120502&Ver=2&mid=2054625e-e3ee-4bce-b21f-38a4358c6ad7&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=T.M.Lewin%20%7C%20Shop%20Online%20Men%E2%80%99s%20Shirt.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “%cDiscount Ninja - Gift not found. Error message: 'Offer XZJ14 is disabled because it has a gift that could not be foun…”.

2 checks passed
  • Tap targets are thumb-sized

    153 of 153 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • 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 568 words of copy

    The homepage carries about 568 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop shirts” and “Shop workwear”.

  • 24 calls to action

    The homepage has 24 calls to action, for example “Shop All New In”, “Shop all 20% off 2+” and “Shop all Shirts”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 1 more (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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 49 other companies contacted

    Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 tmlewin.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blotout Edgetag · Consentmo Gdpr · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Gorgias Live Chat Helpdesk · Contentsquare Analytics · Triplewhale · Forms · Gdpr Backpack · global-e.com · 9gtb.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Hosting
Shopify

Company

Founded
1898
Headquarters
London

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on tmlewin.co.uk, including 15 speed issues, 1 SEO issue and 3 conversion gaps. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25