Website review, no card needed

usa-rs.com logo

usa-rs.com website review

Visit site (opens in a new tab)Reviewed 8 November 202635 issues · 84 checks

This review found 35 issues worth fixing on usa-rs.com, 12 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.8 s1.6 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.3 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.3 s
Sep 26, 20262.1 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
112 ms92 msMay 16Oct 31104 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026109 ms
May 23, 2026105 ms
May 30, 202695 ms
Jun 6, 2026101 ms
Jun 13, 2026103 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 202698 ms
Jul 11, 202697 ms
Jul 18, 202694 ms
Jul 25, 2026100 ms
Aug 1, 202696 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026109 ms
Sep 5, 2026107 ms
Sep 12, 2026110 ms
Sep 19, 2026107 ms
Sep 26, 2026107 ms
Oct 3, 2026105 ms
Oct 10, 2026104 ms
Oct 17, 2026105 ms
Oct 24, 2026103 ms
Oct 31, 2026104 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of usa-rs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. usa-rs.com at 0.7 s0.7 s
  2. usa-rs.com at 1.4 s1.4 s
  3. usa-rs.com at 2.0 s2.0 s
  4. usa-rs.com at 2.7 s2.7 s
  5. usa-rs.com at 3.4 s3.4 s
  6. usa-rs.com at 4.1 s4.1 s
  7. usa-rs.com at 4.7 s4.7 s
  8. usa-rs.com at 5.4 s5.4 s

Speed

11 to fix55
  • Reduce unused JavaScript

    1.5 s · 388 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 431 KiB

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

  • Improve image delivery

    900 ms · 323 KiB

    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.

  • Mobile performance score: 55

    55/100

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

  • Render-blocking requests

    450 ms

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

  • Main-thread work: 3.3 s

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

  • Duplicated JavaScript

    300 ms · 18 KiB

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

  • 2,800 HTML elements

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

  • 6 long tasks on the main thread

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

  • Google CDN adds 123 ms

    123 ms

    Google CDN costs a phone 123 ms of main-thread work and 299 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 adds 107 ms

    107 ms

    Shopify costs a phone 107 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 on the page

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

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 10.9 s

    10.9 s

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

  • Time to Interactive: 15.4 s

    15.4 s

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

  • Speed Index: 10.0 s

    10.0 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • 16 images without width and height

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

  • Total Blocking Time: 228 ms

    228 ms

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

  • Tap response (INP) held steady for real visitors

    -3%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 704 ms

    704 ms

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

  • Largest content (LCP) got 23% faster for real visitors

    -23%

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix83
  • Page weight: 3.2 MB in 376 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 376 requests on a phone: scripts 1.2 MB (147), images 920 KiB (96) and other files 802 KiB (113). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    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 in older formats

    1 image (36 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 below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.91 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8291
  • ARIA attributes must conform to valid values (1 element)

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

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Frames without titles

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

  • 6 images without alt text

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

  • All page content should be contained by landmarks (3 elements)

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

  • 1 link without text

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

1 checks passed
  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8590
  • Title is short (24 characters)

    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 crawlers can't follow

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

  • 258 internal links, 3 external

    The homepage links to 258 pages on usa-rs.com and 3 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Commercial restaurant equipment from 300+ authorized brands. 300,000+ products stocked in U.S. warehouses, expert help,…”.

  • One H1 headline

    Your main headline reads: “Need somethingfast?”.

  • Canonical URL set

    The canonical URL is https://shopusars.com/.

  • Structured data in place

    Structured data found: OnlineStore and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://shopusars.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,060 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://shopusars.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

6 to fix43
  • 1 linked page is broken

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

  • 1 page without a title

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

  • 1 linked page hidden from search

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

  • 1 page without a meta description

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

  • 13 pages share a meta description

    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.

  • 1 page without an H1

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

  • 15 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9297
  • 1 distorted image

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    18 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 699 words of copy

    The homepage carries about 699 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP QUICK SHIP” and “SHOP EQUIPMENT”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Shop All”, “Donut Shop” and “Coffee & Tea Shop”.

  • 33 short forms

    33 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks, a star rating and 3 trust badges.

  • Analytics in place

    Analytics detected: PostHog.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 7 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 36 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at usa-rs.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Epa Easy Product Addons · Judge Me Reviews · Google Youtube · Inbox · Mailchimp · Pixiehog · hubapi.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
PostHog
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on usa-rs.com, including 17 speed issues and 2 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25