Website review, no card needed
armanddebrignac.com website review
Visit site (opens in a new tab)Reviewed 5 November 202637 issues · 82 checks
This review found 37 issues worth fixing on armanddebrignac.com, 14 of them high impact, across 82 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 117 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 122 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 132 ms |
| Aug 1, 2026 | 140 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 151 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 155 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 186 ms |
| Sep 26, 2026 | 160 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 148 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 146 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
4.1 s
8.2 s
12.3 s
16.4 s
20.5 s
24.5 s
28.6 s
32.7 s
Speed
Reduce unused JavaScript
5.4 s · 946 KiBAbout 946 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.
Use efficient cache lifetimes
2.3 s · 433 KiB10 files are served with short cache lifetimes, so returning visitors download them again (433 KiB).
Mobile performance score: 39
39/100Your mobile performance score is 39. 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, Accessibe Accessibility Overlay and bottlenexus.com and others), adding 2.1 MB and 1.0 s of main-thread time.
Google Tag Manager adds 638 ms
638 msGoogle Tag Manager costs a phone 638 ms of main-thread work and 928 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
450 ms12 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.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
workers.dev adds 49 ms
49 msworkers.dev costs a phone 49 ms of main-thread work and 453 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 228 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 54 KiBAbout 54 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.
Improve image delivery
150 ms · 23 KiB1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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
15 KiBPolyfills for old browsers add 15 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
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
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: 27.6 s
27.6 sYour largest element takes 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Armand de Brignac Champagne”.
Speed Index: 32.9 s
32.9 sVisually, the page fills in at 32.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 27.6 s
27.6 sThe page becomes fully interactive after 27.6 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user INP: 364 ms
364 msReal visitors wait 364 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 117 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.214
0.214The layout shifts by 0.214 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 408 ms
408 msScripts block taps and scrolling for 408 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 698 ms
698 msReal visitors wait 698 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 24.9 MB in 131 requests
24.9 MBYour homepage downloads 24.9 MB in 131 requests on a phone: media 17.3 MB (4), images 5.2 MB (36) and scripts 1.9 MB (41). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
13 images in older formats
13 images (2.8 MB) 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.
An image on the first screen is lazy-loaded
crudropdown-708x1024.png 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).
1 image below the first screen load straight away
1 image further down the page (175 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 7.1 g of CO₂ per visit
7.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.07 g of CO₂e: 848.3 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.
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.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 44 images in the HTML carry an alt attribute.
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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (28 characters)
Your title is only 28 characters: “Homepage - Armand De Brignac”. Between 30 and 65 characters leaves room to say what you do and for whom.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
53 internal links, 2 external
The homepage links to 53 pages on armanddebrignac.com and 2 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “13 generations of wine growing and a true passion for the art of champagne making. Discover Champagne Armand de Brignac…”.
Canonical URL set
The canonical URL is https://armanddebrignac.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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.
XML sitemap found
Your XML sitemap is reachable at https://armanddebrignac.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 (614 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://armanddebrignac.com/llms.txt (1 KiB, 13 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://armanddebrignac.com/fr/qualites-et-caracteristiques-environnementales, which answers with an error. Visitors hit a dead end and search engines drop it.
14 pages without a meta description
https://armanddebrignac.com/about-us, https://armanddebrignac.com/our-craft, https://armanddebrignac.com/our-prestige-cuvees, https://armanddebrignac.com/products/brut-gold, https://armanddebrignac.com/products/rose and https://armanddebrignac.com/products/brut-gold-limited-edition-green and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://armanddebrignac.com/about-us, https://armanddebrignac.com/our-craft, https://armanddebrignac.com/our-prestige-cuvees, https://armanddebrignac.com/products/brut-gold, https://armanddebrignac.com/products/rose and https://armanddebrignac.com/products/brut-gold-limited-edition-green and 8 others 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 17 found) and read each the way a search engine does.
4 checks passed
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
24 small tap targets
24 of 74 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
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 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 640 words of copy
The homepage carries about 640 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: “SHOP NOW” and “Toggle Shop Now submenu”.
10 calls to action
The homepage has 10 calls to action, for example “Shop Now”, “Learn more” and “Learn More”.
3 short forms
3 short forms (5 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and 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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
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.
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 armanddebrignac.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- GoDaddy.com, LLC
Company
- Founded
- 2006
- Headquarters
- France
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on armanddebrignac.com, including 20 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.