Website review, no card needed
dynveo.fr website review
Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 87 checks
This review found 38 issues worth fixing on dynveo.fr, 14 of them high impact, across 87 checks. The most urgent: main-thread work: 16.9 s. 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
73C- #91,503 of 123,862 reviewed websitesbeats 23%
- #57,024 of 69,698 online storesbeats 15%
- #53,349 of 63,406 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 191 ms |
| May 23, 2026 | 195 ms |
| May 30, 2026 | 200 ms |
| Jun 6, 2026 | 205 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 211 ms |
| Jun 27, 2026 | 213 ms |
| Jul 4, 2026 | 215 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 220 ms |
| Jul 25, 2026 | 218 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 224 ms |
| Aug 22, 2026 | 228 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 229 ms |
| Sep 12, 2026 | 229 ms |
| Sep 19, 2026 | 230 ms |
| Sep 26, 2026 | 233 ms |
| Oct 3, 2026 | 236 ms |
| Oct 10, 2026 | 238 ms |
| Oct 17, 2026 | 239 ms |
| Oct 24, 2026 | 235 ms |
| Oct 31, 2026 | 229 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
Main-thread work: 16.9 s
A phone's processor spends 16.9 s on main-thread work while loading, 9.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Hotjar adds 1.1 s
1.1 sHotjar costs a phone 1.1 s of main-thread work and 280 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7,200 HTML elements
The page has 7,200 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Hotjar, JSDelivr CDN and Shopify and others), adding 1.8 MB and 3.2 s of main-thread time.
Reduce unused JavaScript
450 ms · 793 KiBAbout 793 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 957 ms. During a long task the page ignores taps.
Render-blocking requests
750 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Use efficient cache lifetimes
150 ms · 516 KiB23 files are served with short cache lifetimes, so returning visitors download them again (516 KiB).
JSDelivr CDN adds 523 ms
523 msJSDelivr CDN costs a phone 523 ms of main-thread work and 443 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.
Shopify adds 397 ms
397 msShopify costs a phone 397 ms of main-thread work and 447 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.
TikTok adds 305 ms
305 msTikTok costs a phone 305 ms of main-thread work and 157 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.
Clarity adds 290 ms
290 msClarity costs a phone 290 ms of main-thread work and 28 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
223 KiB11 images could be 223 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
43 KiBPolyfills for old browsers add 43 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
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: 9 ms
9 msYour server sent the HTML in 9 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.
Time to Interactive: 26.2 s
26.2 sThe page becomes fully interactive after 26.2 s. Good is under 3.8 s.
Total Blocking Time: 3.5 s
3.5 sScripts block taps and scrolling for 3.5 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video”.
Real-user INP: 304 ms
304 msReal visitors wait 304 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 191 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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 CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 799 ms
799 msReal visitors wait 799 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 528 requests
5.9 MBYour homepage downloads 5.9 MB in 528 requests on a phone: scripts 2.3 MB (110), media 1.6 MB (1) and other files 984 KiB (358). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
shilajit-ingredient.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).
7 images in older formats
7 images (492 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 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.2 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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
2 checks passed
Every image has alt text
All 129 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 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.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
447 internal links, 7 external
The homepage links to 447 pages on dynveo.fr and 7 external pages.
6 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Découvrez nos compléments alimentaires hautement concentrés en principes actifs. Produits naturels, bio, sans additifs …”.
Title: 53 characters
Your title is a healthy 53 characters: “Dynveo : Laboratoire français expert en nutraceutique”.
Canonical URL set
The canonical URL is https://www.dynveo.fr/.
Structured data in place
Structured data found: Organization, WebPage 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.dynveo.fr/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.dynveo.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.
3 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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (4,062 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 173 found) and read each the way a search engine does.
7 checks passed
Linked pages load
4 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 4 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 4 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187107796&tm=gtm002&Ver=2&mid=adc7c28c-750d-4208-b6c9-0716ca2bf729&bo=3&sid=95187de0d87511f19d2171e2f11fa8d2&vid=951889d0d87511f199ef9de33b2669ac&vids=0&msclkid=N&pi=9.
11 small tap targets
11 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “mm-faq-dropdown: data-header ou data-content manquant”.
Missing source maps
Large scripts ship without source maps.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 935 words of copy
The homepage carries about 935 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “SHOP” and “Contact”.
90 short forms
90 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity, Hotjar and TikTok Pixel.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 6 mores (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.
35 cookies set on arrival
35Opening the homepage sets 35 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.
44 other companies contacted
Loading the homepage contacts 44 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 dynveo.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yotpo Loyalty Rewards · Yotpo Product Reviews · Addingwell · Klaviyo Email Marketing Sms · Wisepops Popup Builder Cro · Digital Appointments · Essential Post Purchase Upsell · Axeptio · rechargecdn.com · dpd.fr · jsdelivr.net
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
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on dynveo.fr, including 21 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.