typesauto.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Osano CMP and others), adding 2.2 MB and 2.0 s of main-thread time.

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

Shopify costs a phone 480 ms of main-thread work and 703 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 Tag Manager costs a phone 389 ms of main-thread work and 340 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.

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

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

Osano CMP costs a phone 309 ms of main-thread work and 83 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.

ZenDesk costs a phone 205 ms of main-thread work and 431 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.

narvar.com costs a phone 94 ms of main-thread work and 316 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.

44 KiB could be saved by minifying JavaScript.

38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

3 KiB could be saved by minifying CSS.

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.

Your largest element takes 19.7 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 23.2 s. Good is under 3.8 s.

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

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

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

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

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

1 image 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 131 ms to 147 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 18.0 MB in 300 requests on a phone: media 13.2 MB (1), scripts 2.7 MB (130) and images 1.1 MB (30). Under 2 MB keeps phones on slow connections fast.

TYPES_Banners26_BT534745-1_r1_Mobile_v1.jpg 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).

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

ARIA attributes must conform to valid values: 2 elements on the page fail 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.

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

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

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.

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

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

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

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

The homepage links to 100 pages on typesauto.com and 9 external pages.

https://typesauto.com/collections/formula-drift-led-kits, https://typesauto.com/pages/led-fog-light-bulbs, https://typesauto.com/collections/offroad-lights, https://typesauto.com/collections/led-lighting-accessories, https://typesauto.com/collections/ev-charger and https://typesauto.com/collections/battery-chargers and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://typesauto.com/pages/led-fog-light-bulbs and https://typesauto.com/pages/ride-share-dashcam have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Microsoft Clarity and TikTok Pixel (measured from a US location before any click). A consent tool (Osano) 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 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.