shopsps.com website review

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

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

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

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

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Clarity and Attentive and others), adding 589 KiB and 514 ms of main-thread time.

Google Tag Manager costs a phone 381 ms of main-thread work and 461 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 280 ms. During a long task the page ignores taps.

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

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

7 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 32.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We sell name-brand surgical disposables at a lower price. G…”.

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

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

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

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

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

Real visitors wait 273 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 70 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 8.6 MB in 172 requests on a phone: images 5.5 MB (106), other files 1.4 MB (42) and scripts 1.4 MB (18). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 2.44 g of CO₂e: 292.5 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.

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Headings should not be empty: 2 elements on the page fail 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 80 characters, so Google will cut it off around 60: “The Largest Surgical Disposables Store Online | Surgical Product Solutions (SPS)”.

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

There are 3 <h1> headlines (“We Value Your Privacy”, “Subscribe to Our Newsletter” and “We sell name-brand surgical disposablesat a lower…”). One clear main headline is easier for people and search engines.

Your meta description is 269 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.

4 links have no real href, so search engines can't follow them.

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

The homepage links to 47 pages on shopsps.com and 2 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.shopsps.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.shopsps.com/About%20Us, https://www.shopsps.com/manufacturer/galatea, https://www.shopsps.com/sps-refurbished-scopes, https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-arthroscopes, https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-colonoscopes and https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-cystoscopes and 9 others have no <title>, so Google invents the link text in results.

https://www.shopsps.com/About%20Us, https://www.shopsps.com/manufacturer/galatea, https://www.shopsps.com/sps-refurbished-scopes, https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-arthroscopes, https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-colonoscopes and https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-cystoscopes and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.shopsps.com/About%20Us, https://www.shopsps.com/manufacturer/galatea, https://www.shopsps.com/sps-refurbished-scopes, https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-arthroscopes, https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-colonoscopes and https://www.shopsps.com/sps-refurbished-scopes/sps-refurbished-cystoscopes and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

13 of 30 tappable elements near the top of the page are 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: the server responded with a status of 400 ()”.

Large scripts ship without source maps.

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

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.

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

Your longest form asks for 16 fields (0 required). Every extra field lowers completion.

The homepage has only about 111 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 link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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