Website review, no card needed
culistack.com website review
Visit site (opens in a new tab)Reviewed 8 November 202627 issues · 80 checks
This review found 27 issues worth fixing on culistack.com, 8 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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
82B- #33,036 of 117,105 reviewed websitesbeats 66%
- #22,149 of 66,867 online storesbeats 60%
- #21,418 of 60,987 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 186 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 195 ms |
| Jul 18, 2026 | 196 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 205 ms |
| Aug 8, 2026 | 210 ms |
| Aug 15, 2026 | 212 ms |
| Aug 22, 2026 | 218 ms |
| Aug 29, 2026 | 221 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 230 ms |
| Sep 19, 2026 | 235 ms |
| Sep 26, 2026 | 237 ms |
| Oct 3, 2026 | 236 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 237 ms |
| Oct 24, 2026 | 237 ms |
| Oct 31, 2026 | 233 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
Main-thread work: 4.1 s
A phone's processor spends 4.1 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 67
67/100Your mobile performance score is 67. 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, Klaviyo and Clarity and others), adding 1.1 MB and 708 ms of main-thread time.
Reduce unused JavaScript
150 ms · 391 KiBAbout 391 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.
Use efficient cache lifetimes
100 ms · 357 KiB19 files are served with short cache lifetimes, so returning visitors download them again (357 KiB).
Render-blocking requests
450 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Klaviyo adds 171 ms
171 msKlaviyo costs a phone 171 ms of main-thread work and 479 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.
1,733 HTML elements
The page has 1,733 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.
Legacy JavaScript
53 KiBPolyfills for old browsers add 53 KiB JavaScript that modern phones do not need.
Reduce unused CSS
10 ms · 37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10 ms faster on a phone.
Improve image delivery
22 KiB2 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
1 checks passed
Server response: 124 ms
124 msYour server sent the HTML in 124 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.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 186 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 604 ms
604 msReal visitors wait 604 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 200 ms
200 msScripts block the page for only 200 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 3.6 MB in 378 requests
3.6 MBYour homepage downloads 3.6 MB in 378 requests on a phone: scripts 1.6 MB (107), other files 1.1 MB (211) and HTML 387 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
hf_20260817_092501_cc1970f9-c663-4754-bac0-9852d8ed008f_2.pn 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 1.0 g of CO₂ per visit
1.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.02 g of CO₂e: 122.8 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
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 58 images in the HTML carry an alt attribute.
49 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: 49 passed and 5 failed. 2 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.
108 internal links, 7 external
The homepage links to 108 pages on culistack.com and 7 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Over 100,000 home cooks chose CuliStack: award-winning stackable cookware sets that fit in a single kitchen drawer. Ord…”.
Title: 59 characters
Your title is a healthy 59 characters: “CuliStack | Stackable Cookware Sets | 60 Days Trial Cooking”.
Canonical URL set
The canonical URL is https://culistack.com/en.
Structured data in place
Structured data found: Organization, WebPage 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://culistack.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 (1,064 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://culistack.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://culistack.com/en/collections/all, whose canonical is https://culistack.com/en/collections/all-products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://culistack.com/en/collections/all, https://culistack.com/en/products/ultimate-cookware-set, https://culistack.com/en/products/pro-cookware-set, https://culistack.com/en/products/essential-cookware-set, https://culistack.com/en/products/one-cookware-set and https://culistack.com/en/collections/cookware-sets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://culistack.com/en/collections/all took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187152282&tm=gtm002&Ver=2&mid=7b6cff6e-54fa-41da-81f8-b6eafd63440f&bo=2&sid=57feab00db1d11f1a6fb950adbfb204b&vid=57fef270db1d11f199b46bee0f3e6cdd&vids=1&msclkid=N&pi=9.
10 small tap targets
10 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 520 words of copy
The homepage carries about 520 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
11 calls to action
The homepage has 11 calls to action, for example “Shop all Cookware sets”, “Shop all Best sellers” and “Shop all Accessories”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks, a star rating and 6 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo, Meta Pixel and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
36 cookies set on arrival
36Opening the homepage sets 36 cookies, 3 of them by other companies (measured from a US location before any click).
40 other companies contacted
Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 culistack.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · T Lab Ai Translate · Klaviyo Email Marketing Sms · Stape Remix · zigpoll.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on culistack.com, including 15 speed issues and 1 SEO issue. 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.