Website review, no card needed
twinings.fr website review
Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 79 checks
This review found 31 issues worth fixing on twinings.fr, 12 of them high impact, across 79 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
68D- #110,299 of 125,811 reviewed websitesbeats 10%
- #65,467 of 70,268 online storesbeats 5%
- #60,166 of 63,827 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 89 ms |
| May 30, 2026 | 89 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 89 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 90 ms |
| Jul 4, 2026 | 89 ms |
| Jul 11, 2026 | 90 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 100 ms |
| Sep 19, 2026 | 100 ms |
| Sep 26, 2026 | 100 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 97 ms |
| Oct 24, 2026 | 99 ms |
| Oct 31, 2026 | 96 ms |
| Nov 7, 2026 | 96 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
Speed
Reduce unused JavaScript
1.2 s · 207 KiBAbout 207 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
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.
Improve image delivery
600 ms · 1.3 MB19 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 600 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 536 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
400 ms · 117 KiB7 files are served with short cache lifetimes, so returning visitors download them again (117 KiB).
Reduce unused CSS
300 ms · 61 KiBAbout 61 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.
Render-blocking requests
350 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 third-party services on the page
6 third-party services load with your homepage (Optanon, Shopify and Google Tag Manager and others), adding 674 KiB and 320 ms of main-thread time.
Duplicated JavaScript
150 ms · 48 KiB48 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 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: 11 ms
11 msYour server sent the HTML in 11 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.
Real-user CLS: 0.43
0.43For real visitors the layout shifts by 0.43 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Inscrivez-vous à nos emails Entrez dans nos coulisses : jeu…”.
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.388
0.388The layout shifts by 0.388 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 620 ms
620 msScripts block taps and scrolling for 620 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 89 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 106 ms
106 msReal visitors wait 106 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 769 ms
769 msReal visitors wait 769 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.0 MB in 188 requests
4.0 MBYour homepage downloads 4.0 MB in 188 requests on a phone: images 1.9 MB (27), scripts 1.1 MB (52) and other files 742 KiB (91). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
22 KiB1 image is downloaded at several times the size a phone draws it, for example icons-37.png at 390 px wide, shown at 96 px. Resized copies would save about 22 KiB.
About 1.1 g of CO₂ per visit
1.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.13 g of CO₂e: 135.0 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
Interactive controls must not be nested (7 elements)
Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 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 (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “TWININGS – Thés & Infusions: blends créatifs, goûts intenses – twinings.fr”.
2 H1 headlines
There are 2 <h1> headlines (“Vous êtes à un de vous faire plaisir” and “Nouveau Jeu Concours”). One clear main headline is easier for people and search engines.
Structured data has 2 problems
Structured data found (Corporation) but with 2 problems, for example “Corporation: logo is not an absolute URL ("https:files/PNG-KV_HOMEPAGE.png")”.
38 internal links, 12 external
The homepage links to 38 pages on twinings.fr and 12 external pages.
5 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “Découvrez nos thés et infusions TWININGS aux goûts intenses et aux ingrédients audacieux pour une explosion de saveurs …”.
Canonical URL set
The canonical URL is https://twinings.fr/.
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://twinings.fr/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 description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (367 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://twinings.fr/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages share a meta description
https://twinings.fr/pages/ou-nous-trouver, https://twinings.fr/pages/histoire and https://twinings.fr/pages/contact use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "menu-navigation" has already been u…”.
2 checks passed
Tap targets are thumb-sized
38 of 38 tappable elements near the top are at least 24 px.
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 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 451 words of copy
The homepage carries about 451 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 twinings.fr, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder
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
- The footer still says © 2024.
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on twinings.fr, including 17 speed issues, 3 SEO issues and 2 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.