jimsauto.com website review

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

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

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

About 137 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.

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

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

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

4 third-party services load with your homepage (tailwindcss.com, Unpkg and smartestsearch.com and others), adding 1.2 MB and 143 ms of main-thread time.

Amazon Web Services costs a phone 0 ms of main-thread work and 945 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.

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

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

19 KiB could be saved by minifying JavaScript.

13 KiB could be saved by minifying CSS.

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

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.

Your largest element takes 16.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “QUALITY USED DOMESTIC PARTS Jim’s Auto Salvage Is Florida’s…”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

jims-auto-happy-customer-e1745422743812.png weighs 691 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.5 MB in 123 requests on a phone: images 1.5 MB (7), scripts 706 KiB (53) and stylesheets 249 KiB (52). Under 2 MB keeps phones on slow connections fast.

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

2 images further down the page (714 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example jims-auto-parts-2025-logo-e1745423212504-600x351.png at 390 px wide, shown at 95 px. Resized copies would save about 53 KiB.

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

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

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

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

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

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

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

The homepage links to 209 pages on jimsauto.com and 2 external pages.

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

There is no https://jimsauto.com/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.

Your homepage links to https://jimsauto.com/inventory, which answers with an error. Visitors hit a dead end and search engines drop it.

https://jimsauto.com/used-parts, https://jimsauto.com/used-parts/DODGE/DODGE_1500_PICKUP/260740/2022, https://jimsauto.com/used-parts/CADILLAC/XT5/260744/2024, https://jimsauto.com/used-parts/BUICK/ENCLAVE/260745/2021, https://jimsauto.com/used-parts/CHEVROLET/BLAZER/260742/2022 and https://jimsauto.com/used-parts/DODGE/DODGE_1500_PICKUP/260746/2019 and 3 others all use the title “used-parts - Jim's Domestic Auto Salvage”. Search engines can't tell which page to show for a search, so each competes with the others.

https://jimsauto.com/used-parts has no meta description, so Google writes the search snippet from whatever text it finds.

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

5 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.jimsauto.com/staging/wp-content/uploads/elementor/google-fonts/fonts/urbanist-l0x4df02if…”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

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.

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