Website review, no card needed
united-drug.com website review
Visit site (opens in a new tab)Reviewed 12 November 202630 issues · 75 checks
This review found 30 issues worth fixing on united-drug.com, 12 of them high impact, across 75 checks. The most urgent: reduce unused JavaScript. 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
77C- #65,132 of 115,917 reviewed websitesbeats 39%
- #42,843 of 66,651 online storesbeats 31%
- #40,830 of 60,853 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 122 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 127 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 116 ms |
| Jul 11, 2026 | 116 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 135 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 106 ms |
| Oct 3, 2026 | 111 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 118 ms |
| Oct 31, 2026 | 118 ms |
| Nov 7, 2026 | 121 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
Reduce unused JavaScript
1.6 s · 318 KiBAbout 318 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.4 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and Shopify and others), adding 3.6 MB and 323 ms of main-thread time.
Improve image delivery
400 ms · 119 KiB6 images could be 119 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 78 KiB6 files are served with short cache lifetimes, so returning visitors download them again (78 KiB).
Shopify adds 22 ms
22 msShopify costs a phone 22 ms of main-thread work and 3.1 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Legacy JavaScript
100 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.
Reduce unused CSS
30 KiBAbout 30 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
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 742 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 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.
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to offer various services, to con…”.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Speed Index: 6.3 s
6.3 sVisually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 122 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 553 ms
553 msReal visitors wait 553 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 11 ms
11 msScripts block the page for only 11 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.8 MB in 198 requests
8.8 MBYour homepage downloads 8.8 MB in 198 requests on a phone: media 6.6 MB (1), scripts 769 KiB (61) and other files 682 KiB (81). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (113 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.
4 images below the first screen load straight away
4 images further down the page (197 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.5 g of CO₂ per visit
2.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.50 g of CO₂e: 299.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Interactive controls must not be nested (26 elements)
Interactive controls must not be nested: 26 elements on the page fail this check, rated serious by axe-core.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
47 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: 47 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “United Drug | Ireland’s largest pharmaceutical distribution company.”.
4 H1 headlines
There are 4 <h1> headlines (“”, “” and “United, we do better”). One clear main headline is easier for people and search engines.
Meta description is long (296 characters)
Your meta description is 296 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("/")”.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
102 internal links, 10 external
The homepage links to 102 pages on united-drug.com and 10 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.united-drug.com/.
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://www.united-drug.com/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 (1,650 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.united-drug.com/llms.txt (6 KiB, 8 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 58 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
3 small tap targets
3 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 1,508 words of copy
The homepage carries about 1,508 words of visible text.
4 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Learn More” and “Learn more”.
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: 1 customer or partner logo and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
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 united-drug.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Headquarters
- Dublin
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 united-drug.com, including 15 speed issues, 6 SEO issues 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.