Website review, no card needed
cookanyday.com website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 88 checks
This review found 43 issues worth fixing on cookanyday.com, 13 of them high impact, across 88 checks. The most urgent: main-thread work: 20.9 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
76C- #73,594 of 120,852 reviewed websitesbeats 34%
- #47,388 of 68,414 online storesbeats 26%
- #44,941 of 62,341 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 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.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 193 ms |
| May 23, 2026 | 191 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 189 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 207 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 221 ms |
| Jul 18, 2026 | 221 ms |
| Jul 25, 2026 | 236 ms |
| Aug 1, 2026 | 256 ms |
| Aug 8, 2026 | 263 ms |
| Aug 15, 2026 | 262 ms |
| Aug 22, 2026 | 258 ms |
| Aug 29, 2026 | 244 ms |
| Sep 5, 2026 | 243 ms |
| Sep 12, 2026 | 242 ms |
| Sep 19, 2026 | 244 ms |
| Sep 26, 2026 | 246 ms |
| Oct 3, 2026 | 241 ms |
| Oct 10, 2026 | 260 ms |
| Oct 17, 2026 | 269 ms |
| Oct 24, 2026 | 282 ms |
| Oct 31, 2026 | 289 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.6 s
3.2 s
4.9 s
6.5 s
8.1 s
9.7 s
11.3 s
12.9 s
Speed
Main-thread work: 20.9 s
A phone's processor spends 20.9 s on main-thread work while loading, 11.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 363 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,535 HTML elements
The page has 3,535 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 (Google Tag Manager, alia-prod.com and gotolstoy.com and others), adding 5.6 MB and 4.4 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 910 KiB36 files are served with short cache lifetimes, so returning visitors download them again (910 KiB).
Improve image delivery
500 ms · 746 KiB24 images could be 746 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
alia-prod.com adds 775 ms
775 msalia-prod.com costs a phone 775 ms of main-thread work and 3.3 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.
gotolstoy.com adds 732 ms
732 msgotolstoy.com costs a phone 732 ms of main-thread work and 410 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
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 506 ms. During a long task the page ignores taps.
rebuyengine.com adds 395 ms
395 msrebuyengine.com costs a phone 395 ms of main-thread work and 755 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.
automizely.com adds 343 ms
343 msautomizely.com costs a phone 343 ms of main-thread work and 287 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 · 63 KiBAbout 63 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
58 KiBPolyfills for old browsers add 58 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
28 KiB28 KiB could be saved by minifying JavaScript.
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: 16 ms
16 msYour server sent the HTML in 16 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.
Speed Index: 23.6 s
23.6 sVisually, the page fills in at 23.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.8 s
40.8 sThe page becomes fully interactive after 40.8 s. Good is under 3.8 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tablet/Mobile Image”.
Real-user INP: 218 ms
218 msReal visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 49% slower for real visitors
+49%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 193 ms to 289 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 540 ms
540 msReal visitors wait 540 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.069
0.069The layout barely moves while loading (CLS 0.069, good is under 0.1).
Images and page weight
Page weight: 9.5 MB in 455 requests
9.5 MBYour homepage downloads 9.5 MB in 455 requests on a phone: images 4.6 MB (49), scripts 2.9 MB (140) and other files 1.1 MB (230). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
18 KiB1 image is downloaded at several times the size a phone draws it, for example FALL_TABLESCAPE_8pc_Round_Dish_Set_Kale_Frosted_wFood_sq_1.p at 1,254 px wide, shown at 390 px. Resized copies would save about 18 KiB.
1 image in older formats
1 image (35 KiB) is 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 2.7 g of CO₂ per visit
2.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.70 g of CO₂e: 324.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
52 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: 52 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Anyday Anyday” and “Anydelis on Sale”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
199 internal links, 7 external
The homepage links to 199 pages on cookanyday.com and 7 external pages.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Anyday is a multi-use, plastic-free, and 100% non-toxic kitchen essentials brand that will transform how you spend time…”.
Title: 40 characters
Your title is a healthy 40 characters: “Anyday | Plastic-Free Kitchen Essentials”.
Canonical URL set
The canonical URL is https://cookanyday.com/.
Structured data in place
Structured data found: FAQPage.
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://cookanyday.com/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 (1,929 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://cookanyday.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://cookanyday.com/collections/disney and https://cookanyday.com/products/the-disney-collection all use the title “The Disney Collection – Anyday”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://cookanyday.com/collections/frontpage, https://cookanyday.com/collections/disney, https://cookanyday.com/collections/sets, https://cookanyday.com/collections/round-dishes, https://cookanyday.com/collections/anyday-square-dish and https://cookanyday.com/collections/deep-dishes and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://cookanyday.com/products/14-piece-clear-glass-round-dish-set, https://cookanyday.com/products/12-piece-round-dish-set, https://cookanyday.com/products/8-piece-round-dish-set, https://cookanyday.com/products/8-piece-square-dish-set and https://cookanyday.com/products/4-piece-square-dish-set use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://cookanyday.com/products/8-piece-round-dish-set has 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 58 found) and read each the way a search engine does.
4 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.
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 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
39 of 42 tappable elements near the top are at least 24 px.
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 434 words of copy
The homepage carries about 434 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop the Sale”.
31 calls to action
The homepage has 31 calls to action, for example “Shop All”, “Shop All Dishes” and “Shop All Anydelis”.
5 short forms
5 short forms (3 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 14 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
30 cookies set on arrival
30Opening the homepage sets 30 cookies (measured from a US location before any click).
76 other companies contacted
Loading the homepage contacts 76 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) 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 cookanyday.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 20 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Mntn · Wyllo Formerly Nofraud · Elevar Conversion Tracking · Black Crow Ai That Delivers · Hark Solve Ai · Tolstoy · Ground · Aftership Tracking · Checkmate · Rebuy Personalization Engine · Aftership Returns · Klaviyo Email Marketing Sms · Aftership Personalization · Deliverr Fast Tags · Swishlist · amazonaws.com · cart-bot.net · cloudfront.net · botnot.io · automizely.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
- San Francisco
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 cookanyday.com, including 25 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.