Website review, no card needed

medscope.co.uk logo

medscope.co.uk website review

Visit site (opens in a new tab)Reviewed 11 November 202625 issues · 76 checks

This review found 25 issues worth fixing on medscope.co.uk, 6 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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.4 s1.1 sMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
115 ms91 msMay 23Nov 7110 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202694 ms
May 30, 202694 ms
Jun 6, 202694 ms
Jun 13, 202695 ms
Jun 20, 2026103 ms
Jun 27, 2026108 ms
Jul 4, 2026111 ms
Jul 11, 2026106 ms
Jul 18, 2026111 ms
Jul 25, 2026105 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026101 ms
Aug 29, 2026103 ms
Sep 5, 2026104 ms
Sep 12, 202699 ms
Sep 19, 2026103 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 2026108 ms
Oct 17, 2026108 ms
Oct 24, 2026112 ms
Oct 31, 2026112 ms
Nov 7, 2026110 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 medscope.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. medscope.co.uk at 0.9 s0.9 s
  2. medscope.co.uk at 1.8 s1.8 s
  3. medscope.co.uk at 2.8 s2.8 s
  4. medscope.co.uk at 3.7 s3.7 s
  5. medscope.co.uk at 4.6 s4.6 s
  6. medscope.co.uk at 5.5 s5.5 s
  7. medscope.co.uk at 6.4 s6.4 s
  8. medscope.co.uk at 7.3 s7.3 s

Speed

7 to fix84
  • Render-blocking requests

    1.2 s

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

  • 4,004 HTML elements

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

  • Mobile performance score: 84

    84/100

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

  • Reduce unused JavaScript

    150 ms · 333 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and smile.io and others), adding 1.1 MB and 257 ms of main-thread time.

  • smile.io adds 47 ms

    47 ms

    smile.io costs a phone 47 ms of main-thread work and 359 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.

  • Shopify adds 48 ms

    48 ms

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

  • Minify JavaScript

    150 ms · 22 KiB

    22 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 5 KiB

    Polyfills for old browsers add 5 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    11 KiB

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

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

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 462 ms of it running JavaScript. That is comfortably low.

  • Server response: 48 ms

    48 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 8.8 s

    8.8 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 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-11-07, real Chrome visitors' tap response (inp) went from 94 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -6%

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

9 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.1 s

    1.1 s

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

  • Real-user INP: 112 ms

    112 ms

    Real visitors wait 112 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 402 ms

    402 ms

    Real visitors wait 402 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).

  • Total Blocking Time: 29 ms

    29 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 291 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 291 requests on a phone: other files 1.0 MB (136), scripts 978 KiB (84) and images 303 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9797
  • 12 text elements with low contrast

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

  • Alternative text of images should not be repeated as text (6 elements)

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 10087
  • Meta description is long (306 characters)

    Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 366 internal links, 1 external

    The homepage links to 366 pages on medscope.co.uk and 1 external page.

5 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Littmann Stethoscopes & Medical Supplies – Medscope”.

  • Canonical URL set

    The canonical URL is https://www.medscope.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://www.medscope.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,110 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix76
  • 2 pages share a title

    https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscopes and https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscope all use the title “Littmann Classic III Stethoscopes – Medscope”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.medscope.co.uk/collections/stethoscope-cases and https://www.medscope.co.uk/collections/3m-littmann-spare-parts-kits have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscopes and https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscope use the same meta description. A description written for each page earns more clicks.

  • 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.medscope.co.uk/collections/littmann-classic-iii-stethoscopes, whose canonical is https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscope. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages without an H1

    https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscopes, https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscope, https://www.medscope.co.uk/collections/3m-littmann-cardiology-iv-stethoscope, https://www.medscope.co.uk/collections/littmann-core-stethoscope, https://www.medscope.co.uk/collections/3mtm-littmannr-master-cardiology-stethoscope and https://www.medscope.co.uk/collections/3mtm-littmannr-lightweight-ii-s-e-stethoscope and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscopes, https://www.medscope.co.uk/collections/littmann-classic-iii-stethoscope, https://www.medscope.co.uk/collections/3m-littmann-cardiology-iv-stethoscope, https://www.medscope.co.uk/collections/littmann-core-stethoscope, https://www.medscope.co.uk/collections/stethoscope-cases and https://www.medscope.co.uk/collections/3m-littmann-spare-parts-kits and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 340 words of copy

    The homepage carries about 340 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Classic III”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop By Profession”, “Shop Classic III” and “Shop CORE”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

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, Meta Pixel and Microsoft Ads 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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 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.

  • 24 other companies contacted

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

Apps your storefront loads

Analyzify Ga4 Ads Tracking · Flair · 56071677a62720b5cde4241477474f626e61c35a · Checkout Rules · Pify Order Purchase Limit · archivepro.io · smile.io

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
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on medscope.co.uk, including 11 speed issues, 3 SEO issues 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