pacesupply.com website review

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Fonts and others), adding 8.6 MB and 327 ms of main-thread time.

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

cloudfront.net costs a phone 0 ms of main-thread work and 7.4 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

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

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

Amazon Web Services costs a phone 0 ms of main-thread work and 477 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 28 KiB of CSS is downloaded but never applied on this page.

10 KiB could be saved by minifying CSS.

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.

For real visitors the layout shifts by 0.94 (75th percentile). Good is under 0.1.

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

Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “PACE Supply Reno/Sparks | New McCarran, NV Location Coming …”.

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

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

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

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

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

2 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 204 ms to 203 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.1 MB in 78 requests on a phone: images 8.0 MB (34), scripts 1.9 MB (6) and other files 132 KiB (34). Under 2 MB keeps phones on slow connections fast.

2 images weigh 6.4 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example web-banner_nampa_twin-falls_20x6_v1edit.png at 4,027 px wide, shown at 358 px. Resized copies would save about 5.0 MB.

12 images (7.1 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.

4 images further down the page (200 KiB) 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.87 g of CO₂e: 343.9 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: 2 elements on the page fail this check, rated critical by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

Heading levels should only increase by one: 5 elements on the page fail this check, rated moderate by axe-core.

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

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://www.pacesupply.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

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

A phone browser shows 477 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

There is no https://www.pacesupply.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.

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

5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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