peterbiltparts.com website review

About 925 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Mailchimp and others), adding 2.2 MB and 1.5 s of main-thread time.

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

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

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

16 images could be 335 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

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

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

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

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

6 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 20 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.

Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “10% Off AC & HEATING”.

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

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

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

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

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

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.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 419 requests on a phone: scripts 2.0 MB (97), other files 1.3 MB (263) and images 652 KiB (39). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Elite-Truck-Parts-700px.webp at 700 px wide, shown at 125 px. Resized copies would save about 132 KiB.

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

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

Banner landmark should not be contained in another landmark: 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.

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

There are 7 <h1> headlines (“Peterbilt Parts”, “Peterbilt Parts” and “TOP CATEGORIES”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 399 pages on peterbiltparts.com and 8 external pages.

https://peterbiltparts.com/policies/shipping-policy, https://peterbiltparts.com/pages/contact, https://peterbiltparts.com/collections/brands and https://peterbiltparts.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://peterbiltparts.com/policies/shipping-policy, https://peterbiltparts.com/pages/contact, https://peterbiltparts.com/collections/recently-added, https://peterbiltparts.com/collections/brands, https://peterbiltparts.com/collections/elite and https://peterbiltparts.com/collections/paccar and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://peterbiltparts.com/policies/shipping-policy, https://peterbiltparts.com/pages/contact, https://peterbiltparts.com/collections/recently-added, https://peterbiltparts.com/collections/brands, https://peterbiltparts.com/collections/elite and https://peterbiltparts.com/collections/paccar and 9 others have 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 177 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4057554&Ver=2&mid=3b7afa16-0d80-46b7-b2a8-92c714bfa85a&bo=1&sid=cf9d5a90db0d11f19070f54bac955b6b&vid=cf9d80e0db0d11f189422562316ed2fa&vids=1&msclkid=N&pi=918639831&lg=.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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

Social proof on the homepage: 15 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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