hallauto.com website review

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

Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (Google Tag Manager, complyauto.com and edmunds.com and others), adding 568 KiB and 549 ms of main-thread time.

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

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

Google Tag Manager costs a phone 270 ms of main-thread work and 315 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.5 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 220 KiB of JavaScript is downloaded but never used on this page.

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

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

15 KiB could be saved by minifying JavaScript.

7 KiB JavaScript is shipped twice across bundles.

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.

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome to Hall Learn More About How We Support Our Communi…”.

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

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

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

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

Your homepage downloads 2.1 MB in 137 requests on a phone: scripts 1,005 KiB (60), other files 333 KiB (35) and images 327 KiB (24). Under 2 MB keeps phones on slow connections fast.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

button, link, and menuitem elements do not have accessible names. (1 element).

Elements use prohibited ARIA attributes (1 element).

1 element has a tabindex above 0, which scrambles the keyboard order.

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

Structured data found (AutoDealer, AutomotiveBusiness, BreadcrumbList and Organization) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

There is no robots.txt at hallauto.com/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 73 pages on hallauto.com and 11 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/body-shop/locations.htm is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/used-inventory/fuel-efficient.htm and /commercial-new-inventory/index.htm use the same meta description. A description written for each page earns more clicks.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

Requests the geolocation permission on page load.

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

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

hallauto.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage has only about 3 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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.

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

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.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.