Website review, no card needed

brocelitepro.com logo

brocelitepro.com website review

Visit site (opens in a new tab)Reviewed 13 November 202645 issues · 84 checks

This review found 45 issues worth fixing on brocelitepro.com, 18 of them high impact, across 84 checks. The most urgent: page weight: 53.2 MB in 183 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

Full-page screenshot of brocelitepro.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brocelitepro.com at 1.2 s1.2 s
  2. brocelitepro.com at 2.4 s2.4 s
  3. brocelitepro.com at 3.7 s3.7 s
  4. brocelitepro.com at 4.9 s4.9 s
  5. brocelitepro.com at 6.1 s6.1 s
  6. brocelitepro.com at 7.3 s7.3 s
  7. brocelitepro.com at 8.6 s8.6 s
  8. brocelitepro.com at 9.8 s9.8 s

Speed

9 to fix60
  • Render-blocking requests

    2.9 s

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

  • Reduce unused JavaScript

    1.2 s · 233 KiB

    About 233 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, applovin.com and Google Optimize and others), adding 50.4 MB and 344 ms of main-thread time.

  • Shopify adds 26 ms

    26 ms

    Shopify costs a phone 26 ms of main-thread work and 50.0 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.

  • Mobile performance score: 60

    60/100

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

  • Improve image delivery

    990 KiB

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

  • Reduce unused CSS

    450 ms · 99 KiB

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

  • Use efficient cache lifetimes

    300 ms · 33 KiB

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

  • Main-thread work: 3.0 s

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

  • Legacy JavaScript

    150 ms · 9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 123 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).

  • Minify CSS

    10 KiB

    10 KiB could be saved by minifying CSS.

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

    3 ms

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

Core Web Vitals

5 to fix64
  • Largest Contentful Paint: 14.3 s

    14.3 s

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

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • 10 images without width and height

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

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

2 checks passed
  • Total Blocking Time: 175 ms

    175 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix43
  • Page weight: 53.2 MB in 183 requests

    53.2 MB

    Your homepage downloads 53.2 MB in 183 requests on a phone: media 49.9 MB (11), images 1.2 MB (18) and other files 733 KiB (85). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    574 KiB

    7 images are downloaded at several times the size a phone draws them, for example ML_Liquid.png at 1,882 px wide, shown at 370 px. Resized copies would save about 574 KiB.

  • 7 images below the first screen load straight away

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

  • About 15.1 g of CO₂ per visit

    15.09 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

11 to fixGoogle 7382
  • Invalid ARIA attributes

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

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (12 elements)

    All page content should be contained by landmarks: 12 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.

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

6 to fixGoogle 8565
  • 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 (18 characters)

    Your title is only 18 characters: “brocelitewholesale”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 28 internal links, 6 external

    The homepage links to 28 pages on brocelitepro.com and 6 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://brocelitepro.com/.

  • 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://brocelitepro.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix76
  • 8 pages share 4 titles

    https://brocelitepro.com/products/brocelite-plus and https://brocelitepro.com/products/brocelite%C2%AE-plus-60-caps-1 all use the title “BrocElite® Plus - 60 caps – brocelitewholesale”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://brocelitepro.com/pages/get-in-touch has no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages share a meta description

    https://brocelitepro.com/products/brocelite-plus and https://brocelitepro.com/products/brocelite%C2%AE-plus-60-caps-1 use the same meta description. A description written for each page earns more clicks.

  • 7 links to non-canonical URLs

    Your homepage links to 7 pages by a URL that isn't their canonical one, for example https://brocelitepro.com/products/brocelite%E2%84%A2-plus-30-caps, whose canonical is https://brocelitepro.com/products/brocelite%e2%84%a2-plus-30-caps. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://brocelitepro.com/products/brocelite-plus, https://brocelitepro.com/products/brocelite%E2%84%A2-plus-30-caps, https://brocelitepro.com/products/curcelite, https://brocelitepro.com/products/berbelite, https://brocelitepro.com/products/sleepelite and https://brocelitepro.com/products/quercelite%E2%84%A2 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://brocelitepro.com/products/brocelite-plus, https://brocelitepro.com/products/brocelite%E2%84%A2-plus-30-caps, https://brocelitepro.com/products/curcelite, https://brocelitepro.com/products/berbelite, https://brocelitepro.com/products/sleepelite and https://brocelitepro.com/products/quercelite%E2%84%A2 and 7 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.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

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

    The homepage carries about 387 words of visible text.

4 checks passed
  • 14 calls to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 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.

  • 21 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2022.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on brocelitepro.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