Website review, no card needed

prestigebrands.com logo

prestigebrands.com website review

Visit site (opens in a new tab)Reviewed 28 October 202634 issues · 82 checks

This review found 34 issues worth fixing on prestigebrands.com, 13 of them high impact, across 82 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
4.8 s1.1 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.2 s
May 23, 20264.3 s
May 30, 20264.2 s
Jun 6, 20264.4 s
Jun 13, 20264.3 s
Jun 20, 20264.0 s
Jun 27, 20263.9 s
Jul 4, 20263.4 s
Jul 11, 20262.7 s
Jul 18, 20262.2 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
110 ms69 msMay 9Oct 2478 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202697 ms
May 16, 202698 ms
May 23, 2026102 ms
May 30, 2026102 ms
Jun 6, 2026104 ms
Jun 13, 2026105 ms
Jun 20, 2026105 ms
Jun 27, 2026100 ms
Jul 4, 202692 ms
Jul 11, 202687 ms
Jul 18, 202685 ms
Jul 25, 202682 ms
Aug 1, 202686 ms
Aug 8, 202686 ms
Aug 15, 202681 ms
Aug 22, 202680 ms
Aug 29, 202676 ms
Sep 5, 202674 ms
Sep 12, 202675 ms
Sep 19, 202675 ms
Sep 26, 202678 ms
Oct 3, 202680 ms
Oct 10, 202679 ms
Oct 17, 202678 ms
Oct 24, 202678 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 prestigebrands.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix63
  • Render-blocking requests

    2.4 s

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

  • Improve image delivery

    350 ms · 1.5 MB

    29 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Reduce unused JavaScript

    910 ms · 144 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Reduce unused CSS

    750 ms · 106 KiB

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

  • Use efficient cache lifetimes

    350 ms · 240 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and userway.org and others), adding 623 KiB and 167 ms of main-thread time.

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

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 264 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 13.6 s

    13.6 s

    Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Trusted Brands For Generations For more than 100 years, our…”.

  • Time to Interactive: 14.0 s

    14.0 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 3 images without width and height

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

6 checks passed
  • Real-user INP: 93 ms

    93 ms

    Real visitors wait 93 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.

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

    -20%

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

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

    -51%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 2.1 s 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).

  • Total Blocking Time: 58 ms

    58 ms

    Scripts block the page for only 58 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • Page weight: 2.7 MB in 66 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 66 requests on a phone: images 2.0 MB (38), scripts 344 KiB (11) and fonts 281 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

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

  • 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: 92.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • 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 fixGoogle 7891
  • 1 button without a name

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

  • 7 tap targets too small

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

  • 2 text elements with low contrast

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

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

  • Hidden but focusable

    28 elements hidden from screen readers can still receive keyboard focus.

  • 2 links without text

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

  • 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 33 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8588
  • No meta description

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

  • 29 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 42 internal links, 6 external

    The homepage links to 42 pages on prestigebrands.com and 6 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Trusted Brands For Generations”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Homepage | Prestige Consumer Healthcare, Inc.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ItemList, Organization and WebPage.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.prestigebrands.com/sitemap.xml.

AI search readiness

2 to fix75
  • Some text only appears after JavaScript runs

    54%

    The HTML your server sends has 536 of the 993 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

Other pages

2 to fix90
  • 6 pages without a meta description

    https://www.prestigebrands.com/find-our-products, https://www.prestigebrands.com/about-us/our-team, https://www.prestigebrands.com/about-us/corporate-responsibility, https://www.prestigebrands.com/careers, https://www.prestigebrands.com/careers/open-positions and https://www.prestigebrands.com/careers/working-prestige have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.prestigebrands.com/find-our-products has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.prestigebrands.com/products, https://www.prestigebrands.com/find-our-products, https://www.prestigebrands.com/products/digestive-care/dramamine, https://www.prestigebrands.com/products/eye-ear-nose-throat/chloraseptic and https://www.prestigebrands.com/products/eye-ear-nose-throat/ludens 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 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.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 13 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v6.4.2/css/all.css' from origin 'https://www.prestige…”.

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: 14 customer or partner logos. 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 form on the homepage

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

  • About 993 words of copy

    The homepage carries about 993 words of visible text.

3 checks passed
  • 1 call to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

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

  • 12 other companies contacted

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

1 checks passed
  • Consent tool: Ketch

    A consent management tool (Ketch) 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 prestigebrands.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
Drupal
Framework
Bootstrap
Analytics
Google Tag Manager
Hosting
AWS

Company

Employees
448
Founded
1996
Headquarters
Tarrytown

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on prestigebrands.com, including 15 speed issues, 2 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