Website review, no card needed
lavignery.fr website review
Visit site (opens in a new tab)Reviewed 25 October 202644 issues · 91 checks
This review found 44 issues worth fixing on lavignery.fr, 14 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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
74C- #86,869 of 124,405 reviewed websitesbeats 26%
- #54,568 of 69,889 online storesbeats 18%
- #73 of 176 PrestaShop storesbeats 54%
Closest competitors among PrestaShop stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 1.0 s |
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 1.0 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 1.0 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 141 ms |
| May 9, 2026 | 138 ms |
| May 16, 2026 | 136 ms |
| May 23, 2026 | 136 ms |
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 136 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 135 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 132 ms |
| Sep 12, 2026 | 131 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 132 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 134 ms |
| Oct 17, 2026 | 133 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.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.1 s
3.6 s
4.1 s
Speed
Render-blocking requests
4.2 s49 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 78). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
500 ms · 110 KiB2 files are served with short cache lifetimes, so returning visitors download them again (110 KiB).
Reduce unused JavaScript
450 ms · 99 KiBAbout 99 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
458 KiB13 images could be 458 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
300 ms · 74 KiBAbout 74 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.
2,196 HTML elements
The page has 2,196 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 28 KiB28 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 136 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
4 third-party services on the page
4 third-party services load with your homepage (Google Maps, skeepers.io and Google Fonts and others), adding 206 KiB and 68 ms of main-thread time.
Minify JavaScript
24 KiB24 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 78 but mobile only 42. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 324 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 1.303
1.303The layout shifts by 1.303 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 6.0 s
6.0 sYour largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Vous devez être majeur pour commander sur le site de La Vig…”.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Time to Interactive: 6.0 s
6.0 sThe page becomes fully interactive after 6.0 s. Good is under 3.8 s.
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 141 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 140 ms
140 msReal visitors wait 140 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 588 ms
588 msReal visitors wait 588 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 145 ms
145 msScripts block the page for only 145 ms while loading. Good is under 200 ms.
Images and page weight
16 images in older formats
16 images (1,001 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.
10 images below the first screen load straight away
10 images further down the page (407 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
56 KiB2 images are downloaded at several times the size a phone draws them, for example 6.jpg at 684 px wide, shown at 113 px. Resized copies would save about 56 KiB.
About 0.5 g of CO₂ per visit
0.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.53 g of CO₂e: 63.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.9 MB in 114 requests
1.9 MBYour homepage downloads 1.9 MB in 114 requests on a phone: images 1.2 MB (43), scripts 364 KiB (39) and fonts 180 KiB (6). That is a lean page.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
72 form fields without a label
72 form fields have no label, so screen readers announce an empty box and autofill guesses.
9 links without text
9 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.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 12 failed. 4 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: “La Vignery - Achat Vin Champagne Whisky Rhum et Bières - La Vignery”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Ça pourrait aussi vous plaire :” and “Offrir le cadeau idéal”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.lavignery.fr/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at lavignery.fr/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
207 internal links, 8 external
The homepage links to 207 pages on lavignery.fr and 8 external pages.
2 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Votre caviste La Vignery, la qualité au meilleur prix : vin, Champagne, whisky, rhum et bière, plus de 3000 références.…”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.lavignery.fr/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,011 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.lavignery.fr/16-univers-bourgogne, which answers with an error. Visitors hit a dead end and search engines drop it.
3 pages without a meta description
https://www.lavignery.fr/reservation, https://www.lavignery.fr/commande and https://www.lavignery.fr/6-biere have 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 147 found) and read each the way a search engine does.
5 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.
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 13 pages that loaded have a <title>.
Best practices
119 small tap targets
119 of 150 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
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.
A 34-field form
Your longest form asks for 34 fields (0 required). Every extra field lowers completion.
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 843 words of copy
The homepage carries about 843 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 1 customer or partner logo.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 lavignery.fr, 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
- PrestaShop
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on lavignery.fr, including 13 speed issues, 6 SEO issues and 4 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.