Website review, no card needed

pharmacytimes.com logo

pharmacytimes.com website review

Visit site (opens in a new tab)Reviewed 17 November 202619 issues · 64 checks

This review found 19 issues worth fixing on pharmacytimes.com, 5 of them high impact, across 64 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
4.3 s1.7 sMay 30Nov 143.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.9 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20263.9 s
Jun 27, 20263.8 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.8 s
Aug 1, 20264.0 s
Aug 8, 20264.0 s
Aug 15, 20263.9 s
Aug 22, 20263.8 s
Aug 29, 20263.6 s
Sep 5, 20263.5 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20262.3 s
Oct 17, 20262.2 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Nov 7, 20262.6 s
Nov 14, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
131 ms92 msMay 30Nov 14111 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202696 ms
Jun 6, 2026102 ms
Jun 13, 2026103 ms
Jun 20, 2026105 ms
Jun 27, 2026107 ms
Jul 4, 2026109 ms
Jul 11, 2026112 ms
Jul 18, 2026114 ms
Jul 25, 2026115 ms
Aug 1, 2026119 ms
Aug 8, 2026119 ms
Aug 15, 2026118 ms
Aug 22, 2026118 ms
Aug 29, 2026116 ms
Sep 5, 2026116 ms
Sep 12, 2026119 ms
Sep 19, 2026120 ms
Sep 26, 2026123 ms
Oct 3, 2026126 ms
Oct 10, 2026108 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Oct 31, 2026104 ms
Nov 7, 2026105 ms
Nov 14, 2026111 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

3 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Tap response (INP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user INP: 111 ms

    111 ms

    Real visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 509 ms

    509 ms

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

  • Largest content (LCP) got 28% faster for real visitors

    -28%

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB

    2.7 MB

    Your homepage downloads 2.7 MB on a phone, 800 KiB of it images (29%). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (369 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.8 g of CO₂ per visit

    0.77 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fix91
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 10 text elements with low contrast

    10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

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

  • 16 links without text

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

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 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.

2 checks passed
  • Every image has alt text

    All 84 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

100
  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 275 internal links, 48 external

    The homepage links to 275 pages on pharmacytimes.com and 48 external pages.

8 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Pharmacy Times offers the latest news and insights for the pharmacy professional and solutions that impact the everyday…”.

  • One H1 headline

    Your main headline reads: “Latest News”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Pharmacy Times – Pharmacy Practice News and Expert Insights”.

  • Canonical URL set

    The canonical URL is https://www.pharmacytimes.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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.pharmacytimes.com/sitemap.xml.

AI search readiness

100
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, sameAs (social profiles), description and contact details; url and logo would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,188 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.pharmacytimes.com/llms.txt (8 KiB, 46 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.pharmacytimes.com/latest-conference and https://www.pharmacytimes.com/conference all use the title “Conference | Pharmacy Times”. 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://www.pharmacytimes.com/latest-conference and https://www.pharmacytimes.com/conference use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.pharmacytimes.com/watch and https://www.pharmacytimes.com/sponsored-webcast have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fix93
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

2 checks passed
  • Tap targets are thumb-sized

    82 of 85 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,937 words of copy

    The homepage carries about 1,937 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Subscribe” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Segment.

Privacy and tracking

  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 4 of them by other companies (measured from a US location before any click).

  • 42 other companies contacted

    Loading the homepage contacts 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 pharmacytimes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Astro
Analytics
Google Tag Manager | Segment
Hosting
Vercel

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on pharmacytimes.com, including 3 speed 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