Website review, no card needed
chill.store website review
Visit site (opens in a new tab)Reviewed 9 November 202639 issues · 90 checks
This review found 39 issues worth fixing on chill.store, 12 of them high impact, across 90 checks. The most urgent: main-thread work: 5.3 s. 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,154 of 117,615 reviewed websitesbeats 66%
- #22,156 of 66,923 online storesbeats 60%
- #21,424 of 61,018 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 107 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 109 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 108 ms |
| Aug 22, 2026 | 105 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 108 ms |
| Oct 31, 2026 | 104 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: 5.3 s
A phone's processor spends 5.3 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,464 HTML elements
The page has 4,464 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
300 ms · 793 KiBAbout 793 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, alia-prod.com and rebuyengine.com and others), adding 1.6 MB and 895 ms of main-thread time.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
773 KiB17 images could be 773 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 477 ms
477 msShopify costs a phone 477 ms of main-thread work and 599 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.
Render-blocking requests
500 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Use efficient cache lifetimes
339 KiB20 files are served with short cache lifetimes, so returning visitors download them again (339 KiB).
alia-prod.com adds 151 ms
151 msalia-prod.com costs a phone 151 ms of main-thread work and 403 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.
rebuyengine.com adds 114 ms
114 msrebuyengine.com costs a phone 114 ms of main-thread work and 299 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 140 ms. During a long task the page ignores taps.
Legacy JavaScript
65 KiBPolyfills for old browsers add 65 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).
Reduce unused CSS
32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page.
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.4 s
21.4 sThe page becomes fully interactive after 21.4 s. Good is under 3.8 s.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 290 ms
290 msScripts block taps and scrolling for 290 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 107 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 449 ms
449 msReal visitors wait 449 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 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: 4.9 MB in 341 requests
4.9 MBYour homepage downloads 4.9 MB in 341 requests on a phone: images 2.1 MB (74), scripts 1.6 MB (79) and other files 912 KiB (132). Under 2 MB keeps phones on slow connections fast.
12 images in older formats
12 images (866 KiB) 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.
3 images below the first screen load straight away
3 images further down the page (90 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 167.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
20 images without alt text
20 images have no alt text, which hurts accessibility and image search.
277 links without text
277 visible links have no text or label, so screen readers cannot say where they go.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (320 characters)
Your meta description is 320 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.
80 internal links, 34 external
The homepage links to 80 pages on chill.store and 34 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Chill Steel Pipes”.
Title: 55 characters
Your title is a healthy 55 characters: “Chill Steel Pipes - Built to Chill. Designed to Evolve.”.
Canonical URL set
The canonical URL is https://chill.store/.
Structured data in place
Structured data found: BreadcrumbList 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://chill.store/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://chill.store/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (919 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without an H1
https://chill.store/pages/our-story and https://chill.store/pages/dyspensr-wholesale-registration 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 34 found) and read each the way a search engine does.
6 checks passed
Linked pages load
9 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 9 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 9 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://chill.store/.
106 small tap targets
106 of 243 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://himanshukalal404.myfreshworks.com/crm/sales/web_forms/fbbc9690899bdb09f2736affec7464b90990…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 92 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 837 words of copy
The homepage carries about 837 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: “Shop Now”.
5 calls to action
The homepage has 5 calls to action, for example “Shop”, “Contact Us” and “Shop Now”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
34 other companies contacted
Loading the homepage contacts 34 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 chill.store, 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 17 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Shipguard Protection · Flair · Puco Sections Blocks · Vex Auto Add To Cart · Webrex Ai Seo Optimer · Klaviyo Email Marketing Sms · Aimerce First Party Pixel · Ecomposer Builder · Opinew Reviews · Pusher Sections Builder · Forms · Age Checker · chimpstatic.com · goaffpro.com · vwa.la · av-northern-apps.com · rebuyengine.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
- Hosting
- Shopify
Company
- Headquarters
- Boulder
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 chill.store, including 16 speed issues, 2 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.