inemotion.com website review

About 624 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

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

Your mobile performance score is 66 (desktop: 62). Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (Google Tag Manager, Hubspot and cookiefirst.com and others), adding 1.1 MB and 748 ms of main-thread time.

1 image could be 137 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

Google Tag Manager costs a phone 514 ms of main-thread work and 681 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.

About 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

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

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

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.

Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 270 ms in total while the page loads. Good is under 200 ms.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.2 MB in 82 requests on a phone: scripts 1.1 MB (25), images 628 KiB (28) and fonts 341 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Untitled-design-4-1-1.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 165 KiB.

3 images (433 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.

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

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 2 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: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “In&motion | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“In&motion engineers smart wearable airbag systems” and “In&motion”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, WebPage and WebSite) but with 1 problem, for example “BreadcrumbList: itemListElement is an empty list”.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 97 pages on inemotion.com and 22 external pages.

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.

There is no /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.

/en and / all use the title “In&motion | Home”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/, /it, /de, /es, /ja and /en-us and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/fr and /fr-ca use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is /en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/myinemotion/en/moto-membership has no <h1> headline, so visitors and search engines get no clear main topic.

/ja 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.

/, /fr, /it, /de, /es and /ja and 8 others took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

2 links go through two or more redirects, for example https://www.inemotion.com/myinemotion/en/moto-membership.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

inemotion.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

inemotion.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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 519 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 8 cookies (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.