adesa.com website review

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

7 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 369 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 730 ms faster on a phone.

Your mobile performance score is 58 (desktop: 56). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Optanon and jQuery CDN and others), adding 1.7 MB and 401 ms of main-thread time.

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

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

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

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

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

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

site.com costs a phone 11 ms of main-thread work and 715 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.

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

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

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.

4 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

17 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-17, real Chrome visitors' tap response (inp) went from 108 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.1 MB in 100 requests on a phone: images 9.1 MB (21), scripts 1.4 MB (38) and fonts 290 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images weigh 8.4 MB together. On a phone connection a single image that size takes seconds.

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

3 images are downloaded at several times the size a phone draws them, for example Homepage-Clear-Graphic-v2.svg at 1,080 px wide, shown at 344 px. Resized copies would save about 401 KiB.

1 image (102 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 3.16 g of CO₂e: 378.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

The page declares lang=“en-US ss”, which is not a usable language code, so screen readers and translation tools guess.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is only 5 characters: “ADESA”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 101 pages on adesa.com and 25 external pages.

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.

/inventory and /auction_location/adesa-little-rock have no meta description, so Google writes the search snippet from whatever text it finds.

/auctions, /inventory, /carvalue, /about-us, /auction_location/adesa-birmingham and /auction_location/adesa-phoenix and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://adesa-us.my.site.com/ESWADESAMIAWChat1722886086021/assets/styles/bootstrap.min.css…”.

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.

1 link go through two or more redirects, for example https://www.adesaclear.com/browse?utm_campaign=header_login.

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.

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

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

The homepage carries about 365 words of visible text.

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 Analytics, Google Tag Manager and Segment (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 6 cookies (measured from a US location before any click).

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