Website review, no card needed

medtree.co.uk logo

medtree.co.uk website review

Visit site (opens in a new tab)Reviewed 7 November 202628 issues · 78 checks

This review found 28 issues worth fixing on medtree.co.uk, 8 of them high impact, across 78 checks. The most urgent: google Tag Manager adds 1.1 s. 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.5 s1.3 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
152 ms98 msMay 16Oct 31141 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026104 ms
May 23, 2026106 ms
May 30, 2026111 ms
Jun 6, 2026117 ms
Jun 13, 2026123 ms
Jun 20, 2026127 ms
Jun 27, 2026127 ms
Jul 4, 2026123 ms
Jul 11, 2026121 ms
Jul 18, 2026120 ms
Jul 25, 2026120 ms
Aug 1, 2026120 ms
Aug 8, 2026123 ms
Aug 15, 2026122 ms
Aug 22, 2026121 ms
Aug 29, 2026121 ms
Sep 5, 2026118 ms
Sep 12, 2026116 ms
Sep 19, 2026116 ms
Sep 26, 2026120 ms
Oct 3, 2026129 ms
Oct 10, 2026139 ms
Oct 17, 2026145 ms
Oct 24, 2026146 ms
Oct 31, 2026141 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 medtree.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. medtree.co.uk at 0.9 s0.9 s
  2. medtree.co.uk at 1.8 s1.8 s
  3. medtree.co.uk at 2.6 s2.6 s
  4. medtree.co.uk at 3.5 s3.5 s
  5. medtree.co.uk at 4.4 s4.4 s
  6. medtree.co.uk at 5.3 s5.3 s
  7. medtree.co.uk at 6.1 s6.1 s
  8. medtree.co.uk at 7.0 s7.0 s

Speed

9 to fix54
  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 859 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.

  • Main-thread work: 9.3 s

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

  • 3,972 HTML elements

    The page has 3,972 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 (Google Tag Manager, Shopify and Clarity and others), adding 1.8 MB and 2.3 s of main-thread time.

  • Reduce unused JavaScript

    320 ms · 749 KiB

    About 749 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 320 ms faster on a phone.

  • Mobile performance score: 54

    54/100

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

  • Shopify adds 788 ms

    788 ms

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

  • Render-blocking requests

    650 ms

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

  • 20 long tasks on the main thread

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

  • Improve image delivery

    150 ms · 226 KiB

    10 images could be 226 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    224 KiB

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

  • Legacy JavaScript

    46 KiB

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

  • Reduce unused CSS

    24 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 21.2 s

    21.2 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Largest Contentful Paint: 4.4 s

    4.4 s

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

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

    +37%

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

  • Speed Index: 5.2 s

    5.2 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 147 ms

    147 ms

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

  • 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: 465 ms

    465 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.8 MB in 292 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 292 requests on a phone: scripts 1.9 MB (92), other files 934 KiB (119) and images 758 KiB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (45 KiB) is 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.

  • About 1.1 g of CO₂ per visit

    1.06 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

2 to fixGoogle 9798
  • 344 links without text

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

  • All page content should be contained by landmarks (10 elements)

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

2 checks passed
  • Every image has alt text

    All 390 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 694 internal links, 5 external

    The homepage links to 694 pages on medtree.co.uk and 5 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “We are the UK's leading distributor of a wide range of emergency medical products, medical equipment & first aid suppli…”.

  • One H1 headline

    Your main headline reads: “Buy Medical Equipment and Supplies UK”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Emergency Medical Supplies & Medical Equipment Store UK – MedTree”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://medtree.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 (1,525 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://medtree.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://medtree.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://medtree.co.uk/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://medtree.co.uk/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211064171&tm=gtm002&Ver=2&mid=c33eede0-9900-4ab1-a1f4-09be4e8c6efd&bo=1&sid=5080e2f0da5f11f1a28fc1b59b220269&vid=5080f6c0da5f11f184687dc1ee7e81b0&vids=1&msclkid=N&gtm_.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'email')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 1,051 words of copy

    The homepage carries about 1,051 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “Shop by Department”, “Shop by Products” and “Shop by Brand”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and LinkedIn Insight.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 2 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.

  • 33 cookies set on arrival

    33

    Opening the homepage sets 33 cookies, 1 of them by other companies (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.

  • 35 other companies contacted

    Loading the homepage contacts 35 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 medtree.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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Swatch King · Klaviyo Email Marketing Sms · Zepto Product Personalizer · Gdpr Cookie Consent · Variant Image Swatch · Stape Remix · Essential Post Purchase Upsell · Swym Wishlist Plus · trustpilot.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on medtree.co.uk, including 15 speed issues, 1 SEO issue and 2 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