genesis.ca website review

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

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

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

Google Tag Manager costs a phone 2.1 s of main-thread work and 1.9 MB 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.

218 KiB could be saved by minifying JavaScript.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 3.9 MB and 3.4 s of main-thread time.

Google CDN costs a phone 493 ms of main-thread work and 736 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 364 ms. During a long task the page ignores taps.

Facebook costs a phone 267 ms of main-thread work and 281 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.

Google Maps costs a phone 196 ms of main-thread work and 396 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 101 ms of main-thread work and 447 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 96 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.

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

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

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

8 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Side angle of the white Genesis GV90 Coach”.

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

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

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

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

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

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

Your homepage downloads 6.5 MB in 220 requests on a phone: scripts 4.2 MB (52), images 1.6 MB (95) and other files 424 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

5 images further down the page (146 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

There are 3 <h1> headlines (“Start Your Genesis Experience”, “Genesis Canada” and “Born to CreateBorn to Create”). One clear main headline is easier for people and search engines.

11 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 set, so this is minor.

The homepage links to 329 pages on genesis.ca and 101 external pages.

/ca/en/main.html and /ca/en.html all use the title “Genesis Motors Canada | Luxury Sedans & SUVs”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 15 pages by a URL that isn't their canonical one, for example /ca/en.html, whose canonical is /ca/en/main.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/ca/en/models/luxury-suv-genesis/gv60.html and /ca/en/models/luxury-electric-genesis/gv60.html use the same meta description. A description written for each page earns more clicks.

/ca/en.html, /ca/en/models/luxury-suv-genesis/gv70.html and /ca/en/models/luxury-suv-genesis/gv80-coupe-black.html have no <h1> headline, so visitors and search engines get no clear main topic.

/ca/en/models/luxury-suv-genesis/gv80.html, /ca/en/models/luxury-suv-genesis/gv80-black.html, /ca/en/models/luxury-suv-genesis/gv80-coupe.html, /ca/en/models/luxury-suv-genesis/gv80-coupe-black.html, /ca/en/models/luxury-suv-genesis/electrified-gv70.html and /ca/en/models/luxury-sedan-genesis/g70.html and 4 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 136 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=5762233&tm=gtm002&Ver=2&mid=d26eb777-fbcd-40d7-bf1e-fe842878ed4d&bo=1&sid=ce71fba0d82c11f188a46bb80dd8ae53&vid=ce724ea0d82c11f181cbc3fb0d7b3570&vids=1&msclkid=N&pi=918.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Large scripts ship without source maps.

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

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.

Opening https://genesis.ca goes through 3 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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

DMARC is set to p=none, so mail pretending to be genesis.ca is still delivered. Reports are on, so moving to quarantine is the next step.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 mx ip4:69.17.130.0/24 ip4:69.20.234.0/24 ip4:67.71.195.0/26 ip4:211.252.131.195 ip4:211.252.131.231 a:mail.hyund…”.

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, LinkedIn Insight and Meta Pixel and 3 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 25 cookies (measured from a US location before any click).

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