pharmaca.com website review

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

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

About 191 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 480 ms faster on a phone.

8 third-party services load with your homepage (dynatrace.com, Google Tag Manager and Adobe Tag Manager and others), adding 1.3 MB and 1.3 s of main-thread time.

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

27 images could be 637 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

dynatrace.com costs a phone 603 ms of main-thread work and 132 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.

The page has 2,545 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Polyfills for old browsers add 69 KiB JavaScript that modern phones do not need.

29 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

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

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

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

Your 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 text “Get vaccinated and earn $15 Walgreens Cash or more* in rewa…”. Most of its time is element render delay (2.3 s).

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

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

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

22 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 5.5 MB in 246 requests on a phone: scripts 2.9 MB (76), images 1.3 MB (77) and other files 820 KiB (76). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example 20261101_HP_Photo_Image_Card2_3up.jpg at 672 px wide, shown at 175 px. Resized copies would save about 115 KiB.

7 images further down the page (336 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images (202 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.

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

Certain ARIA roles must be contained by particular parents: 46 elements on the page fail this check, rated critical by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (4 elements).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

4 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 190 pages on pharmaca.com and 34 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.walgreens.com/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.

https://www.walgreens.com/rx-druginfo/pharmacy/finddrug/druginfosearch has no <title>, so Google invents the link text in results.

https://www.walgreens.com/store/c/productlist/N=20007975 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.walgreens.com/youraccount/default.jsp, https://www.walgreens.com/rx-refillhub/refillhub-holistic, https://www.walgreens.com/immunizationservice/pharmacy/immunization/ViewImmunizeHistory.jsp, https://www.walgreens.com/youraccount/dlorder/reorder.jsp, https://www.walgreens.com/pharmacy/fulfillment/rx-landing and https://www.walgreens.com/rx-status and 3 others all use the title “Sign In or Register to Get Started Using Walgreens.com”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.walgreens.com/youraccount/default.jsp, https://www.walgreens.com/rx-refillhub/refillhub-holistic, https://www.walgreens.com/immunizationservice/pharmacy/immunization/ViewImmunizeHistory.jsp, https://www.walgreens.com/orderhistory/orders-ui, https://www.walgreens.com/youraccount/dlorder/reorder.jsp and https://www.walgreens.com/pharmacy/fulfillment/rx-landing and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.walgreens.com/store/c/productlist/N=20007835, whose canonical is https://www.walgreens.com/store/c/productlist/N=20007835-tier3. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.walgreens.com/findcare/schedule-vaccine, https://www.walgreens.com/youraccount/default.jsp, https://www.walgreens.com/rx-refillhub/refillhub-holistic, https://www.walgreens.com/immunizationservice/pharmacy/immunization/ViewImmunizeHistory.jsp, https://www.walgreens.com/orderhistory/orders-ui and https://www.walgreens.com/youraccount/dlorder/reorder.jsp and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.walgreens.com/youraccount/default.jsp, https://www.walgreens.com/rx-refillhub/refillhub-holistic, https://www.walgreens.com/immunizationservice/pharmacy/immunization/ViewImmunizeHistory.jsp, https://www.walgreens.com/youraccount/dlorder/reorder.jsp, https://www.walgreens.com/pharmacy/fulfillment/rx-landing and https://www.walgreens.com/rx-status and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 500 ()”.

Requests the geolocation permission on page load.

1 image is served at too low a resolution for sharp phone screens.

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

Large scripts ship without source maps.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 852 words of visible text.

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

Opening the homepage sets 35 cookies (measured from a US location before any click).

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