Website review, no card needed
bornprimitive.com.au website review
Visit site (opens in a new tab)Reviewed 10 November 202642 issues · 93 checks
This review found 42 issues worth fixing on bornprimitive.com.au, 16 of them high impact, across 93 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
75C- #72,181 of 109,350 reviewed websitesbeats 30%
- #45,865 of 61,859 online storesbeats 22%
- #43,357 of 56,401 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 278 ms |
| May 30, 2026 | 275 ms |
| Jun 6, 2026 | 277 ms |
| Jun 13, 2026 | 267 ms |
| Jun 20, 2026 | 262 ms |
| Jun 27, 2026 | 267 ms |
| Jul 4, 2026 | 272 ms |
| Jul 11, 2026 | 283 ms |
| Jul 18, 2026 | 282 ms |
| Jul 25, 2026 | 289 ms |
| Aug 1, 2026 | 313 ms |
| Aug 8, 2026 | 328 ms |
| Aug 15, 2026 | 358 ms |
| Aug 22, 2026 | 382 ms |
| Aug 29, 2026 | 407 ms |
| Sep 5, 2026 | 401 ms |
| Sep 12, 2026 | 385 ms |
| Sep 19, 2026 | 363 ms |
| Sep 26, 2026 | 313 ms |
| Oct 3, 2026 | 288 ms |
| Oct 10, 2026 | 295 ms |
| Oct 17, 2026 | 295 ms |
| Oct 24, 2026 | 297 ms |
| Oct 31, 2026 | 296 ms |
| Nov 7, 2026 | 287 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.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Improve image delivery
2.1 s · 954 KiB18 images could be 954 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
FontAwesome CDN adds 1.8 s
1.8 sFontAwesome CDN costs a phone 1.8 s of main-thread work and 68 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,633 HTML elements
The page has 6,633 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 (FontAwesome CDN, Google Tag Manager and govx.com and others), adding 2.0 MB and 3.4 s of main-thread time.
Reduce unused JavaScript
972 KiBAbout 972 KiB of JavaScript is downloaded but never used on this page.
Render-blocking requests
750 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google Tag Manager adds 580 ms
580 msGoogle Tag Manager costs a phone 580 ms of main-thread work and 848 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.
Use efficient cache lifetimes
348 KiB37 files are served with short cache lifetimes, so returning visitors download them again (348 KiB).
govx.com adds 328 ms
328 msgovx.com costs a phone 328 ms of main-thread work and 7 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.
Klaviyo adds 230 ms
230 msKlaviyo costs a phone 230 ms of main-thread work and 544 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 120 ms
120 msShopify costs a phone 120 ms of main-thread work and 404 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Reduce unused CSS
82 KiBAbout 82 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
61 KiBPolyfills for old browsers add 61 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 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: 20.3 s
20.3 sYour largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 35.4 s
35.4 sThe page becomes fully interactive after 35.4 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.252
0.252The layout shifts by 0.252 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
100 images without width and height
100 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 311 ms
311 msScripts block taps and scrolling for 311 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 278 ms to 287 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 499 ms
499 msReal visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 22.7 MB in 581 requests
22.7 MBYour homepage downloads 22.7 MB in 581 requests on a phone: media 14.1 MB (1), images 4.5 MB (101) and scripts 2.2 MB (137). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
coed_bestsellers.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).
About 6.4 g of CO₂ per visit
6.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.44 g of CO₂e: 772.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
131 text elements with low contrast
131 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
35 links without text
35 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “PATRIOTIC”). One clear main headline is easier for people and search engines.
Meta description is long (188 characters)
Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
761 internal links, 5 external
The homepage links to 761 pages on bornprimitive.com.au and 5 external pages.
6 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “Born Primitive - Apparel & Footwear For The Driven”.
Canonical URL set
The canonical URL is https://bornprimitive.com/.
Structured data in place
Structured data found: Organization, Person and WebSite.
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://bornprimitive.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,805 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bornprimitive.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://bornprimitive.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://bornprimitive.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://bornprimitive.com/collections/all, https://bornprimitive.com/customer_authentication/redirect, https://bornprimitive.com/pages/veterans-day and https://bornprimitive.com/collections/mens-shop-all have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://bornprimitive.com/collections/all, https://bornprimitive.com/customer_authentication/redirect, https://bornprimitive.com/collections/mens-womens-best-sellers, https://bornprimitive.com/pages/veterans-day, https://bornprimitive.com/collections/mens-shop-all and https://bornprimitive.com/collections/campfire-collection-mens and 9 others 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 137 found) and read each the way a search engine does.
3 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://scontent.cdninstagram.com/v/t51.82787-15/894138375_18647208676022677_2589904515894589525_n.jpg?stp=dst-jpg_e35_tt6&_nc_cat=108&ccb=7-5&_nc_sid=18de74&efg=eyJlZmdfdGFnIjoiU1RPUlkuYmVzdF9pbWFnZV.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to fetch r.fetch (https://bornprimitive.com/cdn/wpm/sf59a8868w8ba6d0d6p6ab5e8acm046c7fc6m.js:1:74498)”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
74 of 75 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 733 words of copy
The homepage carries about 733 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP MEN'S” and “SHOP WOMEN'S”.
524 calls to action
The homepage has 524 calls to action, for example “Shop All”, “WOODSMAN FLANNEL Shop Now →” and “NEW ARRIVALS Shop Now →”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Pinterest Tag 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.
29 cookies set on arrival
29Opening the homepage sets 29 cookies, 1 of them by other companies (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.
64 other companies contacted
Loading the homepage contacts 64 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 bornprimitive.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 26 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Aspire Affiliates App · Okendo · Redo · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · P8lm7fn3b Opensend · Orderprotect · Gdpr Cookie Consent · Applovin Shop Integration · Aspire App · Giftwizard · Realift · upsell-apps.com · snapchat.com · cloudfront.net · provenpixel.com · govx.com · goaffpro.com · zonos.com · googleapis.com · ablestar.app · gorgias.chat · shipinsure.io · 9gtb.com · rise-ai.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
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on bornprimitive.com.au, including 21 speed issues, 3 SEO issues and 3 conversion gaps. 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.