Website review, no card needed
phelans.ie website review
Visit site (opens in a new tab)Reviewed 24 October 202634 issues · 84 checks
This review found 34 issues worth fixing on phelans.ie, 10 of them high impact, across 84 checks. The most urgent: main-thread work: 6.5 s. 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,899 of 125,791 reviewed websitesbeats 82%
- #10,529 of 70,264 online storesbeats 80%
- #10,220 of 63,827 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 159 ms |
| May 9, 2026 | 157 ms |
| May 16, 2026 | 155 ms |
| May 23, 2026 | 157 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 159 ms |
| Jun 13, 2026 | 160 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 157 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 155 ms |
| Aug 8, 2026 | 157 ms |
| Aug 15, 2026 | 157 ms |
| Aug 22, 2026 | 156 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 169 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 157 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
Speed
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,251 HTML elements
The page has 4,251 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 Klaviyo and others), adding 2.5 MB and 1.6 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 78). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
765 KiBAbout 765 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
100 ms · 512 KiB15 images could be 512 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 202 KiB14 files are served with short cache lifetimes, so returning visitors download them again (202 KiB).
Google Tag Manager adds 444 ms
444 msGoogle Tag Manager costs a phone 444 ms of main-thread work and 513 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
450 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Shopify adds 339 ms
339 msShopify costs a phone 339 ms of main-thread work and 326 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.
Klaviyo adds 259 ms
259 msKlaviyo costs a phone 259 ms of main-thread work and 630 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.
rebuyengine.com adds 223 ms
223 msrebuyengine.com costs a phone 223 ms of main-thread work and 725 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 269 ms. During a long task the page ignores taps.
Reduce unused CSS
96 KiBAbout 96 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
62 KiBPolyfills for old browsers add 62 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 34 ms
34 msYour server sent the HTML in 34 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 27.3 s
27.3 sThe page becomes fully interactive after 27.3 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a wheelchair with a person sitting in the back”.
Total Blocking Time: 702 ms
702 msScripts block taps and scrolling for 702 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 159 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 173 ms
173 msReal visitors wait 173 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 401 ms
401 msReal visitors wait 401 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 352 requests
5.2 MBYour homepage downloads 5.2 MB in 352 requests on a phone: scripts 2.7 MB (136), images 1.0 MB (40) and other files 836 KiB (123). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Vaccine_-_Mobiule.jpg 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).
1 image far larger than shown
22 KiB1 image is downloaded at several times the size a phone draws it, for example icon_35_lx_1.png at 437 px wide, shown at 123 px. Resized copies would save about 22 KiB.
About 1.5 g of CO₂ per visit
1.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
18 links without text
18 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 120 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (88 characters)
Your title is 88 characters, so Google will cut it off around 60: “Phelans Pharmacy | Lifelong Mobility Ireland | Irish Pharmacy Online – Phelan's Pharmacy”.
Meta description is long (207 characters)
Your meta description is 207 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
291 internal links, 10 external
The homepage links to 291 pages on phelans.ie and 10 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://phelans.ie/.
Structured data in place
Structured data found: Organization and WebSite.
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://phelans.ie/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,320 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://phelans.ie/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://phelans.ie/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://phelans.ie/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://phelans.ie/customer_authentication/redirect, https://phelans.ie/collections/mobility-bestsellers, https://phelans.ie/collections/commodes-toilet-aids and https://phelans.ie/collections/personal-care have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://phelans.ie/customer_authentication/redirect and https://phelans.ie/pages/store-locator have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://phelans.ie/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 169 found) and read each the way a search engine does.
3 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.
Titles are unique
Every page we checked has its own title.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
112 of 131 tappable elements near the top are at least 24 px.
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 877 words of copy
The homepage carries about 877 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: “Book a Vaccine Flu, Shingles & Covid-19”.
27 calls to action
The homepage has 27 calls to action, for example “Need Expert Advice? Contact Us”, “Most Popular Mobility Products Shop Now” and “Winter Cold & Flu Remedies Shop Now”.
12 short forms
12 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
39 other companies contacted
Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 phelans.ie, 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
- 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 34 issues on phelans.ie, including 19 speed issues, 3 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.