Website review, no card needed
sodastream.com.ar website review
Visit site (opens in a new tab)Reviewed 4 November 202623 issues · 75 checks
This review found 23 issues worth fixing on sodastream.com.ar, 6 of them high impact, across 75 checks. The most urgent: 14 text elements with low contrast. 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
87B- #7,381 of 105,311 reviewed websitesbeats 90%
- #4,287 of 59,150 online storesbeats 89%
- #4,163 of 53,897 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 248 ms |
| May 23, 2026 | 248 ms |
| May 30, 2026 | 248 ms |
| Jun 6, 2026 | 246 ms |
| Jun 13, 2026 | 257 ms |
| Jun 20, 2026 | 262 ms |
| Jun 27, 2026 | 267 ms |
| Jul 4, 2026 | 276 ms |
| Jul 11, 2026 | 283 ms |
| Jul 18, 2026 | 285 ms |
| Jul 25, 2026 | 272 ms |
| Aug 1, 2026 | 245 ms |
| Aug 8, 2026 | 218 ms |
| Aug 15, 2026 | 203 ms |
| Aug 22, 2026 | 200 ms |
| Aug 29, 2026 | 202 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 205 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 211 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 210 ms |
| Oct 24, 2026 | 208 ms |
| Oct 31, 2026 | 204 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
0.7 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.2 s
Speed
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
250 ms · 591 KiB15 images could be 591 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Render-blocking requests
500 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused CSS
300 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 851 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, 506.io and Klaviyo and others), adding 475 KiB and 300 ms of main-thread time.
Reduce unused JavaScript
150 ms · 167 KiBAbout 167 KiB of JavaScript is downloaded but never used on this page. 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 126 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
56 KiB10 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need.
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
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MAQUINA DE SODA PACK TERRA”.
Time to Interactive: 8.6 s
8.6 sThe page becomes fully interactive after 8.6 s. Good is under 3.8 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
10 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 701 ms
701 msReal visitors wait 701 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 248 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 74 ms
74 msScripts block the page for only 74 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 211 requests
2.6 MBYour homepage downloads 2.6 MB in 211 requests on a phone: images 1.1 MB (28), other files 660 KiB (78) and scripts 633 KiB (61). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
60 KiB1 image is downloaded at several times the size a phone draws it, for example Megapack_Rendimiento_Terra_Negro_b9672279-d94b-44b0-9f07-f44 at 1,000 px wide, shown at 158 px. Resized copies would save about 60 KiB.
About 0.8 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 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
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “SodaStream Oficial: Maquinas para hacer soda – Sodastream Argentina”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
48 internal links, 14 external
The homepage links to 48 pages on sodastream.com.ar and 14 external pages.
6 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Hacé tu soda en casa en pocos segundos. Encontrá Máquinas, Botellas, Cilindros y Recambios en nuestra tienda oficial de…”.
One H1 headline
Your main headline reads: “SodaStream Argentina: máquinas para hacer soda en casa, cilindros de CO₂ y botellas”.
Canonical URL set
The canonical URL is https://www.sodastream.com.ar/.
Structured data in place
Structured data found: OnlineStore 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://www.sodastream.com.ar/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and description; logo and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,177 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.sodastream.com.ar/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.sodastream.com.ar/policies/terms-of-service has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
6 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 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
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “preDataLayer is not defined”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
20 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 1,530 words of copy
The homepage carries about 1,530 words of visible text.
3 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
2 trackers load before any consent
2Before 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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 3 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.
21 other companies contacted
Loading the homepage contacts 21 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 sodastream.com.ar, 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
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on sodastream.com.ar, including 9 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.