Website review, no card needed
apricotton.ca website review
Visit site (opens in a new tab)Reviewed 24 October 202642 issues · 89 checks
This review found 42 issues worth fixing on apricotton.ca, 17 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
67D- #112,235 of 125,263 reviewed websitesbeats 9%
- #66,309 of 70,145 online storesbeats 4%
- #60,825 of 63,741 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 146 ms |
| May 9, 2026 | 151 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 157 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 136 ms |
| Aug 22, 2026 | 133 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 155 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 164 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
2.1 s
4.1 s
6.2 s
8.3 s
10.3 s
12.4 s
14.5 s
16.5 s
Speed
Reduce unused JavaScript
4.8 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 424 KiB41 files are served with short cache lifetimes, so returning visitors download them again (424 KiB).
Render-blocking requests
1.5 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Main-thread work: 10.3 s
A phone's processor spends 10.3 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 66). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, Google CDN and gotolstoy.com and others), adding 15.1 MB and 2.2 s of main-thread time.
ContentSquare adds 988 ms
988 msContentSquare costs a phone 988 ms of main-thread work and 189 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.
Improve image delivery
400 ms · 495 KiB34 images could be 495 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Google CDN adds 379 ms
379 msGoogle CDN costs a phone 379 ms of main-thread work and 765 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.
gotolstoy.com adds 288 ms
288 msgotolstoy.com costs a phone 288 ms of main-thread work and 874 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.
2,362 HTML elements
The page has 2,362 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 193 ms
193 msGoogle Tag Manager costs a phone 193 ms of main-thread work and 318 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 150 ms
150 msKlaviyo costs a phone 150 ms of main-thread work and 336 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.
Reduce unused CSS
150 ms · 105 KiBAbout 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 126 ms. During a long task the page ignores taps.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.4 s
8.4 sThe first text or image appears after 8.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 25.4 s
25.4 sYour largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 20.4 s
20.4 sVisually, the page fills in at 20.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 33.7 s
33.7 sThe page becomes fully interactive after 33.7 s. Good is under 3.8 s.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 202 ms
202 msReal visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
37 images without width and height
37 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 321 ms
321 msScripts block taps and scrolling for 321 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 146 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user TTFB: 423 ms
423 msReal visitors wait 423 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: 26.6 MB in 505 requests
26.6 MBYour homepage downloads 26.6 MB in 505 requests on a phone: media 19.3 MB (5), scripts 2.9 MB (134) and other files 2.4 MB (278). Under 2 MB keeps phones on slow connections fast.
About 7.5 g of CO₂ per visit
7.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.54 g of CO₂e: 905.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
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.
Links must have discernible text (12 elements)
Links must have discernible text: 12 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
23 images without alt text
23 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.
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 (h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “bras that grow as she grows”). One clear main headline is easier for people and search engines.
Meta description is long (181 characters)
Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.
93 internal links, 14 external
The homepage links to 93 pages on apricotton.ca and 14 external pages.
5 checks passed
Title: 35 characters
Your title is a healthy 35 characters: “Best Tween & Teen Bras - Apricotton”.
Canonical URL set
The canonical URL is https://apricotton.co/.
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://apricotton.co/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (805 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://apricotton.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
7 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.
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.
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 15 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 689 words of copy
The homepage carries about 689 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” and “bras that grow as she grows shop now”.
5 calls to action
The homepage has 5 calls to action, for example “Shop”, “Contact” and “Subscribe to Our Newsletter”.
8 short forms
8 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email 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 Meta Pixel 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.
33 cookies set on arrival
33Opening the homepage sets 33 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 apricotton.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
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 apricotton.ca, including 24 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.