Website review, no card needed
cultiver.com website review
Visit site (opens in a new tab)Reviewed 7 November 202646 issues · 92 checks
This review found 46 issues worth fixing on cultiver.com, 14 of them high impact, across 92 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- #71,683 of 117,184 reviewed websitesbeats 34%
- #46,437 of 66,875 online storesbeats 26%
- #44,060 of 60,990 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 129 ms |
| May 23, 2026 | 138 ms |
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 150 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 156 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 175 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 167 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 162 ms |
| Oct 31, 2026 | 162 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
Speed
Improve image delivery
3.5 s · 12.2 MB79 images could be 12.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.
Render-blocking requests
1.3 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
11,660 HTML elements
The page has 11,660 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and Google Tag Manager and others), adding 26.6 MB and 1.1 s of main-thread time.
Shopify adds 242 ms
242 msShopify costs a phone 242 ms of main-thread work and 25.2 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.
Reduce unused JavaScript
150 ms · 910 KiBAbout 910 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 493 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
415 KiB43 files are served with short cache lifetimes, so returning visitors download them again (415 KiB).
Reduce unused CSS
300 ms · 92 KiBAbout 92 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 231 ms
231 msKlaviyo costs a phone 231 ms of main-thread work and 637 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.
Google Tag Manager adds 219 ms
219 msGoogle Tag Manager costs a phone 219 ms of main-thread work and 341 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.
Legacy JavaScript
52 KiBPolyfills for old browsers add 52 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 JavaScript
25 KiB25 KiB could be saved by minifying JavaScript.
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: 12 ms
12 msYour server sent the HTML in 12 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: 14.6 s
14.6 sYour largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 83.2 s
83.2 sThe page becomes fully interactive after 83.2 s. Good is under 3.8 s.
Speed Index: 11.9 s
11.9 sVisually, the page fills in at 11.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 233 ms
233 msReal visitors wait 233 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 436 ms
436 msScripts block taps and scrolling for 436 ms in total while the page loads. Good is under 200 ms.
33 images without width and height
33 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 416 ms
416 msReal visitors wait 416 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 49.6 MB in 507 requests
49.6 MBYour homepage downloads 49.6 MB in 507 requests on a phone: media 24.6 MB (3), images 21.4 MB (165) and scripts 2.2 MB (142). Under 2 MB keeps phones on slow connections fast.
36 images far larger than shown
7.5 MB36 images are downloaded at several times the size a phone draws them, for example LINENFABRICSWATCH-PINSTRIPE_1.jpg at 2,000 px wide, shown at 269 px. Resized copies would save about 7.5 MB.
35 images below the first screen load straight away
35 images further down the page (9.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
32 images in older formats
32 images (8.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.
About 14.1 g of CO₂ per visit
14.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 14.06 g of CO₂e: 1687.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
22 text elements with low contrast
22 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.
204 links without text
204 visible links have no text or label, so screen readers cannot say where they go.
179 form fields without a label
179 form fields have no label, so screen readers announce an empty box and autofill guesses.
All page content should be contained by landmarks (84 elements)
All page content should be contained by landmarks: 84 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor 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
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 H1 headlines
There are 6 <h1> headlines (“THE ROCCO & ROYAL ARRIVAL”, “THE ABUNDANT TABLE” and “INTRODUCING PINE”). One clear main headline is easier for people and search engines.
Meta description is long (178 characters)
Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("files/Logo.svg")”.
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.
477 internal links, 24 external
The homepage links to 477 pages on cultiver.com and 24 external pages.
4 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “100% European Flax Bed Linen and more | CULTIVER - USA”.
Canonical URL set
The canonical URL is https://cultiver.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://cultiver.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://cultiver.com/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,707 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.
7 checks passed
Linked pages load
10 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 10 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 10 pages that loaded have a <title>.
Best practices
69 small tap targets
69 of 120 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://cultiver.com/cdn/shop/t/259/assets/customer.css?v=66684' because its MIME type ('t…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 11-field form
Your longest form asks for 11 fields (0 required). Every extra field lowers completion.
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 2,345 words of copy
The homepage carries about 2,345 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more” and “THE GIFT SHOP”.
51 calls to action
The homepage has 51 calls to action, for example “NEW ARRIVALS SHOP NOW”, “SHOP BEDDING DISCOVER THE LOOKBOOK” and “SHOP DINING EXPLORE THE LOOKBOOK”.
Social proof on the page
Social proof on the homepage: 140 testimonial or review blocks, a star rating and 17 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.
27 cookies set on arrival
27Opening the homepage sets 27 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.
47 other companies contacted
Loading the homepage contacts 47 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, 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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Bm Country Blocker Ip Blocker · Okendo · Klaviyo Email Marketing Sms · Elevar Conversion Tracking · Gdpr Cookie Consent · Boostymark Regionblock · Simple Bundle · Swym Wishlist Plus · rise-ai.com · azureedge.net · gorgias.chat · aliyuncs.com · 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
- Spit Junction
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on cultiver.com, including 22 speed issues, 5 SEO issues and 2 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.