Website review, no card needed
mediworld.co.uk website review
Visit site (opens in a new tab)Reviewed 24 October 202628 issues · 82 checks
This review found 28 issues worth fixing on mediworld.co.uk, 6 of them high impact, across 82 checks. The most urgent: 6,278 HTML elements. 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
87B- #8,084 of 116,487 reviewed websitesbeats 90%
- #4,750 of 66,776 online storesbeats 89%
- #4,609 of 60,929 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 167 ms |
| May 9, 2026 | 165 ms |
| May 16, 2026 | 162 ms |
| May 23, 2026 | 165 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 159 ms |
| Jun 13, 2026 | 159 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 149 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 158 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 171 ms |
| Oct 10, 2026 | 168 ms |
| Oct 17, 2026 | 169 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
6,278 HTML elements
The page has 6,278 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 176 KiBAbout 176 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 136 KiB14 files are served with short cache lifetimes, so returning visitors download them again (136 KiB).
Improve image delivery
300 ms · 50 KiB4 images could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
350 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, Google Tag Manager and Klaviyo and others), adding 705 KiB and 386 ms of main-thread time.
Minify JavaScript
150 ms · 4 KiB4 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 94 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.4 s
11.4 sThe page becomes fully interactive after 11.4 s. Good is under 3.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 167 ms to 169 ms 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: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 172 ms
172 msReal visitors wait 172 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.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 684 ms
684 msReal visitors wait 684 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 89 ms
89 msScripts block the page for only 89 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 323 requests
2.6 MBYour homepage downloads 2.6 MB in 323 requests on a phone: scripts 925 KiB (83), other files 902 KiB (168) and images 483 KiB (40). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
58 KiB1 image is downloaded at several times the size a phone draws it, for example Bank-of-America-Emblem_1.webp at 390 px wide, shown at 71 px. Resized copies would save about 58 KiB.
5 images in older formats
5 images (379 KiB) 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.
About 0.7 g of CO₂ per visit
0.73 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.73 g of CO₂e: 87.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 81 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, CollectionPage, ImageObject and Organization) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected property name or '}' in JSON at position 7 (line 3 )”.
970 internal links, 1 external
The homepage links to 970 pages on mediworld.co.uk and 1 external page.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Mediworld is a London based supplier of medical products including stethoscopes, thermometers, medical scrubs, hospital…”.
One H1 headline
Your main headline reads: “Shopping For An Organisation?”.
Title: 44 characters
Your title is a healthy 44 characters: “Mediworld Ltd: Medical Supplies Store London”.
Canonical URL set
The canonical URL is https://mediworld.co.uk/.
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://mediworld.co.uk/sitemap.xml.
AI search readiness
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 (3,029 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mediworld.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://mediworld.co.uk/pages/ordering-tracking is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://mediworld.co.uk/products/multicarein-cholesterol-triglycerides-and-glucose-copy and https://mediworld.co.uk/products/multicarein-cholesterol-triglycerides-and-glucose all use the title “MULTICAREIN (cholesterol, triglycerides & glucose)”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://mediworld.co.uk/products/multicarein-cholesterol-triglycerides-and-glucose-copy and https://mediworld.co.uk/products/multicarein-cholesterol-triglycerides-and-glucose use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://mediworld.co.uk/collections/bestsellers, https://mediworld.co.uk/products/multicarein-cholesterol-triglycerides-and-glucose-copy, https://mediworld.co.uk/products/professional-vaccine-carrier, https://mediworld.co.uk/products/multicarein-cholesterol-triglycerides-and-glucose, https://mediworld.co.uk/products/lumina-led-light-trolley and https://mediworld.co.uk/products/omron-m3-comfort-afib-blood-pressure-monitor and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://mediworld.co.uk/pages/about-us, https://mediworld.co.uk/pages/meet-the-team and https://mediworld.co.uk/pages/all-blogs 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 554 words of copy
The homepage carries about 554 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: “Buy Now” and “SHOP NOW”.
15 calls to action
The homepage has 15 calls to action, for example “Order Tracking”, “Contact Us” and “Non Contact Infrared Thermometers”.
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: 40 testimonial or review blocks and 5 customer or partner logos.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
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 mediworld.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
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 mediworld.co.uk, including 11 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.