Programmable

Website review, no card needed

baseblocks.com.au logo

baseblocks.com.au website review

Visit site (opens in a new tab)Reviewed 12 November 202631 issues · 69 checks

This review found 31 issues worth fixing on baseblocks.com.au, 12 of them high impact, across 69 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

Site score

78C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.1 s1.4 sMay 23Nov 71.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.5 s
Jun 13, 20261.7 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20262.0 s
Nov 7, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
106 ms87 msMay 23Nov 795 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202689 ms
May 30, 202691 ms
Jun 6, 202698 ms
Jun 13, 202693 ms
Jun 20, 202695 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202698 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202698 ms
Aug 15, 202698 ms
Aug 22, 202698 ms
Aug 29, 2026101 ms
Sep 5, 2026103 ms
Sep 12, 2026103 ms
Sep 19, 2026104 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026104 ms
Oct 17, 202698 ms
Oct 24, 202698 ms
Oct 31, 202698 ms
Nov 7, 202695 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

baseblocks.com.au (opens in a new tab)
Full-page screenshot of baseblocks.com.au (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. baseblocks.com.au at 0.4 s0.4 s
  2. baseblocks.com.au at 0.8 s0.8 s
  3. baseblocks.com.au at 1.1 s1.1 s
  4. baseblocks.com.au at 1.5 s1.5 s
  5. baseblocks.com.au at 1.9 s1.9 s
  6. baseblocks.com.au at 2.3 s2.3 s
  7. baseblocks.com.au at 2.6 s2.6 s
  8. baseblocks.com.au at 3.0 s3.0 s

Speed

9 to fix53

  • Render-blocking requests

    1.9 s

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

  • Improve image delivery

    1.1 s · 619 KiB

    10 images could be 619 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Reduce unused JavaScript

    1.1 s · 237 KiB

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

  • Use efficient cache lifetimes

    800 ms · 249 KiB

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

  • Mobile performance score: 53

    53/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and Klaviyo and others), adding 2.6 MB and 725 ms of main-thread time.

  • Legacy JavaScript

    350 ms · 31 KiB

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

  • Main-thread work: 2.4 s

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

  • Shopify adds 25 ms

    25 ms

    Shopify costs a phone 25 ms of main-thread work and 1.8 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.

  • Minify JavaScript

    270 ms · 49 KiB

    49 KiB could be saved by minifying JavaScript.

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    33 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed

  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 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.

  • Largest Contentful Paint: 14.1 s

    14.1 s

    Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BaseBlocks strength training at home”.

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user TTFB: 953 ms

    953 ms

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

  • Total Blocking Time: 391 ms

    391 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

5 checks passed

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 93 ms

    93 ms

    Real visitors wait 93 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.8 s

    1.8 s

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

  • Cumulative Layout Shift: 0.064

    0.064

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

Images and page weight

1 to fix0

  • Page weight: 4.9 MB in 191 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 191 requests on a phone: media 1.7 MB (1), images 1.3 MB (15) and scripts 1.0 MB (72). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.39 g

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

Accessibility

3 to fix85

  • [aria-*] attributes are not valid or misspelled

    [aria-*] attributes are not valid or misspelled (1 element).

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed

  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

SEO

3 to fixGoogle 10086

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (69 characters)

    Your meta description is only 69 characters: “Equipment designed in-house for the home. Quick setup. Easy to store.”. 70 to 160 characters is enough to sell the click.

  • 3 H1 headlines

    There are 3 <h1> headlines (“.site-header__logo-image { height: 15px; }”, “MASTERYOUR BODY” and “MASTERYOUR BODY”). One clear main headline is easier for people and search engines.

  • 56 internal links, 4 external

    The homepage links to 56 pages on baseblocks.com.au and 4 external pages.

5 checks passed

  • Title: 46 characters

    Your title is a healthy 46 characters: “BaseBlocks | Strength training without the gym”.

  • Canonical URL set

    The canonical URL is https://baseblocks.com.au/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://baseblocks.com.au/sitemap.xml.

AI search readiness

1 to fix83

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

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.

  • llms.txt published

    The site publishes https://baseblocks.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix63

  • 2 linked pages are broken

    Your homepage links to https://baseblocks.com.au/pages/returns and https://baseblocks.com.au/pages/contact, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 10 linked pages hidden from search

    https://baseblocks.com.au/pages/collection, https://baseblocks.com.au/products/baseblocks-air, https://baseblocks.com.au/pages/baseblocks-digital, https://baseblocks.com.au/products/the-big-bar-plus, https://baseblocks.com.au/products/b-bars and https://baseblocks.com.au/products/the-nordic-plus and 4 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 7 pages without an H1

    https://baseblocks.com.au/pages/collection, https://baseblocks.com.au/products/baseblocks-air, https://baseblocks.com.au/pages/accessories, https://baseblocks.com.au/products/the-big-bar-plus, https://baseblocks.com.au/products/b-bars and https://baseblocks.com.au/products/the-nordic-plus and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7388

  • 1 third-party cookie

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

  • 1 console error

    1 error was logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 429 (Too Many Requests)”).

  • Browser-reported issues

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

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90

  • 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 577 words of copy

    The homepage carries about 577 words of visible text.

4 checks passed

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop All→”, “CONTACT” and “SHOP EQUIPMENT”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

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 baseblocks.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · snapchat.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on baseblocks.com.au, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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