piercedistribution.com website review

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

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

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

About 879 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.7 s faster on a phone.

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

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

6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.6 MB and 983 ms of main-thread time.

Google CDN costs a phone 675 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.

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

93 KiB could be saved by minifying CSS.

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

25 KiB could be saved by minifying JavaScript.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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.

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

Your largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We specialize in third-party logistics (3PL) and distributi…”.

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

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

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

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

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.

Your homepage downloads 9.9 MB in 86 requests on a phone: media 2.9 MB (1), images 2.9 MB (20) and scripts 2.1 MB (29). Under 2 MB keeps phones on slow connections fast.

11 images (2.8 MB) 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.

11 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 6 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.

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

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

Your title is 79 characters, so Google will cut it off around 60: “Pierce Distribution Services Company - Rockford, IL | Crating Company Milwaukee”.

Structured data found (Article, ImageObject, LocalBusiness and Organization) but with 2 problems, for example “Article: missing datePublished”.

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 50 pages on piercedistribution.com and 3 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. 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://piercedistribution.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.

https://piercedistribution.com/why-pierce/locations took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://piercedistribution.com/index.php/_wblapi?nolangfilter=1&_wblapi=https://piercedistribution.com/forseo/v1/cron/image/83401648659116999196916911756.svg.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 209 words of visible text; thin pages give Google and first-time buyers little to go on.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 4 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.