shopusars.com website review

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

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

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

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

7 images could be 323 KiB 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.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

The page has 2,755 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Shopify costs a phone 93 ms of main-thread work and 373 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.

8 third-party services load with your homepage (Google CDN, Shopify and Hubspot and others), adding 859 KiB and 365 ms of main-thread time.

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

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

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

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

Your largest element takes 14.5 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 15.9 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 3.2 MB in 369 requests on a phone: scripts 1.2 MB (148), images 908 KiB (97) and other files 760 KiB (104). Under 2 MB keeps phones on slow connections fast.

slide3.jpg 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).

1 image (40 KiB) 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.

1 image further down the page (60 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.6 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 tap targets are too small or too close together to hit reliably with a finger.

1 frame has no title, so screen-reader users cannot tell what it contains.

6 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is only 24 characters: “USA Restaurant Suppliers”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link has no real href, so search engines can't follow it.

The homepage links to 255 pages on shopusars.com and 3 external pages.

Your homepage links to https://shopusars.com/[url], which answers with an error. Visitors hit a dead end and search engines drop it.

https://shopusars.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://shopusars.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://shopusars.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://shopusars.com/collections/equipment, https://shopusars.com/collections/beverage-equipment, https://shopusars.com/collections/concession-equipment, https://shopusars.com/collections/cooking-equipment, https://shopusars.com/collections/facility-ventilation-equipment and https://shopusars.com/collections/food-display-merchandising-equipment and 7 others use the same meta description. A description written for each page earns more clicks.

https://shopusars.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://shopusars.com/collections/equipment, https://shopusars.com/collections/beverage-equipment, https://shopusars.com/collections/cooking-equipment and https://shopusars.com/collections/plumbing-water-treatment-equipment took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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