Website review, no card needed

aev-conversions.com logo

aev-conversions.com website review

Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 83 checks

This review found 34 issues worth fixing on aev-conversions.com, 13 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
991 ms880 msMay 2Oct 17913 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026978 ms
May 9, 2026978 ms
May 16, 2026976 ms
May 23, 2026964 ms
May 30, 2026945 ms
Jun 6, 2026923 ms
Jun 13, 2026906 ms
Jun 20, 2026900 ms
Jun 27, 2026896 ms
Jul 4, 2026895 ms
Jul 11, 2026894 ms
Jul 18, 2026893 ms
Jul 25, 2026898 ms
Aug 1, 2026911 ms
Aug 8, 2026916 ms
Aug 15, 2026919 ms
Aug 22, 2026928 ms
Aug 29, 2026916 ms
Sep 5, 2026930 ms
Sep 12, 2026956 ms
Sep 19, 2026944 ms
Sep 26, 2026948 ms
Oct 3, 2026941 ms
Oct 10, 2026918 ms
Oct 17, 2026913 ms
Real-visitor tap response (INP)75th percentile, phones
100 ms82 msMay 2Oct 1798 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202684 ms
May 9, 202684 ms
May 16, 202686 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202688 ms
Jun 13, 202691 ms
Jun 20, 202693 ms
Jun 27, 202695 ms
Jul 4, 202695 ms
Jul 11, 202696 ms
Jul 18, 202695 ms
Jul 25, 202695 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202696 ms
Aug 22, 202696 ms
Aug 29, 202696 ms
Sep 5, 202696 ms
Sep 12, 202696 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 202697 ms
Oct 10, 202697 ms
Oct 17, 202698 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 aev-conversions.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aev-conversions.com at 1.1 s1.1 s
  2. aev-conversions.com at 2.2 s2.2 s
  3. aev-conversions.com at 3.3 s3.3 s
  4. aev-conversions.com at 4.4 s4.4 s
  5. aev-conversions.com at 5.5 s5.5 s
  6. aev-conversions.com at 6.6 s6.6 s
  7. aev-conversions.com at 7.7 s7.7 s
  8. aev-conversions.com at 8.8 s8.8 s

Speed

12 to fix32
  • Reduce unused JavaScript

    5.7 s · 749 KiB

    About 749 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.7 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 244 KiB

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

  • Mobile performance score: 32

    32/100

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

  • Main-thread work: 4.5 s

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

  • Improve image delivery

    800 ms · 644 KiB

    9 images could be 644 KiB 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (hsappstatic.net, Google CDN and Hubspot and others), adding 2.3 MB and 1.2 s of main-thread time.

  • hsappstatic.net adds 522 ms

    522 ms

    hsappstatic.net costs a phone 522 ms of main-thread work and 694 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.

  • Reduce unused CSS

    440 ms · 76 KiB

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

  • Render-blocking requests

    450 ms

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

  • Legacy JavaScript

    300 ms · 23 KiB

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

  • Google CDN adds 205 ms

    205 ms

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

  • Shopify adds 103 ms

    103 ms

    Shopify costs a phone 103 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.

  • 13 long tasks on the main thread

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

  • Phones get a much slower page than desktops

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

8 to fix67
  • 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 CLS: 0.43

    0.43

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

  • First Contentful Paint: 15.6 s

    15.6 s

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

  • Largest Contentful Paint: 23.7 s

    23.7 s

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

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 27.3 s

    27.3 s

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

  • Cumulative Layout Shift: 0.383

    0.383

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

  • Total Blocking Time: 251 ms

    251 ms

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

4 checks passed
  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 112 ms

    112 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 372 ms

    372 ms

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

Images and page weight

2 to fix69
  • Page weight: 5.3 MB in 385 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 385 requests on a phone: scripts 2.3 MB (149), other files 1.3 MB (174) and images 1.2 MB (32). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    HM_HERO_JL370.webp 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).

  • 2 images in older formats

    2 images (119 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.

  • 1 image below the first screen load straight away

    1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.49 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9395
  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Zoom is disabled

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 49 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: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • Open Graph partly set

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

  • 148 internal links, 7 external

    The homepage links to 148 pages on aev-conversions.com and 7 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Visit American Expedition Vehicles (AEV), the leading store for high-quality off-road vehicle parts. Discover the essen…”.

  • One H1 headline

    Your main headline reads: “American Expedition Vehicles”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “American Expedition Vehicles – Off-Road Parts & Upgrades”.

  • Canonical URL set

    The canonical URL is https://aev-conversions.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://aev-conversions.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (627 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://aev-conversions.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://aev-conversions.com/pages/vehicles-canyon and https://aev-conversions.com/pages/vehicles-fx370 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://aev-conversions.com/pages/vehicles, https://aev-conversions.com/pages/vehicles-wrangler-jl, https://aev-conversions.com/pages/vehicles-gladiator-jt, https://aev-conversions.com/pages/vehicles-colorado, https://aev-conversions.com/pages/vehicles-silverado-1500 and https://aev-conversions.com/pages/vehicles-silverado-hd and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

3 to fixGoogle 7385
  • 7 small tap targets

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

  • 1 third-party cookie

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • 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 348 words of copy

    The homepage carries about 348 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP GMC NOW” and “SHOP CHEVY NOW”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Start shopping”, “SHOP GMC NOW” and “SHOP CHEVY NOW”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

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

  • 46 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 aev-conversions.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

E-commerce
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on aev-conversions.com, including 20 speed issues and 3 conversion gaps. 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