Website review, no card needed
touring.be website review
Visit site (opens in a new tab)Reviewed 28 October 202630 issues · 78 checks
This review found 30 issues worth fixing on touring.be, 7 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 171 ms |
| May 16, 2026 | 171 ms |
| May 23, 2026 | 163 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 175 ms |
| Jul 4, 2026 | 177 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 177 ms |
| Aug 1, 2026 | 176 ms |
| Aug 8, 2026 | 176 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 177 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 175 ms |
| Sep 26, 2026 | 175 ms |
| Oct 3, 2026 | 176 ms |
| Oct 10, 2026 | 175 ms |
| Oct 17, 2026 | 176 ms |
| Oct 24, 2026 | 177 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
Improve image delivery
1.8 s · 668 KiB7 images could be 668 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 69
69/100Your mobile performance score is 69 (desktop: 44). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 226 KiB69 files are served with short cache lifetimes, so returning visitors download them again (226 KiB).
Reduce unused CSS
300 ms · 62 KiBAbout 62 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,336 HTML elements
The page has 2,336 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, piwik.pro and cdn-cookieyes.com and others), adding 341 KiB and 268 ms of main-thread time.
Reduce unused JavaScript
150 ms · 139 KiBAbout 139 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 114 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 480 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
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: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Une femme au volant tend une clé de voiture vers l’extérieu…”.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 846 ms
846 msReal visitors wait 846 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 171 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 160 ms
160 msReal visitors wait 160 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.
Total Blocking Time: 186 ms
186 msScripts block the page for only 186 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.4 MB in 85 requests
2.4 MBYour homepage downloads 2.4 MB in 85 requests on a phone: images 1.0 MB (48), fonts 944 KiB (12) and scripts 405 KiB (13). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (811 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.
9 images below the first screen load straight away
9 images further down the page (862 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.69 g of CO₂e: 82.8 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
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 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 3 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 (WebPage and WebSite) but with 1 problem, for example “WebPage: breadcrumb is an empty list”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
246 internal links, 9 external
The homepage links to 246 pages on touring.be and 9 external pages.
6 checks passed
Meta description: 101 characters
Your meta description is 101 characters: “En Belgique ou à l’étranger, soyez couverts 7j/7, 24h/24, lors de tous vos déplacements avec Touring.”.
One H1 headline
Your main headline reads: “Une voiture d’occasion ? Oui ! Les mauvaises surprises ? Non !”.
Title: 53 characters
Your title is a healthy 53 characters: “Touring | Assistances dépannage et assurances voyages”.
Canonical URL set
The canonical URL is https://www.touring.be/fr.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.touring.be/sitemap.xml.
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.touring.be/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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,324 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.touring.be/fr/panne, https://www.touring.be/fr/touring-club, https://www.touring.be/fr/carselect and https://www.touring.be/fr/contact have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.touring.be/fr/assist, whose canonical is https://www.touring.be/fr/assist/default/flowSelection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.touring.be/fr/assist has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.touring.be/fr/assist has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www.touring.be/fr/carselect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 156 found) and read each the way a search engine does.
4 checks passed
Linked pages load
8 pages of 15 loaded without an error (the rest turned automated requests away).
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 8 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
198 of 214 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 1,310 words of copy
The homepage carries about 1,310 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Apply”.
5 calls to action
The homepage has 5 calls to action, for example “Contact” and “Apply”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 3 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) 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).
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
Consent tool: CookieYes
A consent management tool (CookieYes) 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 touring.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Google Cloud
Company
- Founded
- 1895
- Headquarters
- Brussels
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on touring.be, including 14 speed issues and 3 SEO issues. 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.