emvauto.com website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.5 s faster on a phone.

The page goes through 1 redirect before it starts loading, costing about 3.2 s. Link and advertise the final URL directly.

Your mobile performance score is 17 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Google Optimize and Hotjar and others), adding 508 KiB and 254 ms of main-thread time.

Desktop scores 46 but mobile only 17. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 first text or image appears after 14.3 s on a phone. Good is under 1.8 s.

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

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

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

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

The layout shifts by 0.258 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

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

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

Your homepage downloads 4.7 MB in 177 requests on a phone: scripts 3.7 MB (84), stylesheets 353 KiB (22) and other files 227 KiB (42). Under 2 MB keeps phones on slow connections fast.

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

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

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 9 characters: “Xos | EMV”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

A phone browser shows 645 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/6334c9da00f79124428d327f/191/5c5…”.

Chrome logged issues while loading the page (“Cookie”).

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.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

emvauto.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 and Hotjar (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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