peterbilt.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and termly.io and others), adding 1.8 MB and 1.1 s of main-thread time.

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

Google CDN costs a phone 601 ms of main-thread work and 1.1 MB 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.

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

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

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

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

Desktop scores 80 but mobile only 48. 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.

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 first text or image appears after 16.2 s on a phone. Good is under 1.8 s.

Your largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PACCAR Connect”.

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

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

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

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

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

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

5 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 116 ms to 112 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.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.6 MB in 142 requests on a phone: scripts 1.9 MB (29), other files 1.1 MB (33) and images 1.0 MB (30). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Banner1.25.webp at 1,920 px wide, shown at 390 px. Resized copies would save about 114 KiB.

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

31 elements hidden from screen readers can still receive keyboard focus.

4 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: 47 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.

Page should contain a level-one heading: 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.

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

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 31 pages on peterbilt.com and 16 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.

https://www.peterbilt.com/trucks/zero-emission, https://www.peterbilt.com/trucks/on-highway and https://www.peterbilt.com/trucks/vocational all use the title “Peterbilt Work Trucks | Peterbilt”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.peterbilt.com/trucks/zero-emission, https://www.peterbilt.com/trucks/on-highway and https://www.peterbilt.com/trucks/vocational use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.peterbilt.com/resources/mobile-wallpapers, whose canonical is https://www.peterbilt.com/resources. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.peterbilt.com/news-and-events, https://www.peterbilt.com/trucks/zero-emission, https://www.peterbilt.com/trucks/on-highway, https://www.peterbilt.com/recalls and https://www.peterbilt.com/trucks/vocational 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 21 found) and read each the way a search engine does.

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.

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

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

The page uses urgency cues (a countdown or limited-time wording).

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