mythinkcarfr.com website review

A phone's processor spends 4.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,401 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

6 long tasks block the main thread while loading, the longest for 321 ms. During a long task the page ignores taps.

Shopify costs a phone 131 ms of main-thread work and 466 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 third-party services load with your homepage (Shopify, Clarity and 506.io and others), adding 763 KiB and 308 ms of main-thread time.

About 211 KiB of JavaScript is downloaded but never used on this page.

6 images could be 120 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 38 KiB of CSS is downloaded but never applied on this page.

7 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need.

12 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Visually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 10.7 s. Good is under 3.8 s.

The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

1 image have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 213 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.1 MB in 170 requests on a phone: images 963 KiB (31), scripts 694 KiB (68) and other files 217 KiB (33). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Serie_ThinkScan.jpg at 640 px wide, shown at 181 px. Resized copies would save about 64 KiB.

1 image (50 KiB) is 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.

1 image further down the page (71 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA commands must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

3 elements hidden from screen readers can still receive keyboard focus.

3 tap targets are too small or too close together to hit reliably with a finger.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

<svg> elements with an img or image role must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

13 form fields have no label, so screen readers announce an empty box and autofill guesses.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Your title is 84 characters, so Google will cut it off around 60: “Scanner Diagnostic Auto Professionnel & Solutions OBD2 | THINKCAR Fran – THINKCAR FR”.

Your meta description is 261 characters; Google truncates after about 160, so the end of your pitch is cut.

Your <h1> is empty.

The homepage links to 174 pages on mythinkcarfr.com and 7 external pages.

There is no https://mythinkcarfr.com/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.

https://mythinkcarfr.com/collections/outils-diagnostics, https://mythinkcarfr.com/collections/serie-thinkcar-thinkscan, https://mythinkcarfr.com/collections/thinkcar-tpms-service, https://mythinkcarfr.com/collections/accessoires and https://mythinkcarfr.com/collections/thinkcar-outils-de-diagnostic have no meta description, so Google writes the search snippet from whatever text it finds.

https://mythinkcarfr.com/collections/outils-diagnostics, https://mythinkcarfr.com/products/thinkscan-689bt-pro-valise-diagnostic-auto, https://mythinkcarfr.com/products/thinkcar-thinkscan-689bt-bidirectional-scan-tool, https://mythinkcarfr.com/products/thinkscan-689-professional-auto-scan-tool, https://mythinkcarfr.com/products/thinkscan-662 and https://mythinkcarfr.com/products/thinkdiag-2 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://mythinkcarfr.com/.

21 of 59 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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 guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 316 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

Opening the homepage sets 9 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.