Website review, no card needed
pearlchemistgroup.co.uk website review
Visit site (opens in a new tab)Reviewed 24 October 202630 issues · 76 checks
This review found 30 issues worth fixing on pearlchemistgroup.co.uk, 9 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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
85B- #16,642 of 124,013 reviewed websitesbeats 82%
- #10,472 of 69,747 online storesbeats 80%
- #35 of 725 Magento storesbeats 94%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.1 s |
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 113 ms |
| May 9, 2026 | 118 ms |
| May 16, 2026 | 124 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 129 ms |
| Jun 6, 2026 | 130 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 126 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 122 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 118 ms |
| Aug 22, 2026 | 115 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 119 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 122 ms |
| Sep 26, 2026 | 122 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 125 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.5 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 66). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused JavaScript
497 KiBAbout 497 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 60 KiBAbout 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,627 HTML elements
The page has 1,627 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 110 ms
110 msGoogle CDN costs a phone 110 ms of main-thread work and 306 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.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 746 KiB and 392 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
34 KiB2 files are served with short cache lifetimes, so returning visitors download them again (34 KiB).
Improve image delivery
6 KiB1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 835 ms of it running JavaScript. That is comfortably low.
Server response: 225 ms
225 msYour server sent the HTML in 225 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.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Multivitamins and supplements available at Pearl Chemist Gr…”. Most of its time is resource load delay (3.2 s).
Time to Interactive: 8.5 s
8.5 sThe page becomes fully interactive after 8.5 s. Good is under 3.8 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.117
0.117The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 213 ms
213 msScripts block taps and scrolling for 213 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 113 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Images and page weight
An image on the first screen is lazy-loaded
new-PharmacyFirst.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 52.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.5 MB in 54 requests
1.5 MBYour homepage downloads 1.5 MB in 54 requests on a phone: scripts 708 KiB (10), images 530 KiB (25) and HTML 135 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 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: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
215 internal links, 16 external
The homepage links to 215 pages on pearlchemistgroup.co.uk and 16 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Explore a wide range of health and wellness products at Pearl Chemist Group. From medicines to skincare, find everythin…”.
Title: 63 characters
Your title is a healthy 63 characters: “Online Pharmacy & Healthcare Store | Buy Medicines & Essentials”.
Canonical URL set
The canonical URL is https://www.pearlchemistgroup.co.uk/.
Structured data in place
Structured data found: MedicalOrganization, Organization, Pharmacy 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.pearlchemistgroup.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (845 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.pearlchemistgroup.co.uk/llms.txt (9 KiB, 65 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 168 found) and read each the way a search engine does.
1 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “require is not defined”.
2 checks passed
Tap targets are thumb-sized
35 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 350 words of copy
The homepage carries about 350 words of visible text.
5 checks passed
11 calls to action
The homepage has 11 calls to action, for example “No, I want to register a new account”, “Shop” and “Book an Appointment”.
14 short forms
14 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks, 1 customer or partner logo and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
11 other companies contacted
Loading the homepage contacts 11 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 pearlchemistgroup.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
- Tailwind CSS
- E-commerce
- Magento
- Analytics
- Google Analytics | Google Tag Manager
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 pearlchemistgroup.co.uk, including 15 speed issues, 2 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.