Website review, no card needed

mccartans.ie logo

mccartans.ie website review

Visit site (opens in a new tab)Reviewed 21 October 202638 issues · 85 checks

This review found 38 issues worth fixing on mccartans.ie, 9 of them high impact, across 85 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 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
146 ms110 msMay 2Oct 17114 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026129 ms
May 9, 2026126 ms
May 16, 2026121 ms
May 23, 2026124 ms
May 30, 2026120 ms
Jun 6, 2026129 ms
Jun 13, 2026140 ms
Jun 20, 2026142 ms
Jun 27, 2026140 ms
Jul 4, 2026136 ms
Jul 11, 2026121 ms
Jul 18, 2026121 ms
Jul 25, 2026123 ms
Aug 1, 2026120 ms
Aug 8, 2026124 ms
Aug 15, 2026121 ms
Aug 22, 2026120 ms
Aug 29, 2026121 ms
Sep 5, 2026118 ms
Sep 12, 2026116 ms
Sep 19, 2026114 ms
Sep 26, 2026114 ms
Oct 3, 2026117 ms
Oct 10, 2026116 ms
Oct 17, 2026114 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 mccartans.ie (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mccartans.ie at 0.4 s0.4 s
  2. mccartans.ie at 0.8 s0.8 s
  3. mccartans.ie at 1.1 s1.1 s
  4. mccartans.ie at 1.5 s1.5 s
  5. mccartans.ie at 1.9 s1.9 s
  6. mccartans.ie at 2.3 s2.3 s
  7. mccartans.ie at 2.6 s2.6 s
  8. mccartans.ie at 3.0 s3.0 s

Speed

11 to fix45
  • Render-blocking requests

    4.3 s

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

  • Use efficient cache lifetimes

    2.6 s · 681 KiB

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

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45 (desktop: 89). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused CSS

    600 ms · 185 KiB

    About 185 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (zapier.com, Facebook and userway.org and others), adding 1.6 MB and 617 ms of main-thread time.

  • Reduce unused JavaScript

    310 ms · 422 KiB

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

  • zapier.com adds 536 ms

    536 ms

    zapier.com costs a phone 536 ms of main-thread work and 1.4 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

    650 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).

  • Improve image delivery

    500 ms · 92 KiB

    3 images could be 92 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 279 ms. During a long task the page ignores taps.

  • Main-thread work: 2.6 s

    A phone's processor spends 2.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Legacy JavaScript

    150 ms · 11 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 89 but mobile only 45. 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 12.0 s

    12.0 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

    The first text or image appears after 6.5 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 17.9 s

    17.9 s

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

  • Speed Index: 8.1 s

    8.1 s

    Visually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 480 ms

    480 ms

    Scripts block taps and scrolling for 480 ms in total while the page loads. Good is under 200 ms.

  • Largest content (LCP) held steady for real visitors

    -1%

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

8 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.6 s

    1.6 s

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

  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 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: 1.2 s

    1.2 s

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

  • Real-user TTFB: 535 ms

    535 ms

    Real visitors wait 535 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 129 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 3.1 MB in 127 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 127 requests on a phone: scripts 1.6 MB (60), images 789 KiB (10) and fonts 373 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    187 KiB

    2 images are downloaded at several times the size a phone draws them, for example shutterstock_2466675569-2-scaled-1-2048x1366.jpg at 2,048 px wide, shown at 300 px. Resized copies would save about 187 KiB.

  • 4 images in older formats

    4 images (353 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.

  • 1 image below the first screen load straight away

    1 image further down the page (69 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

Accessibility

4 to fixGoogle 9596
  • 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.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 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

3 to fixGoogle 9286
  • Title is short (26 characters)

    Your title is only 26 characters: “McCartan’s Pharmacy | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Caring for the Community”, “Erectile Dysfunction” and “Common Conditions Services”). One clear main headline is easier for people and search engines.

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 76 internal links, 10 external

    The homepage links to 76 pages on mccartans.ie and 10 external pages.

6 checks passed
  • Meta description: 113 characters

    Your meta description is 113 characters: “McCartan’s Pharmacy is a proudly Irish, family-owned pharmacy group, providing trusted healthcare across Ireland.”.

  • Canonical URL set

    The canonical URL is https://www.mccartans.ie/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mccartans.ie/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.mccartans.ie/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 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 (879 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix64
  • 1 linked page is broken

    Your homepage links to https://www.mccartans.ie/request-refill, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a meta description

    https://www.mccartans.ie/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://www.mccartans.ie/common-conditions-consultation, https://www.mccartans.ie/emergency-hormonal-contraception-ehc, https://www.mccartans.ie/erectile-dysfunction-medication, https://www.mccartans.ie/seasonal-flu-and-covid-19-vaccinations, https://www.mccartans.ie/preventative-vaccination and https://www.mccartans.ie/pressure-monitoring use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://www.mccartans.ie/common-conditions-consultation, https://www.mccartans.ie/emergency-hormonal-contraception-ehc, https://www.mccartans.ie/erectile-dysfunction-medication, https://www.mccartans.ie/seasonal-flu-and-covid-19-vaccinations, https://www.mccartans.ie/preventative-vaccination and https://www.mccartans.ie/pressure-monitoring and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 4 small tap targets

    4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://ddh9ivxjtpf66.cloudfront.net/css/appointment_widget.css' from origin 'https://www.…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 206 words

    The homepage has only about 206 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a Vaccination / Consultation”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Book a Vaccination / Consultation”, “Order Online” and “Get In Touch”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 3 email links.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 mccartans.ie, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on mccartans.ie, including 16 speed issues, 3 SEO issues and 5 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