thebrick.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, LivePerson and Riskified and others), adding 1.3 MB and 824 ms of main-thread time.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

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

About 89 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 costs a phone 322 ms of main-thread work and 321 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.

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

LivePerson costs a phone 237 ms of main-thread work and 553 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.

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

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

38 KiB JavaScript is shipped twice across bundles.

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

10 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday Early Access at The Brick! 65% Off Genuine Lea…”.

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

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

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

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

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

Your homepage downloads 4.7 MB in 327 requests on a phone: images 1.7 MB (89), scripts 1.7 MB (99) and other files 840 KiB (117). Under 2 MB keeps phones on slow connections fast.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

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

The homepage links to 683 pages on thebrick.com and 21 external pages.

Your homepage links to https://www.thebrick.com/collections/mattress-store, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.thebrick.com/collections/furniture-living-room, https://www.thebrick.com/collections/furniture-bedroom, https://www.thebrick.com/collections/furniture-dining-room, https://www.thebrick.com/collections/appliances, https://www.thebrick.com/collections/electronics and https://www.thebrick.com/collections/furniture-office and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.thebrick.com/collections/home-decor, https://www.thebrick.com/collections/small-space-furniture, https://www.thebrick.com/collections/outdoor-living, https://www.thebrick.com/collections/sale, https://www.thebrick.com/collections/last-chance and https://www.thebrick.com/pages/flyer and 1 other took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 344 words of visible text.

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

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

Opening the homepage sets 23 cookies (measured from a US location before any click).

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.

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