Website review, no card needed
alldaecascara.com website review
Visit site (opens in a new tab)Reviewed 3 November 202634 issues · 72 checks
This review found 34 issues worth fixing on alldaecascara.com, 8 of them high impact, across 72 checks. The most urgent: page weight: 13.9 MB in 495 requests. 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
One score from every part of this review. How it works
How it loaded on a phone
2.7 s
5.5 s
8.2 s
11.0 s
13.7 s
16.4 s
19.2 s
21.9 s
Speed
Improve image delivery
400 ms · 1.3 MB10 images could be 1.3 MB 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.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 129 KiBAbout 129 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and okendo.io and others), adding 2.3 MB and 266 ms of main-thread time.
Render-blocking requests
450 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 115 ms
115 msShopify costs a phone 115 ms of main-thread work and 967 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 146 ms
146 msKlaviyo costs a phone 146 ms of main-thread work and 310 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.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 964 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
150 ms · 63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.
Reduce unused CSS
20 ms · 31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 20 ms faster on a phone.
Use efficient cache lifetimes
33 KiB12 files are served with short cache lifetimes, so returning visitors download them again (33 KiB).
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: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.0 s
16.0 sYour largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 25.3 s
25.3 sVisually, the page fills in at 25.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.2 s
6.2 sThe first text or image appears after 6.2 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.4 s
16.4 sThe page becomes fully interactive after 16.4 s. Good is under 3.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 13.9 MB in 495 requests
13.9 MBYour homepage downloads 13.9 MB in 495 requests on a phone: media 9.0 MB (2), images 2.2 MB (29) and other files 1.4 MB (236). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
127 KiB1 image is downloaded at several times the size a phone draws it, for example Coffee_is_a_Fruit_Rollover.png at 1,290 px wide, shown at 118 px. Resized copies would save about 127 KiB.
3 images below the first screen load straight away
3 images further down the page (191 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.9 g of CO₂ per visit
3.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.94 g of CO₂e: 473.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 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 (261 characters)
Your meta description is 261 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.
43 internal links, 2 external
The homepage links to 43 pages on alldaecascara.com and 2 external pages.
7 checks passed
One H1 headline
Your main headline reads: “alldae”.
Title: 50 characters
Your title is a healthy 50 characters: “alldae superfruit soda | lightly caffeinated sodas”.
Canonical URL set
The canonical URL is https://drinkalldae.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization 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://drinkalldae.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (276 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://drinkalldae.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://drinkalldae.com/collections/flavors-2-0 and https://drinkalldae.com/collections/drinks all use the title “Drinks | alldae superfruit soda”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://drinkalldae.com/policies/privacy-policy has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://drinkalldae.com/collections/flavors-2-0 and https://drinkalldae.com/collections/drinks use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://drinkalldae.com/collections/flavors-2-0, whose canonical is https://drinkalldae.com/collections/drinks. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://drinkalldae.com/pages/the-superfruit, https://drinkalldae.com/pages/our-story, https://drinkalldae.com/collections/flavors-2-0, https://drinkalldae.com/pages/store-locator, https://drinkalldae.com/pages/faire and https://drinkalldae.com/collections/drinks and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://drinkalldae.com/pages/store-locator, https://drinkalldae.com/pages/faire and https://drinkalldae.com/pages/contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
2 broken images
2 images failed to load on a phone, for example https://drinkalldae.com/.
2 small tap targets
2 of 8 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 “Failed to load resource: net::ERR_FAILED”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 229 words
The homepage has only about 229 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Our Superfruit Sodas”.
9 calls to action
The homepage has 9 calls to action, for example “Shop Now”, “Buy Wholesale on Faire” and “Shop Our Best Sellers”.
5 short forms
5 short forms (1 field at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and TikTok Pixel (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
19 other companies contacted
Loading the homepage contacts 19 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 alldaecascara.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on alldaecascara.com, including 13 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.