Website review, no card needed

brabbu.com logo

brabbu.com website review

Visit site (opens in a new tab)Reviewed 23 October 202661 issues · 92 checks

This review found 61 issues worth fixing on brabbu.com, 27 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
10.9 s3.4 sMay 2Oct 174.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20269.3 s
May 9, 202610.0 s
May 16, 20269.8 s
May 23, 20269.9 s
May 30, 20269.2 s
Jun 6, 20268.1 s
Jun 13, 20266.9 s
Jun 20, 20266.5 s
Jun 27, 20266.3 s
Jul 4, 20266.0 s
Jul 11, 20266.1 s
Jul 18, 20266.2 s
Jul 25, 20266.2 s
Aug 1, 20266.4 s
Aug 8, 20266.7 s
Aug 15, 20266.4 s
Aug 22, 20266.3 s
Aug 29, 20266.3 s
Sep 5, 20266.1 s
Sep 12, 20266.0 s
Sep 19, 20265.8 s
Sep 26, 20265.5 s
Oct 3, 20265.4 s
Oct 10, 20265.3 s
Oct 17, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
149 ms80 msMay 2Oct 1789 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026126 ms
May 16, 2026112 ms
May 23, 2026106 ms
May 30, 2026106 ms
Jun 6, 2026105 ms
Jun 13, 2026105 ms
Jun 20, 2026110 ms
Jun 27, 2026117 ms
Jul 4, 2026132 ms
Jul 11, 2026141 ms
Jul 18, 2026129 ms
Jul 25, 2026123 ms
Aug 1, 2026120 ms
Aug 8, 2026122 ms
Aug 15, 2026122 ms
Aug 22, 2026128 ms
Aug 29, 2026121 ms
Sep 5, 2026109 ms
Sep 12, 2026112 ms
Sep 19, 2026108 ms
Sep 26, 2026111 ms
Oct 3, 2026111 ms
Oct 10, 202688 ms
Oct 17, 202689 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 brabbu.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brabbu.com at 1.0 s1.0 s
  2. brabbu.com at 2.0 s2.0 s
  3. brabbu.com at 2.9 s2.9 s
  4. brabbu.com at 3.9 s3.9 s
  5. brabbu.com at 4.9 s4.9 s
  6. brabbu.com at 5.9 s5.9 s
  7. brabbu.com at 6.9 s6.9 s
  8. brabbu.com at 7.9 s7.9 s

Speed

11 to fix7
  • Reduce unused JavaScript

    11.7 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.7 s faster on a phone.

  • Avoid multiple page redirects

    6.8 s

    The page goes through 2 redirects before it starts loading, costing about 6.8 s. Link and advertise the final URL directly.

  • Render-blocking requests

    2.3 s

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

  • Use efficient cache lifetimes

    1.6 s · 373 KiB

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

  • Mobile performance score: 7

    7/100

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

  • Main-thread work: 6.8 s

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

  • 20 long tasks on the main thread

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

  • Font display

    400 ms

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

  • Reduce unused CSS

    300 ms · 50 KiB

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

  • Google Tag Manager adds 154 ms

    154 ms

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

  • 1,602 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 826 KiB and 244 ms of main-thread time.

  • Legacy JavaScript

    12 KiB

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

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

Core Web Vitals

12 to fix0
  • 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: 5.8 s

    5.8 s

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

  • Real-user CLS: 0.97

    0.97

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

  • First Contentful Paint: 8.3 s

    8.3 s

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

  • Largest Contentful Paint: 93.7 s

    93.7 s

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

  • Speed Index: 16.6 s

    16.6 s

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

  • Time to Interactive: 106.5 s

    106.5 s

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

  • Cumulative Layout Shift: 0.682

    0.682

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 21 images without width and height

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

2 checks passed
  • Tap response (INP) got 26% faster for real visitors

    -26%

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

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

    -50%

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

Images and page weight

4 to fix35
  • Page weight: 39.6 MB in 434 requests

    39.6 MB

    Your homepage downloads 39.6 MB in 434 requests on a phone: images 36.0 MB (300), scripts 3.2 MB (69) and fonts 271 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

  • 40 images in older formats

    40 images (5.9 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 far larger than shown

    55 KiB

    1 image is downloaded at several times the size a phone draws it, for example floor-samples-upholstery-popup.jpg at 1,080 px wide, shown at 343 px. Resized copies would save about 55 KiB.

  • About 11.2 g of CO₂ per visit

    11.22 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

14 to fixGoogle 6580
  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 23 tap targets too small

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

  • Interactive controls must not be nested (4 elements)

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

  • 3 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

  • 89 form fields without a label

    89 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Heading levels should only increase by one (4 elements)

    Heading levels should only increase by one: 4 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 16 links without text

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 13 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 8578
  • No H1 headline

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

  • 36 links crawlers can't follow

    36 links have no real href, so search engines can't follow them.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • 234 internal links, 26 external

    The homepage links to 234 pages on brabbu.com and 26 external pages.

4 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “BRABBU is a design brand that reflects an intense way of living, bringing fierceness, strength and power into an urban …”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “BRABBU Design Forces - Contemporary Home Furniture”.

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

  • No llms.txt

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

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

Other pages

5 to fix76
  • 8 pages share a title

    /, https://brabbu.com/catalogue, https://brabbu.com/downloads/coveted-28th-edition, https://brabbu.com/home/downloads/category/ebooks, https://brabbu.com/home/downloads/category/moodboards and https://brabbu.com/home/downloads and 2 others all use the title “BRABBU Design Forces - Contemporary Home Furniture”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://brabbu.com/blog, https://brabbu.com/en/inspiration-and-ideas and https://brabbu.com/en/news-events have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://brabbu.com/catalogue, https://brabbu.com/downloads/coveted-28th-edition, https://brabbu.com/home/downloads/category/ebooks, https://brabbu.com/home/downloads/category/moodboards, https://brabbu.com/home/downloads and https://brabbu.com/home/room-by-room and 1 other 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://brabbu.com/catalogue, whose canonical is https://brabbu.com/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://brabbu.com/catalogue, https://brabbu.com/downloads/coveted-28th-edition, https://brabbu.com/home/downloads/category/ebooks, https://brabbu.com/home/downloads/category/moodboards, https://brabbu.com/home/downloads and https://brabbu.com/home/room-by-room and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://brabbu.com/catalogue, https://brabbu.com/downloads/coveted-28th-edition, https://brabbu.com/home/downloads/category/ebooks, https://brabbu.com/home/downloads/category/moodboards, https://brabbu.com/home/downloads and https://brabbu.com/home/room-by-room and 1 other 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.

  • 4 pages slow to respond

    https://brabbu.com/catalogue, https://brabbu.com/downloads/coveted-28th-edition, https://brabbu.com/en/inspiration-and-ideas and https://brabbu.com/en/news-events took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

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

Best practices

4 to fixGoogle 9263
  • 1 broken image

    1 image failed to load on a phone, for example https://www.brabbu.com/images/footer/partner-brands/logos/null.jpg.

  • 30 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 15-field form

    Your longest form asks for 15 fields (13 required). Every extra field lowers completion.

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

    The homepage carries about 279 words of visible text.

2 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “REGISTER”, “Register” and “CONTACT US”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

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, Hotjar and LinkedIn Insight 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.

  • 19 cookies set on arrival

    19

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 brabbu.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
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 61 issues on brabbu.com, including 23 speed issues, 5 SEO issues and 4 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