tri-statedistributors.com website review

31 images could be 18.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 47.0 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and userway.org and others), adding 1.1 MB and 362 ms of main-thread time.

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

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

userway.org costs a phone 49 ms of main-thread work and 450 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.

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

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

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.

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

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

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

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

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

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

41 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-17, real Chrome visitors' tap response (inp) went from 78 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 19.8 MB in 101 requests on a phone: images 18.5 MB (41), scripts 728 KiB (21) and other files 339 KiB (25). Under 2 MB keeps phones on slow connections fast.

9 images weigh 16.3 MB together. On a phone connection a single image that size takes seconds.

16 images are downloaded at several times the size a phone draws them, for example osburn-logo(1).png at 5,400 px wide, shown at 152 px. Resized copies would save about 12.3 MB.

27 images (18.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.

24 images further down the page (11.7 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 5.62 g of CO₂e: 674.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 9 characters: “Home Page”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is 352 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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.

The homepage links to 139 pages on tri-statedistributors.com and 10 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.

There is no https://www.tri-statedistributors.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://www.tri-statedistributors.com/catsearch/1/root and https://www.tri-statedistributors.com/products/categories.aspx all use the title “:: Tri-State Distributors”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tri-statedistributors.com/catsearch/1/root, https://www.tri-statedistributors.com/about/emailus, https://www.tri-statedistributors.com/about/locations, https://www.tri-statedistributors.com/secondary/branchlocator, https://www.tri-statedistributors.com/products/categories.aspx and https://www.tri-statedistributors.com/categories/gas-products and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tri-statedistributors.com/about/warranty-form and https://www.tri-statedistributors.com/about/showroomdisplay have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught ReferenceError: sliderDivSelector is not defined”.

1 image is served at too low a resolution for sharp phone screens.

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

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 has only about 197 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 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 6 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.