patchstrips.com website review

The page goes through 2 redirects before it starts loading, costing about 7.8 s. Link and advertise the final URL directly.

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

8 third-party services load with your homepage (patchbandages.com, Facebook and Shopify and others), adding 2.1 MB and 776 ms of main-thread time.

About 559 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 390 ms faster on a phone.

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

patchbandages.com costs a phone 221 ms of main-thread work and 1.3 MB 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.

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

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

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

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

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

2 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The page you requested does not exist. Click here to contin…”.

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

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 3.9 MB in 315 requests on a phone: scripts 1.9 MB (145), other files 809 KiB (109) and images 721 KiB (17). Under 2 MB keeps phones on slow connections fast.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The page answers with an error status, so search engines may drop it.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 79 pages on patchstrips.com and 3 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.

/en-us/collections/future-bandages, /en-us/collections/patch-pet, /en-us/collections/first-aid-kits and /en-us/collections/bite-treatment have no meta description, so Google writes the search snippet from whatever text it finds.

/en-us/collections has no <h1> headline, so visitors and search engines get no clear main topic.

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

14 of 27 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 404 ()”.

Large scripts ship without source maps.

Social proof on the homepage: 112 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 64 words of visible text; thin pages give Google and first-time buyers little to go on.

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, Google Tag Manager, Klaviyo 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 25 cookies, 11 of them by other companies (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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.