Website review, no card needed
bfreeaustralia.com.au website review
Visit site (opens in a new tab)Reviewed 5 November 202639 issues · 81 checks
This review found 39 issues worth fixing on bfreeaustralia.com.au, 10 of them high impact, across 81 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #75,327 of 124,112 reviewed websitesbeats 35%
- #48,249 of 69,786 online storesbeats 26%
- #45,701 of 63,472 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 125 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 164 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 170 ms |
| Aug 15, 2026 | 179 ms |
| Aug 22, 2026 | 193 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 195 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 190 ms |
| Oct 10, 2026 | 188 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 183 ms |
| Oct 31, 2026 | 183 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
How it loaded on a phone
0.9 s
1.8 s
2.6 s
3.5 s
4.4 s
5.3 s
6.1 s
7.0 s
Speed
Improve image delivery
2.6 s · 741 KiB20 images could be 741 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7,138 HTML elements
The page has 7,138 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Clarity and others), adding 2.0 MB and 897 ms of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
782 KiBAbout 782 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
700 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Use efficient cache lifetimes
531 KiB28 files are served with short cache lifetimes, so returning visitors download them again (531 KiB).
Google Tag Manager adds 381 ms
381 msGoogle Tag Manager costs a phone 381 ms of main-thread work and 366 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 290 ms. During a long task the page ignores taps.
ZenDesk adds 216 ms
216 msZenDesk costs a phone 216 ms of main-thread work and 431 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.
Stamped.io adds 68 ms
68 msStamped.io costs a phone 68 ms of main-thread work and 339 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.
Shopify adds 58 ms
58 msShopify costs a phone 58 ms of main-thread work and 363 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.
instant.one adds 47 ms
47 msinstant.one costs a phone 47 ms of main-thread work and 296 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.
Reduce unused CSS
150 ms · 186 KiBAbout 186 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.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fall Refresh Sale”.
Speed Index: 14.5 s
14.5 sVisually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.9 s
22.9 sThe page becomes fully interactive after 22.9 s. Good is under 3.8 s.
Real-user CLS: 0.23
0.23For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.
Tap response (INP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 125 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 526 ms
526 msScripts block taps and scrolling for 526 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 187 ms
187 msReal visitors wait 187 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 787 ms
787 msReal visitors wait 787 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 22.6 MB in 352 requests
22.6 MBYour homepage downloads 22.6 MB in 352 requests on a phone: media 16.2 MB (4), images 3.0 MB (126) and scripts 1.9 MB (88). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MOFALL.jpg 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).
4 images far larger than shown
156 KiB4 images are downloaded at several times the size a phone draws them, for example MOFALL.jpg at 1,504 px wide, shown at 390 px. Resized copies would save about 156 KiB.
About 6.4 g of CO₂ per visit
6.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.41 g of CO₂e: 769.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
50 links without text
50 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 186 images in the HTML carry an alt attribute.
15 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 15 WCAG 2.2 A/AA and best-practice rules on the phone render: 15 passed and 0 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
51 links crawlers can't follow
51 links have no real href, so search engines can't follow them.
Title is long (85 characters)
Your title is 85 characters, so Google will cut it off around 60: “B Free Intimate Apparel: Luxury Lingerie, Maternity Wear & Hosiery – B Free Australia”.
Meta description is long (185 characters)
Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (FAQPage and Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.bfreeaustralia.com.au)”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
500 internal links, 70 external
The homepage links to 500 pages on bfreeaustralia.com.au and 70 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.bfreeusa.com/.
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://www.bfreeusa.com/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (6,411 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bfreeusa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://www.bfreeusa.com/collections/pregnancy-bras and https://www.bfreeusa.com/collections/bra-undies-sets have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
34 small tap targets
34 of 131 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
About 2,415 words of copy
The homepage carries about 2,415 words of visible text.
6 checks passed
73 calls to action
The homepage has 73 calls to action, for example “Log In/Sign Up”, “Shop Now” and “Mesh Shaping Shorts SHOP NOW”.
55 short forms
55 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 91 testimonial or review blocks and 11 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 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.
32 cookies set on arrival
32Opening the homepage sets 32 cookies (measured from a US location before any click).
No consent tool detected
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.
49 other companies contacted
Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 bfreeaustralia.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Triplewhale · Microsoft Clarity · Simprosys Google Shopping Feed · Redo · Attentive · Advanced Wishlist · My Wishlist Share Remind · Klaviyo Email Marketing · Pushowl · B Free Bundles · hulkapps.com · addons.business · getredo.com · attn.tv · instant.one
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 Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on bfreeaustralia.com.au, including 23 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.