boardmans.co.za website review

137 files are served with short cache lifetimes, so returning visitors download them again (9.8 MB).

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

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

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

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

17 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.6 MB and 1.4 s of main-thread time.

1.1 MB could be saved by minifying JavaScript.

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

About 139 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.

Reduce initial server response time. Google estimates savings of 673 ms on a phone.

The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Your server takes 773 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

38 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 26.5 MB in 294 requests on a phone: images 23.5 MB (135), scripts 2.2 MB (77) and other files 469 KiB (67). Under 2 MB keeps phones on slow connections fast.

9 images weigh 8.2 MB together. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example BDM481873_Shop_The_Look_-_Entertain_Host_V3_1.jpg at 1,318 px wide, shown at 358 px. Resized copies would save about 2.8 MB.

39 images (14.7 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.

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

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

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

ARIA commands must have an accessible name: 10 elements on the page fail this check, rated serious by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

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

Some list items are not inside a list.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 138 pages on boardmans.co.za and 7 external pages.

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.

https://www.boardmans.co.za/privacy-policy, https://www.boardmans.co.za/storelocator, https://www.boardmans.co.za/apply-for-credit, https://www.boardmans.co.za/rochester, https://www.boardmans.co.za/bed-bath and https://www.boardmans.co.za/decor-lounge and 5 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.boardmans.co.za/more-categories/work-study, whose canonical is https://www.boardmans.co.za/work-study. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.boardmans.co.za/privacy-policy and https://www.boardmans.co.za/rochester have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.boardmans.co.za/bed-bath, https://www.boardmans.co.za/decor-lounge, https://www.boardmans.co.za/more-categories/work-study, https://www.boardmans.co.za/home-improvement-clean and https://www.boardmans.co.za/more-categories/travel-explore took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Large scripts ship without source maps.

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.

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 1,798 words of visible text.

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

Opening the homepage sets 26 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.