Website review, no card needed

hyundaiusa.com logo

hyundaiusa.com website review

Visit site (opens in a new tab)Reviewed 12 October 202654 issues · 97 checks

This review found 54 issues worth fixing on hyundaiusa.com, 24 of them high impact, across 97 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
9.2 s5.6 sApr 18Oct 38.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20266.0 s
Apr 25, 20266.2 s
May 2, 20266.4 s
May 9, 20266.7 s
May 16, 20267.1 s
May 23, 20267.7 s
May 30, 20268.2 s
Jun 6, 20268.6 s
Jun 13, 20268.7 s
Jun 20, 20268.6 s
Jun 27, 20268.3 s
Jul 4, 20268.3 s
Jul 11, 20268.2 s
Jul 18, 20268.4 s
Jul 25, 20268.5 s
Aug 1, 20268.6 s
Aug 8, 20268.6 s
Aug 15, 20268.6 s
Aug 22, 20268.5 s
Aug 29, 20268.5 s
Sep 5, 20268.6 s
Sep 12, 20268.6 s
Sep 19, 20268.8 s
Sep 26, 20268.7 s
Oct 3, 20268.6 s
Real-visitor tap response (INP)75th percentile, phones
525 ms430 msApr 18Oct 3505 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026462 ms
Apr 25, 2026461 ms
May 2, 2026460 ms
May 9, 2026461 ms
May 16, 2026468 ms
May 23, 2026484 ms
May 30, 2026503 ms
Jun 6, 2026512 ms
Jun 13, 2026514 ms
Jun 20, 2026497 ms
Jun 27, 2026478 ms
Jul 4, 2026478 ms
Jul 11, 2026475 ms
Jul 18, 2026481 ms
Jul 25, 2026481 ms
Aug 1, 2026472 ms
Aug 8, 2026465 ms
Aug 15, 2026449 ms
Aug 22, 2026441 ms
Aug 29, 2026453 ms
Sep 5, 2026467 ms
Sep 12, 2026489 ms
Sep 19, 2026510 ms
Sep 26, 2026510 ms
Oct 3, 2026505 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of hyundaiusa.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hyundaiusa.com at 1.5 s1.5 s
  2. hyundaiusa.com at 3.0 s3.0 s
  3. hyundaiusa.com at 4.4 s4.4 s
  4. hyundaiusa.com at 5.9 s5.9 s
  5. hyundaiusa.com at 7.4 s7.4 s
  6. hyundaiusa.com at 8.9 s8.9 s
  7. hyundaiusa.com at 10.4 s10.4 s
  8. hyundaiusa.com at 11.8 s11.8 s

Speed

16 to fix27
  • Use efficient cache lifetimes

    8.1 s · 4.5 MB

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

  • Reduce unused JavaScript

    5.3 s · 2.6 MB

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

  • audioeye.com adds 1.6 s

    1.6 s

    audioeye.com costs a phone 1.6 s of main-thread work and 328 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.

  • Main-thread work: 13.4 s

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 27

    27/100

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

  • 4,100 HTML elements

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

  • 8 third-party services on the page

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

  • Improve image delivery

    800 ms · 2.6 MB

    25 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    900 ms · 350 KiB

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

  • Google Tag Manager adds 955 ms

    955 ms

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

  • Tealium adds 611 ms

    611 ms

    Tealium costs a phone 611 ms of main-thread work and 213 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.

  • Legacy JavaScript

    300 ms · 153 KiB

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

  • Facebook adds 355 ms

    355 ms

    Facebook costs a phone 355 ms of main-thread work and 276 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 CDN adds 291 ms

    291 ms

    Google CDN costs a phone 291 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.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 163 ms

    163 ms

    Your server sent the HTML in 163 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 5.8 s

    5.8 s

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

  • Real-user FCP: 5.3 s

    5.3 s

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

  • First Contentful Paint: 11.7 s

    11.7 s

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

  • Largest Contentful Paint: 33.9 s

    33.9 s

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

  • Speed Index: 24.3 s

    24.3 s

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

  • Time to Interactive: 55.1 s

    55.1 s

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

  • Total Blocking Time: 2.2 s

    2.2 s

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

  • Real-user INP: 381 ms

    381 ms

    Real visitors wait 381 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 42% slower for real visitors

    +42%

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

  • 11 images without width and height

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

3 checks passed
  • Real-user CLS: 0.06

    0.06

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

  • Real-user TTFB: 438 ms

    438 ms

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

  • Cumulative Layout Shift: 0.049

    0.049

    The layout barely moves while loading (CLS 0.049, good is under 0.1).

Images and page weight

4 to fix33
  • Page weight: 13.0 MB in 305 requests

    13.0 MB

    Your homepage downloads 13.0 MB in 305 requests on a phone: scripts 5.5 MB (109), images 4.9 MB (71) and other files 1.7 MB (84). Under 2 MB keeps phones on slow connections fast.

  • 17 images far larger than shown

    2.1 MB

    17 images are downloaded at several times the size a phone draws them, for example 2027-santa-fe-incentives-v3-2up-tout-375 at 1,440 px wide, shown at 272 px. Resized copies would save about 2.1 MB.

  • 20 images below the first screen load straight away

    20 images further down the page (2.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images in older formats

    5 images (778 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.

  • About 3.7 g of CO₂ per visit

    3.70 g

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

Accessibility

8 to fixGoogle 9090
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • Interactive controls must not be nested (13 elements)

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

  • 3 images without alt text

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

  • All page content should be contained by landmarks (19 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 7783
  • No H1 headline

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

  • No structured data

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

  • 17 links with vague text

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 87 internal links, 0 external

    The homepage links to 87 pages on hyundaiusa.com and 0 external pages.

5 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Welcome to the official site of Hyundai USA. Explore cars, SUVs, electric vehicles, features, offers, inventory and dea…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Hyundai USA: Cars, SUVs, & Electric Vehicles | Official Site”.

  • Canonical URL set

    The canonical URL is https://www.hyundaiusa.com/us/en.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.hyundaiusa.com/content/dam/hyundai/us/com/xml/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    5%

    A phone browser shows 1,170 words, but the HTML your server sends has only 64. 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.

  • No Organization structured data

    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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • llms.txt published

    The site publishes https://www.hyundaiusa.com/llms.txt (16 KiB, 60 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 3 pages without a meta description

    https://www.hyundaiusa.com/us/en/inventory-search/vehicles-list, https://www.hyundaiusa.com/us/en/build and https://www.hyundaiusa.com/us/en/build/options have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.hyundaiusa.com/us/en/electrified, whose canonical is https://www.hyundaiusa.com/us/en/hybrid-and-ev. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://www.hyundaiusa.com/us/en/inventory-search/vehicles-list, https://www.hyundaiusa.com/us/en/build, https://www.hyundaiusa.com/us/en/request-quote, https://www.hyundaiusa.com/us/en/dealer-locator, https://www.hyundaiusa.com/us/en/vehicles and https://www.hyundaiusa.com/us/en/certified-used-vehicles and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://www.hyundaiusa.com/us/en/inventory-search/vehicles-list, https://www.hyundaiusa.com/us/en/build, https://www.hyundaiusa.com/us/en/request-quote, https://www.hyundaiusa.com/us/en/dealer-locator, https://www.hyundaiusa.com/us/en/vehicles and https://www.hyundaiusa.com/us/en/certified-used-vehicles and 9 others have 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fix69
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5282863&Ver=2&mid=1012a5dc-003d-4f5a-825c-4564e02dc527&bo=1&sid=6061a1e0c5dc11f1ba0c77b2ce1e45a9&vid=6061bd40c5dc11f19bf211da2d632783&vids=1&msclkid=N&pi=918639831&lg=.

  • 101 small tap targets

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

  • 6 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: ttd_dom_ready is not defined”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • No social proof

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

  • No form on the homepage

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,170 words of copy

    The homepage carries about 1,170 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “Request a Quote”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Request a Quote” and “Schedule test drive”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 5 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.

  • 37 cookies set on arrival

    37

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

  • 58 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hyundaiusa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on hyundaiusa.com, including 27 speed issues, 4 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25