Website review, no card needed

amerisource.us.com logo

amerisource.us.com website review

Visit site (opens in a new tab)Reviewed 22 October 202639 issues · 75 checks

This review found 39 issues worth fixing on amerisource.us.com, 11 of them high impact, across 75 checks. The most urgent: improve image delivery. 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

Full-page screenshot of amerisource.us.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix56
  • Improve image delivery

    9.2 s · 1.9 MB

    9 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.2 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56 (desktop: 75). Pages that score under 90 lose visitors before the first paint.

  • 6 third-party services on the page

    6 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads and others), adding 1.1 MB and 784 ms of main-thread time.

  • YouTube adds 767 ms

    767 ms

    YouTube costs a phone 767 ms of main-thread work and 991 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.

  • Use efficient cache lifetimes

    550 ms · 78 KiB

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

  • Reduce unused JavaScript

    508 KiB

    About 508 KiB of JavaScript is downloaded but never used on this page.

  • 8 long tasks on the main thread

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

  • Main-thread work: 2.7 s

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

  • Reduce unused CSS

    150 ms · 136 KiB

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

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Font display

    150 ms

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

  • 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: 22 ms

    22 ms

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

Core Web Vitals

5 to fix58
  • Largest Contentful Paint: 15.7 s

    15.7 s

    Your largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Financing America’s Fastest Growing Companies® Over $2 bill…”.

  • Time to Interactive: 17.2 s

    17.2 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Speed Index: 5.8 s

    5.8 s

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

  • Total Blocking Time: 354 ms

    354 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 90 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 90 requests on a phone: images 2.2 MB (18), scripts 995 KiB (26) and fonts 213 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    3 KiB

    3 images are downloaded at several times the size a phone draws them, for example KC-3MM-Trucking-768x419.jpg at 390 px wide, shown at 129 px. Resized copies would save about 3 KiB.

  • 4 images in older formats

    4 images (263 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 (66 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    1.04 g

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

Accessibility

7 to fixGoogle 9291
  • 5 tap targets too small

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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

6 to fixGoogle 9265
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Canonical points to another host

    Your canonical URL points to amerisourceus.azurewebsites.net, not amerisource.us.com, so Google may credit that host instead.

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https://amerisource.us.com/wp-content/uploads/2024/03/Amerisource-Business-Capita…”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at amerisource.us.com/robots.txt, the first file search crawlers ask for.

  • 33 internal links, 16 external

    The homepage links to 33 pages on amerisource.us.com and 16 external pages.

2 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “Home - Amerisource - Freedom to grow ®”.

  • XML sitemap found

    Your XML sitemap is reachable at https://amerisource.us.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://amerisource.us.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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading 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.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://amerisource.us.com/privacy-policy, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 8 pages without a meta description

    https://amerisource.us.com/investment-criteria, https://amerisource.us.com/transactions, https://amerisource.us.com/about-amerisource/history, https://amerisource.us.com/about-amerisource/teams, https://amerisource.us.com/about-amerisource/awards and https://amerisource.us.com/news and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://amerisource.us.com/investment-criteria, https://amerisource.us.com/transactions, https://amerisource.us.com/about-amerisource/history, https://amerisource.us.com/about-amerisource/awards, https://amerisource.us.com/news and https://amerisource.us.com/investment/amerisource-business-capital-closes-30-million-abl-facility-for-infrastructure-services-company and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://amerisource.us.com/investment-criteria, https://amerisource.us.com/transactions and https://amerisource.us.com/about-amerisource/awards 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.

  • 7 pages slow to respond

    https://amerisource.us.com/about-amerisource/history, https://amerisource.us.com/about-amerisource/teams, https://amerisource.us.com/about-amerisource/awards, https://amerisource.us.com/news, https://amerisource.us.com/investment/amerisource-closes-16000000-credit-facility-for-returning-logistics-client and https://amerisource.us.com/investment/amerisource-closes-10m-senior-credit-facility-for-industrial-services-firm-2 and 1 other took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 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 11 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 16 small tap targets

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

  • 5 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 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

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: “over 1,600 companies”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 148 words

    The homepage has only about 148 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.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 1 cookie set on arrival

    1

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

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

  • 11 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on amerisource.us.com, including 14 speed issues, 6 SEO issues and 3 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