Website review, no card needed
greenwhey.com website review
Visit site (opens in a new tab)Reviewed 9 November 202623 issues · 96 checks
This review found 23 issues worth fixing on greenwhey.com, 7 of them high impact, across 96 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
86B- #8,000 of 83,437 reviewed websitesbeats 87%
- #4,424 of 41,883 online storesbeats 85%
- #4,267 of 37,243 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.4 s |
| Jun 27, 2026 | 4.6 s |
| Jul 4, 2026 | 4.6 s |
| Jul 11, 2026 | 4.6 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 184 ms |
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 193 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 200 ms |
| Jul 11, 2026 | 201 ms |
| Jul 18, 2026 | 203 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 201 ms |
| Aug 8, 2026 | 203 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 190 ms |
| Sep 12, 2026 | 177 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 166 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 162 ms |
| Oct 17, 2026 | 160 ms |
| Oct 24, 2026 | 160 ms |
| Oct 31, 2026 | 160 ms |
| Nov 7, 2026 | 156 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.2 s
2.4 s
3.6 s
4.9 s
6.1 s
7.3 s
8.5 s
9.7 s
greenwhey.com does not allow embedding, so this is Google's rendering of the page.
Speed
Reduce unused JavaScript
1.1 s · 285 KiBAbout 285 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.0 s 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 (Shopify, Klaviyo and Google Tag Manager and others), adding 2.2 MB and 818 ms of main-thread time.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Shopify adds 526 ms
526 msShopify costs a phone 526 ms of main-thread work and 1.5 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.
Klaviyo adds 153 ms
153 msKlaviyo costs a phone 153 ms of main-thread work and 313 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
178 KiB4 images could be 178 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Use efficient cache lifetimes
32 KiB5 files are served with short cache lifetimes, so returning visitors download them again (32 KiB).
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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.
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
Time to Interactive: 17.3 s
17.3 sThe page becomes fully interactive after 17.3 s. Good is under 3.8 s.
Largest Contentful Paint: 6.9 s
6.9 sYour largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 248 ms
248 msScripts block taps and scrolling for 248 ms in total while the page loads. Good is under 200 ms.
9 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 161 ms
161 msReal visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 792 ms
792 msReal visitors wait 792 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 184 ms to 156 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 59% faster for real visitors
-59%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 3.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 140 requests
2.4 MBYour homepage downloads 2.4 MB in 140 requests on a phone: images 1,022 KiB (23), scripts 976 KiB (80) and fonts 303 KiB (8). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
banniere_petite-CollageneMatcha.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images in older formats
2 images (147 KiB) are 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 0.7 g of CO₂ per visit
0.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.68 g of CO₂e: 82.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
48 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: 48 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
113 internal links, 3 external
The homepage links to 113 pages on greenwhey.com and 3 external pages.
8 checks passed
Meta description: 119 characters
Your meta description is 119 characters: “Découvrez notre sélection de whey bio, protéines bio et compléments alimentaires clean, sourcés et fabriqués en Europe.”.
One H1 headline
Your main headline reads: “greenwhey”.
Title: 54 characters
Your title is a healthy 54 characters: “Whey Bio, Protéines Bio & Compléments Alimentaires Bio”.
Canonical URL set
The canonical URL is https://greenwhey.com/.
Structured data in place
Structured data found: 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://greenwhey.com/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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (749 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (8 KiB, 51 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
/collections/tous-les-packs 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 53 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
29 small tap targets
29 of 56 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
8 checks passed
Served over HTTPS
The homepage is served over HTTPS (greenwhey.com).
Valid certificate (50 days left)
The certificate from Let's Encrypt · YE2 verifies for greenwhey.com and is valid for another 50 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://greenwhey.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 43 links work
All 43 links checked from your homepage (40 internal, 3 external) answered without errors.
Domain and trust
No CAA record
greenwhey.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
greenwhey.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 17 years old
17 yearsgreenwhey.com was registered in Nov 2008 through Gandi SAS. An established domain carries more trust with email providers and search engines.
Registered until Nov 2027
greenwhey.com is registered until Nov 2027.
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.
Thin social proof
Social proof on the homepage: “400K clients”. Pairing it with named testimonials or customer logos makes it far more convincing.
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 533 words of copy
The homepage carries about 533 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be greenwhey.com is still delivered. Reports are on, so moving to quarantine is the next step.
Email authentication score: 70/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:shops.shopify.com include:mailgun.org include:_spf.google.com ~all”.
DKIM signing found
A DKIM key is published (selector “google”), so receivers can verify mail really came from you.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Pinterest Tag and Snap 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Apps on your store
No apps were seen in the code your storefront loads.
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
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- Framework
- React
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Company
- Founded
- 2015
- Headquarters
- Lyon
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 greenwhey.com, including 11 speed 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.