Website review, no card needed

brondell.com logo

brondell.com website review

Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 92 checks

This review found 42 issues worth fixing on brondell.com, 16 of them high impact, across 92 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
3.3 s2.1 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.5 s
May 9, 20262.5 s
May 16, 20262.4 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.9 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
155 ms139 msMay 2Oct 17152 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026145 ms
May 9, 2026143 ms
May 16, 2026143 ms
May 23, 2026141 ms
May 30, 2026142 ms
Jun 6, 2026142 ms
Jun 13, 2026141 ms
Jun 20, 2026141 ms
Jun 27, 2026144 ms
Jul 4, 2026147 ms
Jul 11, 2026150 ms
Jul 18, 2026152 ms
Jul 25, 2026153 ms
Aug 1, 2026150 ms
Aug 8, 2026149 ms
Aug 15, 2026150 ms
Aug 22, 2026152 ms
Aug 29, 2026153 ms
Sep 5, 2026152 ms
Sep 12, 2026150 ms
Sep 19, 2026148 ms
Sep 26, 2026147 ms
Oct 3, 2026148 ms
Oct 10, 2026149 ms
Oct 17, 2026152 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 brondell.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brondell.com at 1.6 s1.6 s
  2. brondell.com at 3.2 s3.2 s
  3. brondell.com at 4.8 s4.8 s
  4. brondell.com at 6.4 s6.4 s
  5. brondell.com at 8.0 s8.0 s
  6. brondell.com at 9.6 s9.6 s
  7. brondell.com at 11.3 s11.3 s
  8. brondell.com at 12.9 s12.9 s

Speed

14 to fix28
  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 28

    28/100

    Your mobile performance score is 28 (desktop: 36). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 7.8 s

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

  • 3,168 HTML elements

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

  • Reduce unused JavaScript

    750 ms · 1.1 MB

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    750 ms · 733 KiB

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    570 ms · 134 KiB

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

  • Bigcommerce adds 195 ms

    195 ms

    Bigcommerce costs a phone 195 ms of main-thread work and 1.5 MB 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.

  • Improve image delivery

    288 KiB

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

  • omnisnippet1.com adds 274 ms

    274 ms

    omnisnippet1.com costs a phone 274 ms of main-thread work and 96 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.

  • Google Tag Manager adds 187 ms

    187 ms

    Google Tag Manager costs a phone 187 ms of main-thread work and 360 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.

  • Google CDN adds 117 ms

    117 ms

    Google CDN costs a phone 117 ms of main-thread work and 347 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.

  • Font display

    150 ms

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

  • Legacy JavaScript

    63 KiB

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

  • Minify JavaScript

    32 KiB

    32 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

8 to fix100
  • Time to Interactive: 29.7 s

    29.7 s

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

  • Largest Contentful Paint: 8.1 s

    8.1 s

    Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Total Blocking Time: 2.0 s

    2.0 s

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

  • First Contentful Paint: 5.2 s

    5.2 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Largest content (LCP) got 26% slower for real visitors

    +26%

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

  • 19 images without width and height

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

  • Cumulative Layout Shift: 0.107

    0.107

    The layout shifts by 0.107 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +5%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 156 ms

    156 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 457 ms

    457 ms

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

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 360 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 360 requests on a phone: scripts 2.4 MB (84), images 1.1 MB (69) and other files 420 KiB (167). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.29 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 fixGoogle 8891
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 4 tap targets too small

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

  • Hidden but focusable

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • Users should be able to zoom and scale the text up to 500% (1 element)

    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.

  • Headings skip levels

    Headings skip levels (h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

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

  • Title is short (19 characters)

    Your title is only 19 characters: “Homepage | Brondell”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 15 links with vague text

    15 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 incomplete here.

  • 255 internal links, 28 external

    The homepage links to 255 pages on brondell.com and 28 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList and Organization.

  • 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.brondell.com/xmlsitemap.php.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.brondell.com/shower-filtration is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 7 pages without a meta description

    https://www.brondell.com/sales/featured, https://www.brondell.com/water-filtration-systems-comparison-chart, https://www.brondell.com/resources/common-drinking-water-contaminants, https://www.brondell.com/resources/common-air-pollutants, https://www.brondell.com/resources/how-to-increase-shower-water-pressure and https://www.brondell.com/shower-filtration and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 17 small tap targets

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

  • 3 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 630 words of copy

    The homepage carries about 630 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now” and “Learn More”.

  • 31 calls to action

    The homepage has 31 calls to action, for example “Shop Now”, “Learn More” and “Contact Us”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 43 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies (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.

  • 54 other companies contacted

    Loading the homepage contacts 54 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 brondell.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
E-commerce
BigCommerce
Analytics
Google Analytics | Heap | Microsoft Clarity
Hosting
BigCommerce Hosting;Black Lotus

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on brondell.com, including 22 speed issues, 5 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