kvaser.com website review

8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookiebot and others), adding 944 KiB and 607 ms of main-thread time.

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

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

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

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

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

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

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.

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 140 ms to 226 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 2.6 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Advancing connectivity”.

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

Your homepage downloads 2.2 MB in 99 requests on a phone: scripts 1.0 MB (45), media 881 KiB (1) and images 173 KiB (19). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (38 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.62 g of CO₂e: 74.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

28 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements with visible text labels do not have matching accessible names. (13 elements).

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 169 pages on kvaser.com and 20 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/partners, /solutions and /learning-center have no meta description, so Google writes the search snippet from whatever text it finds.

/products and /partners have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

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.

kvaser.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

kvaser.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.

kvaser.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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 9 fields (6 required). Every extra field lowers completion.

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

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, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 9 cookies (measured from a US location before any click).

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