genesis.com website review

50 files are served with short cache lifetimes, so returning visitors download them again (20.8 MB).

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

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

audioeye.com costs a phone 1.7 s of main-thread work and 309 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Google CDN and others), adding 2.6 MB and 3.2 s of main-thread time.

Google Tag Manager costs a phone 851 ms of main-thread work and 984 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 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

12 images could be 382 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Google CDN costs a phone 377 ms of main-thread work and 733 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.

Optanon costs a phone 90 ms of main-thread work and 460 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.

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

Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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.

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 9.9 s on a phone. Good is under 1.8 s.

Your largest element takes 22.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Aerial 3/4 rear driver side view of 2027 Genesis GV80 in da…”.

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

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

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

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

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

Your homepage downloads 32.1 MB in 121 requests on a phone: media 27.6 MB (5), scripts 2.6 MB (32) and images 1.1 MB (35). Under 2 MB keeps phones on slow connections fast.

my27-rg3-0603-v002:1-1 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (262 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.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 8 <h1> headlines (“REFINEMENT YOU CAN FEEL”, “ELECTRIC EXHILARATION” and “FEEL THE THRILL”). One clear main headline is easier for people and search engines.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 280 pages on genesis.com and 24 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.

/us/en/build-and-price/2026/gv60, /us/en/build-and-price/2027/gv60, /us/en/build-and-price/2027/gv60-magma, /us/en/build-and-price/2026/gv70 and /us/en/build-and-price/2027/gv70 all use the title “Build & Price Your (year) Genesis (model) | Genesis USA”. Search engines can't tell which page to show for a search, so each competes with the others.

/us/en/build-and-price/2026/gv60, /us/en/build-and-price/2027/gv60, /us/en/build-and-price/2027/gv60-magma, /us/en/build-and-price/2026/gv70 and /us/en/build-and-price/2027/gv70 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example /us/en/build-and-price/2026/gv60, whose canonical is /us/en/build-and-price/byo-app. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/us/en/build-and-price/2026/gv60, /us/en/build-and-price/2027/gv60, /us/en/build-and-price/2027/gv60-magma, /us/en/build-and-price/2026/gv70 and /us/en/build-and-price/2027/gv70 have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5320778&tm=gtm002&Ver=2&mid=6dff6ac3-cca3-47c2-889b-e29d99b5ff59&bo=1&sid=c59a91c0c5da11f191f5df192ef0b076&vid=c59ab740c5da11f188eae1c53f50134b&vids=1&msclkid=N&pi=918.

4 third-party cookies are 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 “Failed to load resource: net::ERR_FAILED”.

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

Large scripts ship without source maps.

http://genesis.com does not redirect to https, so some visitors land on the insecure version.

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.

Opening https://genesis.com goes through 2 redirects before the homepage loads.

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.

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

genesis.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 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 1,097 words of visible text.

DMARC is set to p=none, so mail pretending to be genesis.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 4 mores (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 30 cookies, 2 of them by other companies (measured from a US location before any click).

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