Website review, no card needed

brunschwig.com logo

brunschwig.com website review

Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 92 checks

This review found 43 issues worth fixing on brunschwig.com, 13 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
2.8 s2.3 sMay 16Oct 312.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
149 ms112 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026116 ms
May 23, 2026127 ms
May 30, 2026129 ms
Jun 6, 2026138 ms
Jun 13, 2026145 ms
Jun 20, 2026143 ms
Jun 27, 2026138 ms
Jul 4, 2026137 ms
Jul 11, 2026130 ms
Jul 18, 2026128 ms
Jul 25, 2026137 ms
Aug 1, 2026138 ms
Aug 8, 2026139 ms
Aug 15, 2026137 ms
Aug 22, 2026129 ms
Aug 29, 2026119 ms
Sep 5, 2026120 ms
Sep 12, 2026119 ms
Sep 19, 2026129 ms
Sep 26, 2026136 ms
Oct 3, 2026130 ms
Oct 10, 2026129 ms
Oct 17, 2026124 ms
Oct 24, 2026123 ms
Oct 31, 2026129 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 brunschwig.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brunschwig.com at 0.9 s0.9 s
  2. brunschwig.com at 1.7 s1.7 s
  3. brunschwig.com at 2.6 s2.6 s
  4. brunschwig.com at 3.4 s3.4 s
  5. brunschwig.com at 4.3 s4.3 s
  6. brunschwig.com at 5.1 s5.1 s
  7. brunschwig.com at 6.0 s6.0 s
  8. brunschwig.com at 6.8 s6.8 s

Speed

12 to fix47
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 5.8 s

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

  • Reduce unused JavaScript

    900 ms · 733 KiB

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

  • Use efficient cache lifetimes

    700 ms · 581 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, nice-incontact.com and visenze.com and others), adding 1.2 MB and 922 ms of main-thread time.

  • Improve image delivery

    300 ms · 516 KiB

    18 images could be 516 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused CSS

    600 ms · 183 KiB

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

  • Google Tag Manager adds 443 ms

    443 ms

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

    350 ms

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

  • 2,991 HTML elements

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

  • nice-incontact.com adds 225 ms

    225 ms

    nice-incontact.com costs a phone 225 ms of main-thread work and 351 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.

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

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

    320 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Time to Interactive: 21.5 s

    21.5 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 794 ms

    794 ms

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Cumulative Layout Shift: 0.031

    0.031

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

Images and page weight

2 to fix83
  • Page weight: 3.8 MB in 324 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 324 requests on a phone: scripts 1.8 MB (237), images 1.3 MB (32) and fonts 228 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    whimsical_2.png 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).

  • 1 image below the first screen load straight away

    1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.09 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9093
  • Unlabelled dropdowns

    1 dropdown has no label.

  • ARIA commands must have an accessible name (1 element)

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 77 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

7 to fixGoogle 9266
  • No H1 headline

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

  • Title is short (26 characters)

    Your title is only 26 characters: “Brunschwig & Fils | Kravet”. 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 canonical URL

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

  • Meta description is long (239 characters)

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

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

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

  • No X (Twitter) card tag

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

  • 489 internal links, 13 external

    The homepage links to 489 pages on brunschwig.com and 13 external pages.

2 checks passed
  • 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.kravet.com/media/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://www.kravet.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

Other pages

2 to fix93
  • 9 pages share a meta description

    https://www.kravet.com/kravet, https://www.kravet.com/contract, https://www.kravet.com/carpet-visualizer, https://www.kravet.com/sectional-visualizer, https://www.kravet.com/advanced-color-search and https://www.kravet.com/barcode_scanner and 3 others use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.kravet.com/kravet, https://www.kravet.com/lee-jofa, https://www.kravet.com/gpj-baker, https://www.kravet.com/donghia, https://www.kravet.com/contract and https://www.kravet.com/kravet-furniture-options and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.kravet.com/barcode_scanner has 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 41 found) and read each the way a search engine does.

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

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

  • 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

3 to fixGoogle 5088
  • 23 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • 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: 1 trust badge. 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 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 278 words of copy

    The homepage carries about 278 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 31 calls to action

    The homepage has 31 calls to action, for example “Register With Trade Account”, “Apply For A Trade Account” and “SHOP NOW”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 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: OneTrust

    A consent management tool (OneTrust) 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 brunschwig.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Safenames Ltd.

Hiring

Hiring
18 open roles
Teams
Manufacturing (6), Showrooms (6), Sales (3), Customer Service (2)
Job board
recruitee

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on brunschwig.com, including 20 speed issues, 7 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