Website review, no card needed
amerisourcebergen.com website review
Visit site (opens in a new tab)Reviewed 20 October 202630 issues · 63 checks
This review found 30 issues worth fixing on amerisourcebergen.com, 6 of them high impact, across 63 checks. The most urgent: fails Core Web Vitals for real visitors. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.7 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 173 ms |
| May 9, 2026 | 181 ms |
| May 16, 2026 | 184 ms |
| May 23, 2026 | 184 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 175 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 177 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 189 ms |
| Aug 29, 2026 | 183 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 160 ms |
| Sep 19, 2026 | 148 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 138 ms |
| Oct 17, 2026 | 132 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
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Optanon and jQuery CDN and others), adding 836 KiB and 1.2 s of main-thread time.
Google Tag Manager adds 953 ms
953 msGoogle Tag Manager costs a phone 953 ms of main-thread work and 560 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.
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 100). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused JavaScript
450 ms · 308 KiBAbout 308 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 416 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
300 ms · 70 KiB4 files are served with short cache lifetimes, so returning visitors download them again (70 KiB).
Reduce unused CSS
23 KiBAbout 23 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 100 but mobile only 70. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 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.
Time to Interactive: 8.0 s
8.0 sThe page becomes fully interactive after 8.0 s. Good is under 3.8 s.
Total Blocking Time: 657 ms
657 msScripts block taps and scrolling for 657 ms in total while the page loads. Good is under 200 ms.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 987 ms
987 msReal visitors wait 987 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are now Cencora. Our shared identity unites us. Cencora …”.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
7 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 131 ms
131 msReal visitors wait 131 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.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 173 ms to 132 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.0 s
3.0 sVisually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.04
0.04The layout barely moves while loading (CLS 0.04, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.25 g of CO₂e: 30.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 908 KiB in 34 requests
908 KiBYour homepage downloads 908 KiB in 34 requests on a phone: scripts 753 KiB (8), images 71 KiB (12) and other files 69 KiB (12). That is a lean page.
Accessibility
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
60 tap targets too small
60 tap targets are too small or too close together to hit reliably with a finger.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
8 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 11 WCAG 2.2 A/AA and best-practice rules on the phone render: 8 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “AmerisourceBergen | United in our responsibility to create healthier futures”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“We are now Cencora. Our shared identity unites us.”, “Marketplace gives pharmacies access to thousands …” and “Careers with purpose”). One clear main headline is easier for people and search engines.
No robots.txt
There is no robots.txt at amerisourcebergen.com/robots.txt, the first file search crawlers ask for.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
66 internal links, 37 external
The homepage links to 66 pages on amerisourcebergen.com and 37 external pages.
4 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “AmerisourceBergen fosters a positive impact on healthcare around the world by advancing the development and delivery of…”.
Canonical URL set
The canonical URL is https://www.amerisourcebergen.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://www.amerisourcebergen.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.amerisourcebergen.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.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
1 JavaScript error while loading
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 403 (Forbidden)”.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 3 words
The homepage has only about 3 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Contact us”, “Learn more” and “Data Subject Request”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 amerisourcebergen.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
- jQuery
- Analytics
- Google Tag Manager
Company
- Employees
- 44,000
- Founded
- 2001
- Headquarters
- Chesterbrook
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 amerisourcebergen.com, including 14 speed issues, 5 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.