Website review, no card needed

drinkdesoi.com logo

drinkdesoi.com website review

Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 93 checks

This review found 42 issues worth fixing on drinkdesoi.com, 12 of them high impact, across 93 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.8 s1.5 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.3 s
Jun 20, 20263.4 s
Jun 27, 20263.1 s
Jul 4, 20262.7 s
Jul 11, 20262.3 s
Jul 18, 20261.9 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.2 s
Oct 10, 20262.0 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
222 ms147 msMay 16Oct 31196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026163 ms
May 23, 2026162 ms
May 30, 2026169 ms
Jun 6, 2026166 ms
Jun 13, 2026156 ms
Jun 20, 2026162 ms
Jun 27, 2026163 ms
Jul 4, 2026177 ms
Jul 11, 2026188 ms
Jul 18, 2026194 ms
Jul 25, 2026203 ms
Aug 1, 2026197 ms
Aug 8, 2026196 ms
Aug 15, 2026204 ms
Aug 22, 2026198 ms
Aug 29, 2026205 ms
Sep 5, 2026213 ms
Sep 12, 2026206 ms
Sep 19, 2026207 ms
Sep 26, 2026204 ms
Oct 3, 2026203 ms
Oct 10, 2026200 ms
Oct 17, 2026195 ms
Oct 24, 2026188 ms
Oct 31, 2026196 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

Full-page screenshot of drinkdesoi.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drinkdesoi.com at 1.6 s1.6 s
  2. drinkdesoi.com at 3.3 s3.3 s
  3. drinkdesoi.com at 4.9 s4.9 s
  4. drinkdesoi.com at 6.6 s6.6 s
  5. drinkdesoi.com at 8.2 s8.2 s
  6. drinkdesoi.com at 9.8 s9.8 s
  7. drinkdesoi.com at 11.5 s11.5 s
  8. drinkdesoi.com at 13.1 s13.1 s

Speed

14 to fix37
  • Use efficient cache lifetimes

    10.6 s · 2.0 MB

    49 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

  • Reduce unused JavaScript

    6.9 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.

  • Main-thread work: 16.0 s

    A phone's processor spends 16.0 s on main-thread work while loading, 7.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37. 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 (Google Tag Manager, lets.shop and alia-prod.com and others), adding 3.9 MB and 3.7 s of main-thread time.

  • Google Tag Manager adds 881 ms

    881 ms

    Google Tag Manager costs a phone 881 ms of main-thread work and 703 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

    950 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • Legacy JavaScript

    800 ms · 119 KiB

    Polyfills for old browsers add 119 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 800 ms faster on a phone.

  • lets.shop adds 578 ms

    578 ms

    lets.shop costs a phone 578 ms of main-thread work and 352 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.

  • alia-prod.com adds 540 ms

    540 ms

    alia-prod.com costs a phone 540 ms of main-thread work and 448 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 551 ms. During a long task the page ignores taps.

  • Shopify adds 459 ms

    459 ms

    Shopify costs a phone 459 ms of main-thread work and 817 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 454 ms

    454 ms

    rebuyengine.com costs a phone 454 ms of main-thread work and 773 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,795 HTML elements

    The page has 2,795 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    244 KiB

    9 images could be 244 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    150 ms · 56 KiB

    About 56 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.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Minify CSS

    10 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    12 KiB

    12 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.

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 20 ms

    20 ms

    Your server sent the HTML in 20 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix33
  • 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.

  • Largest Contentful Paint: 47.3 s

    47.3 s

    Your largest element takes 47.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “De Soi”.

  • Speed Index: 16.3 s

    16.3 s

    Visually, the page fills in at 16.3 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 49.0 s

    49.0 s

    The page becomes fully interactive after 49.0 s. Good is under 3.8 s.

  • Total Blocking Time: 2.2 s

    2.2 s

    Scripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 255 ms

    255 ms

    Real visitors wait 255 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.22

    0.22

    For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 18% slower for real visitors

    +18%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 163 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 1.2 s

    1.2 s

    Real visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 740 ms

    740 ms

    Real visitors wait 740 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 38% faster for real visitors

    -38%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.007

    0.007

    The layout barely moves while loading (CLS 0.007, good is under 0.1).

Images and page weight

1 to fix33
  • Page weight: 8.1 MB in 494 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 494 requests on a phone: scripts 4.0 MB (187), images 2.1 MB (42) and other files 950 KiB (196). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.29 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.29 g of CO₂e: 275.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 9090
  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (1 element).

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 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.

  • 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.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 79 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10092
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 119 internal links, 19 external

    The homepage links to 119 pages on drinkdesoi.com and 19 external pages.

6 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Discover De Soi's non-alcoholic aperitifs, crafted with botanicals & bold flavors for a refreshing & mindful drinking e…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “De Soi | Non-alcoholic cocktails made with natural adaptogens”.

  • Canonical URL set

    The canonical URL is https://drinkdesoi.com/.

  • Structured data in place

    Structured data found: OnlineStore, Organization, Person, WebPage and WebSite.

  • 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://drinkdesoi.com/sitemap.xml.

AI search readiness

100
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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

    The site publishes https://drinkdesoi.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://drinkdesoi.com/products/st-moritz-mule-cocktail and https://drinkdesoi.com/products/haute-margarita-cocktail are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 1 page without a meta description

    https://drinkdesoi.com/collections/party-bundles has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://drinkdesoi.com/collections/party-bundles and https://drinkdesoi.com/pages/find-us 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 42 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 92100
  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    17 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix70
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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.

  • Only about 16 words

    The homepage has only about 16 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop All”, “Subscribe” and “Shop”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 50 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • 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 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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

    15

    Opening the homepage sets 15 cookies, 11 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 drinkdesoi.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 29 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Consentmo Gdpr · Rebuy Personalization Engine · Elevar Conversion Tracking · Onward · Lucky Orange · Instafeed · Accentuate · Okendo · Microsoft Clarity · Triplewhale · Klaviyo Email Marketing Sms · Fermat · Region Restrictions · Gdpr Backpack · Trakt · Gift Box Builder · Rediem · hulkapps.com · b-cdn.net · nfcube.com · retention.com · gorgias.chat · shareasale.com · mailchimp.com · chimpstatic.com · rebuyengine.com · octaneai.com · 9gtb.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
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Founded
2022
Headquarters
Los Angeles

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 drinkdesoi.com, including 22 speed issues, 2 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25