unitedspb.com website review

website-files.com costs a phone 2.1 s of main-thread work and 21.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

3 third-party services load with your homepage (website-files.com, cloudfront.net and Adobe TypeKit), adding 21.3 MB and 2.7 s of main-thread time.

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

Your mobile performance score is 53 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

Desktop scores 92 but mobile only 53. 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.

5 KiB could be saved by minifying CSS.

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

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

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

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

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

11 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 21.3 MB in 45 requests on a phone: media 18.3 MB (2), images 2.5 MB (21) and fonts 329 KiB (14). Under 2 MB keeps phones on slow connections fast.

6a4302241504df90d15c43a4_USB OFFICE PHOTOS (13).jpg weighs 2.1 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 6a4302241504df90d15c43a4_USB OFFICE PHOTOS (13).jpg at 8,592 px wide, shown at 359 px. Resized copies would save about 2.1 MB.

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

3 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.

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

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.

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

There are 6 <h1> headlines (“EMPOWERING ATHLETES.”, “PROTECT.” and “PERFORM.”). One clear main headline is easier for people and search engines.

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

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

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

The homepage links to 29 pages on unitedspb.com and 7 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.unitedspb.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.unitedspb.com/post/shock-doctor-partners-with-amir-sears-the-no-1-high-school-football-player-in-the-class-of-2028 and https://www.unitedspb.com/post/shock-doctor-partners-with-makena-cook-the-nations-top-flag-football-player all use the title “United Sports Brands”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.unitedspb.com/innovation, https://www.unitedspb.com/partners-athletes, https://www.unitedspb.com/news, https://www.unitedspb.com/post/shock-doctor-partners-with-amir-sears-the-no-1-high-school-football-player-in-the-class-of-2028 and https://www.unitedspb.com/post/shock-doctor-partners-with-makena-cook-the-nations-top-flag-football-player have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 of 5 tappable elements near the top of the page is 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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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.

The homepage carries about 261 words of visible text.

Opening the homepage sets 1 cookie (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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.