bruno.com website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 13.1 s.

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

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

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

7 third-party services load with your homepage (Google CDN, Vimeo and Optanon and others), adding 4.1 MB and 1.6 s of main-thread time.

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

Vimeo costs a phone 443 ms of main-thread work and 3.1 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.

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

Optanon costs a phone 415 ms of main-thread work and 197 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.

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

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

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

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

About 77 KiB of CSS is downloaded but never applied on this page.

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

Desktop scores 61 but mobile only 26. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a woman sitting in a chair”.

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

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

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

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

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

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

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

Your homepage downloads 9.6 MB in 121 requests on a phone: scripts 2.9 MB (29), fonts 2.6 MB (9) and images 1.9 MB (40). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example bruno-stairlifts-bruce-irene.webp at 1,920 px wide, shown at 326 px. Resized copies would save about 170 KiB.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (Corporation and Product) but with 2 problems, for example “Corporation: missing name”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 64 pages on bruno.com and 3 external pages.

/stairlifts and /stair-lifts all use the title “Bruno® Stairlifts | Made in USA”. Search engines can't tell which page to show for a search, so each competes with the others.

/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.

/stairlifts and /stair-lifts use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /stair-lifts, whose canonical is /stairlifts. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

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

Large scripts ship without source maps.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bruno.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

bruno.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

Your longest form asks for 9 fields (7 required). Every extra field lowers completion.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 392 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, 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.

Opening the homepage sets 12 cookies, 3 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.