pinnacol.com website review

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

10 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, website-files.com and Google CDN and others), adding 9.5 MB and 637 ms of main-thread time.

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

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

website-files.com costs a phone 96 ms of main-thread work and 8.2 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 569 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Go where you're more than a policy Become a member Learn ho…”.

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

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

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

The layout shifts by 0.108 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.9 MB in 75 requests on a phone: images 8.1 MB (28), scripts 1.3 MB (28) and fonts 385 KiB (7). Under 2 MB keeps phones on slow connections fast.

4 images weigh 6.3 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example 6ac6c950641dc09d0707d626_69f247c68c6922bb5ec9ee2e_David%20AL at 4,096 px wide, shown at 358 px. Resized copies would save about 3.9 MB.

5 images (6.5 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.

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

6997b55d89d1e91ec26858b7_MBOC-white.png 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).

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

5 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: 9 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.

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

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

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: url is not an absolute URL ("/")”.

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

The homepage links to 91 pages on pinnacol.com and 27 external pages.

We fetched 15 pages linked from your homepage (of 50 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=25032264&tm=gtm002&Ver=2&mid=b51488e9-2cbc-4e53-a790-d055ac5dfc77&bo=1&sid=39eb2d00d8ba11f183cd21e50fb4ed97&vid=39eb4f40d8ba11f195965b6f9eb0dc49&vids=1&msclkid=N&pi=91.

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 820 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

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

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