Website review, no card needed
toyota.fr website review
Visit site (opens in a new tab)Reviewed 20 November 202639 issues · 86 checks
This review found 39 issues worth fixing on toyota.fr, 20 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.6 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 4.0 s |
| Nov 7, 2026 | 4.0 s |
| Nov 14, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 453 ms |
| Jun 6, 2026 | 455 ms |
| Jun 13, 2026 | 461 ms |
| Jun 20, 2026 | 472 ms |
| Jun 27, 2026 | 478 ms |
| Jul 4, 2026 | 483 ms |
| Jul 11, 2026 | 486 ms |
| Jul 18, 2026 | 485 ms |
| Jul 25, 2026 | 484 ms |
| Aug 1, 2026 | 487 ms |
| Aug 8, 2026 | 496 ms |
| Aug 15, 2026 | 512 ms |
| Aug 22, 2026 | 528 ms |
| Aug 29, 2026 | 544 ms |
| Sep 5, 2026 | 559 ms |
| Sep 12, 2026 | 562 ms |
| Sep 19, 2026 | 561 ms |
| Sep 26, 2026 | 554 ms |
| Oct 3, 2026 | 554 ms |
| Oct 10, 2026 | 565 ms |
| Oct 17, 2026 | 607 ms |
| Oct 24, 2026 | 702 ms |
| Oct 31, 2026 | 801 ms |
| Nov 7, 2026 | 936 ms |
| Nov 14, 2026 | 1.0 s |
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
Use efficient cache lifetimes
9.6 s · 6.5 MB72 files are served with short cache lifetimes, so returning visitors download them again (6.5 MB).
Reduce unused JavaScript
5.0 s · 937 KiBAbout 937 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Render-blocking requests
4.8 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Improve image delivery
2.5 s · 1.3 MB17 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 2.5 s faster on a phone.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.4 s
A phone's processor spends 8.4 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,344 HTML elements
The page has 3,344 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 (toyota.eu, Kameleoon and askdialog.com and others), adding 10.0 MB and 710 ms of main-thread time.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.
toyota.eu adds 263 ms
263 mstoyota.eu costs a phone 263 ms of main-thread work and 8.4 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.
askdialog.com adds 112 ms
112 msaskdialog.com costs a phone 112 ms of main-thread work and 387 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.
toyota-europe.com adds 46 ms
46 mstoyota-europe.com costs a phone 46 ms of main-thread work and 744 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.
Legacy JavaScript
200 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
150 ms · 53 KiBAbout 53 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 202 ms
202 msYour server sent the HTML in 202 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 INP: 1.7 s
1.7 sReal visitors wait 1.7 s for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 24.6 s
24.6 sYour largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “video-nouvelle-yaris-cross-9-16-sept-2026”.
Time to Interactive: 24.9 s
24.9 sThe page becomes fully interactive after 24.9 s. Good is under 3.8 s.
First Contentful Paint: 7.4 s
7.4 sThe first text or image appears after 7.4 s on a phone. Good is under 1.8 s.
Speed Index: 14.3 s
14.3 sVisually, the page fills in at 14.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 114% slower for real visitors
+114%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 453 ms to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.7 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 491 ms
491 msReal visitors wait 491 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.049
0.049The layout barely moves while loading (CLS 0.049, good is under 0.1).
Images and page weight
Page weight: 11.5 MB in 170 requests
11.5 MBYour homepage downloads 11.5 MB in 170 requests on a phone: media 6.8 MB (1), scripts 2.0 MB (77) and images 1.6 MB (48). Under 2 MB keeps phones on slow connections fast.
12 images far larger than shown
473 KiB12 images are downloaded at several times the size a phone draws them, for example home-page-pro-1600x900-desktop-2026-JTU-Oct.jpg.thumb.1280.1 at 1,280 px wide, shown at 390 px. Resized copies would save about 473 KiB.
3 images below the first screen load straight away
3 images further down the page (372 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (257 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 3.2 g of CO₂ per visit
3.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.25 g of CO₂e: 389.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn'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.
Orphan list items
Some list items are not inside a list.
122 links without text
122 visible links have no text or label, so screen readers cannot say where they go.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (10 elements).
2 checks passed
Every image has alt text
All 75 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
440 internal links, 15 external
The homepage links to 440 pages on toyota.fr and 15 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Bienvenue sur le site de Toyota. Explorez notre gamme de véhicules neufs et occasions, hybrides, entreprise, utilitaire…”.
One H1 headline
Your main headline reads: “Bienvenue, que recherchez-vous?”.
Title: 44 characters
Your title is a healthy 44 characters: “Toyota | Constructeur automobile depuis 1933”.
Canonical URL set
The canonical URL is https://www.toyota.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://www.toyota.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,801 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.toyota.fr/llms.txt (33 KiB, 119 links), a plain-text guide to the site for AI tools.
Other pages
11 pages without an H1
https://www.toyota.fr/vehicules-neufs/aygo-x, https://www.toyota.fr/vehicules-neufs/yaris, https://www.toyota.fr/vehicules-neufs/corolla, https://www.toyota.fr/vehicules-neufs/corolla-touring-sports, https://www.toyota.fr/vehicules-neufs/c-hr-plus-electrique and https://www.toyota.fr/vehicules-neufs/bz4x and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.toyota.fr/vehicules-neufs/rav4, https://www.toyota.fr/vehicules-neufs/mirai and https://www.toyota.fr/vehicules-neufs/gr-yaris took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 177 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.
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.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
20 of 24 tappable elements near the top are at least 24 px.
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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 515 words of copy
The homepage carries about 515 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Start Your Impossible”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 toyota.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Toyota Motor Europe SA
Company
- Employees
- 359,542
- Founded
- 1937
- Headquarters
- Toyota
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on toyota.fr, including 23 speed issues, 1 SEO issue 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.