boardcollective.com.au website review

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

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

8 third-party services load with your homepage (starapps.studio, Klaviyo and Google Tag Manager and others), adding 15.9 MB and 905 ms of main-thread time.

29 images could be 1.3 MB 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.

starapps.studio costs a phone 515 ms of main-thread work and 14.6 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.

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

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

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

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

Klaviyo costs a phone 158 ms of main-thread work and 510 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.

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

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

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

6 KiB could be saved by minifying CSS.

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 see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A promotional banner for summer footwear featuring three pr…”. Most of its time is resource load delay (3.7 s).

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

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

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

3 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 136 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 20.8 MB in 365 requests on a phone: scripts 16.4 MB (99), images 2.8 MB (59) and other files 1.1 MB (187). Under 2 MB keeps phones on slow connections fast.

6 images (1.2 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.

Summer_Footwear_MOB_2.webp 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).

3 images are downloaded at several times the size a phone draws them, for example Summer_Footwear_MOB_2.webp at 1,200 px wide, shown at 390 px. Resized copies would save about 218 KiB.

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

31 buttons have no accessible name, so screen readers announce just “button”.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

The homepage links to 605 pages on boardcollective.com.au and 3 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://boardcollective.com.au/pages/tolstoy-tv-page, https://boardcollective.com.au/collections/mens-new-in, https://boardcollective.com.au/collections/kids-new-in-1, https://boardcollective.com.au/collections/footwear-new-in, https://boardcollective.com.au/collections/accessories-new-in and https://boardcollective.com.au/collections/surf-new-in-1 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://boardcollective.com.au/pages/shipping, https://boardcollective.com.au/pages/tolstoy-tv-page, https://boardcollective.com.au/collections/new-in, https://boardcollective.com.au/collections/mens-new-in, https://boardcollective.com.au/collections/womens-new-in-1 and https://boardcollective.com.au/collections/kids-new-in-1 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

Large scripts ship without source maps.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 337 words of visible text.

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