docsdiesel.com website review

30 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.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 9.3 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

42 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

8 third-party services load with your homepage (Shopify, alia-prod.com and rebuyengine.com and others), adding 2.8 MB and 1.2 s of main-thread time.

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

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

Shopify costs a phone 365 ms of main-thread work and 665 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.

alia-prod.com costs a phone 296 ms of main-thread work and 779 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.

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

rebuyengine.com costs a phone 175 ms of main-thread work and 738 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.

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

About 64 KiB of CSS is downloaded but never applied on this page.

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

15 KiB could be saved by minifying JavaScript.

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.

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.

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

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Veteran Joe Beck in a Doc's Diesel shirt spreading the Amer…”.

Visually, the page fills in at 12.3 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.5 s on a phone. Good is under 1.8 s.

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

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

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

Real visitors wait 1.2 s 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' largest content (lcp) went from 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.7 MB in 444 requests on a phone: images 3.7 MB (65), scripts 2.1 MB (149) and other files 1.2 MB (172). Under 2 MB keeps phones on slow connections fast.

calipers-hero-mobile.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).

2 images are downloaded at several times the size a phone draws them, for example New_Drops_Slide_Calipers.png at 800 px wide, shown at 248 px. Resized copies would save about 34 KiB.

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

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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. (3 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 315 pages on docsdiesel.com and 6 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

The HTML your server sends has 816 of the 2,149 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

/collections/6-7-cummins and /collections/5-9l-cummins are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/pages/contact-us, /pages/deal-for-vets, /collections/cummins, /collections/6-7-cummins, /collections/2025-2026-6-7l-24v-cummins and /collections/2019-2024-6-7l-24v-cummins and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/2025-2026-6-7l-24v-cummins has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

2 links go through two or more redirects, for example https://docsdiesel.com/account.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

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

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

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.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 2,149 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 Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 36 cookies, 1 of them by other companies (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 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.