Website review, no card needed
cultiver.com.au website review
Visit site (opens in a new tab)Reviewed 10 November 202643 issues · 91 checks
This review found 43 issues worth fixing on cultiver.com.au, 16 of them high impact, across 91 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
72C- #91,220 of 117,262 reviewed websitesbeats 19%
- #56,916 of 66,884 online storesbeats 12%
- #53,124 of 60,996 Shopify storesbeats 10%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 179 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 191 ms |
| Jul 4, 2026 | 198 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 212 ms |
| Jul 25, 2026 | 219 ms |
| Aug 1, 2026 | 219 ms |
| Aug 8, 2026 | 220 ms |
| Aug 15, 2026 | 212 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 199 ms |
| Sep 12, 2026 | 203 ms |
| Sep 19, 2026 | 212 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 219 ms |
| Oct 10, 2026 | 217 ms |
| Oct 17, 2026 | 209 ms |
| Oct 24, 2026 | 206 ms |
| Oct 31, 2026 | 211 ms |
| Nov 7, 2026 | 209 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
1.3 s
2.5 s
3.8 s
5.1 s
6.3 s
7.6 s
8.9 s
10.1 s
Speed
Improve image delivery
2.0 s · 3.5 MB27 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
2.1 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 44
44/100Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.7 s
A phone's processor spends 8.7 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7,629 HTML elements
The page has 7,629 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 (Klaviyo, Shopify and Google Tag Manager and others), adding 2.3 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
750 ms · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 435 KiB44 files are served with short cache lifetimes, so returning visitors download them again (435 KiB).
Reduce unused CSS
300 ms · 108 KiBAbout 108 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Klaviyo adds 332 ms
332 msKlaviyo costs a phone 332 ms of main-thread work and 647 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 314 ms
314 msShopify costs a phone 314 ms of main-thread work and 711 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 354 ms. During a long task the page ignores taps.
Google Tag Manager adds 290 ms
290 msGoogle Tag Manager costs a phone 290 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.
Minify JavaScript
150 ms · 49 KiB49 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 KiB JavaScript that modern phones do not need.
Minify CSS
9 KiB9 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.
1 checks passed
Server response: 18 ms
18 msYour server sent the HTML in 18 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: 25.7 s
25.7 sYour largest element takes 25.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 48.2 s
48.2 sThe page becomes fully interactive after 48.2 s. Good is under 3.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 245 ms
245 msReal visitors wait 245 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 901 ms
901 msReal visitors wait 901 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 599 ms
599 msScripts block taps and scrolling for 599 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 179 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 12.7 MB in 428 requests
12.7 MBYour homepage downloads 12.7 MB in 428 requests on a phone: images 8.8 MB (100), scripts 2.4 MB (152) and other files 1.1 MB (145). Under 2 MB keeps phones on slow connections fast.
28 images far larger than shown
3.2 MB28 images are downloaded at several times the size a phone draws them, for example CULTIVER-Fia-Napkin-White-01_dd6f2fcc-4bf9-47d5-ba28-06c3a2b at 1,800 px wide, shown at 343 px. Resized copies would save about 3.2 MB.
25 images below the first screen load straight away
25 images further down the page (4.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
12 images in older formats
12 images (2.5 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.
An image on the first screen is lazy-loaded
Rocco_Royal_Royal_-detail_1.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 3.6 g of CO₂ per visit
3.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.60 g of CO₂e: 432.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (66 elements)
All page content should be contained by landmarks: 66 elements on the page fail this check, rated moderate by axe-core.
139 form fields without a label
139 form fields have no label, so screen readers announce an empty box and autofill guesses.
106 links without text
106 visible links have no text or label, so screen readers cannot say where they go.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“THE ROCCO & ROYAL ARRIVAL”, “INTRODUCING PINE” and “THE GIFT SHOP”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
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.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
371 internal links, 24 external
The homepage links to 371 pages on cultiver.com.au and 24 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Luxurious 100% European flax linen sheets, duvet covers, pillowcases, throws, robes and more. Our linen is pre-washed f…”.
Title: 58 characters
Your title is a healthy 58 characters: “100% European Flax bed linen & more | CULTIVER - Australia”.
Canonical URL set
The canonical URL is https://cultiver.com.au/.
Structured data in place
Structured data found: Organization and WebSite.
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://cultiver.com.au/sitemap.xml.
AI search readiness
No llms.txt
There is no https://cultiver.com.au/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,053 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages slow to respond
https://cultiver.com.au/collections/new-arrivals and https://cultiver.com.au/collections/most-loved took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 151 found) and read each the way a search engine does.
7 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 4 pages that loaded have a meta description.
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 4 pages that loaded have a <title>.
Best practices
36 small tap targets
36 of 84 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 “Refused to apply style from 'https://cultiver.com.au/cdn/shop/t/484/assets/customer.css?v=195185' because its MIME type…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 1,304 words of copy
The homepage carries about 1,304 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: “Learn more” and “SHOP OUR AWARD WINNING LINEN”.
50 calls to action
The homepage has 50 calls to action, for example “SHOP OUR AWARD WINNING LINEN”, “NEW ARRIVALS SHOP NOW” and “GATHER INSPIRATION SHOP THE LOOKBOOK”.
21 short forms
21 short forms (5 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 63 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity 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.
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.
39 other companies contacted
Loading the homepage contacts 39 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 cultiver.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Okendo · Multi Location Stock Info · Wingify · Gdpr Cookie Consent · Simple Bundle · Swym Wishlist Plus · rise-ai.com · gorgias.chat · 9gtb.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
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on cultiver.com.au, including 23 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.