Website review, no card needed

buffbrowz.com logo

buffbrowz.com website review

Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 62 checks

This review found 25 issues worth fixing on buffbrowz.com, 9 of them high impact, across 62 checks. The most urgent: page weight: 6.4 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.4 sAug 1Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20261.5 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20262.0 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
167 ms143 msAug 8Oct 31163 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026146 ms
Aug 15, 2026153 ms
Aug 22, 2026154 ms
Aug 29, 2026162 ms
Sep 5, 2026162 ms
Sep 12, 2026164 ms
Sep 19, 2026163 ms
Sep 26, 2026162 ms
Oct 3, 2026161 ms
Oct 10, 2026160 ms
Oct 17, 2026158 ms
Oct 24, 2026162 ms
Oct 31, 2026163 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

3 to fix100
  • Largest content (LCP) got 27% slower for real visitors

    +27%

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

  • 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: 1.6 s

    1.6 s

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

  • Tap response (INP) held steady for real visitors

    +9%

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

4 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 162 ms

    162 ms

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

Images and page weight

5 to fix38
  • Page weight: 6.4 MB

    6.4 MB

    Your homepage downloads 6.4 MB on a phone, 2.3 MB of it images (37%). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    dc9fe78d-5a57-4201-93a3-1310936d795f.png weighs 960 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    WEB-ASSET-MOBILE_HERO-MAIN-2.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images in older formats

    3 images (1.1 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.

  • 11 images below the first screen load straight away

    11 images further down the page (857 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.82 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.82 g of CO₂e: 218.1 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

8 to fix90
  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

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

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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 (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 38 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 56 automated accessibility rules passed

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

SEO

2 to fix88
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Brow Lamination & Lash Lift Kits | Professional Supplies – Buff Browz”.

  • Meta description is long (201 characters)

    Your meta description is 201 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 383 internal links, 11 external

    The homepage links to 383 pages on buffbrowz.com and 11 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Buff Browz”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

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 (3,925 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 124 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fix78
  • 1 broken image

    1 image failed to load on a phone, for example https://firebasestorage.googleapis.com/v0/b/venn-prod-70222.appspot.com/o/static%2Fappstore-icon.png?alt=media&token=0b243992-925f-4c09-a068-183a30501851.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

2 checks passed
  • Tap targets are thumb-sized

    59 of 64 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage has only about 241 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Join The Community” and “Shop Brows”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Join The Community”, “Shop All” and “Apply Here”.

  • 55 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 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.

  • 50 other companies contacted

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

Apps on your store

Your storefront loads 13 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Microsoft Clarity · Klaviyo Email Marketing Sms · Hulk Form Builder · Venn Apps · Gdpr Backpack · Orbe Geolocation · Back In Stock · snapchat.com · nfcube.com · trustpilot.com · loox.io · amazonaws.com

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

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Google Analytics | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on buffbrowz.com, including 3 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