purocor.com website review

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

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

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

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

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

7 third-party services load with your homepage (sealsubscriptions.com, modapps.com.au and Shopify and others), adding 435 KiB and 126 ms of main-thread time.

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

41 KiB could be saved by minifying JavaScript.

3 images could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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.

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Thick, soft & absorbent wipes. Your members will feel the d…”. Most of its time is element render delay (2.6 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.

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

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

[role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 23 characters: “Gym Wipes – PuroCor USA”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 19 characters: “Gym Wipes that work”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“Made in the USA!”, “Premium Sanitizing Wipes - 4 x 1200 Count Rolls” and “Premium Studio Wipes - 4 x 1160 Count Rolls”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 36 pages on purocor.com and 5 external pages.

There is no https://www.purocor.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.purocor.com/collections/all and https://www.purocor.com/policies/terms-of-service use the same meta description. A description written for each page earns more clicks.

https://www.purocor.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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.

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

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 11 fields (0 required). Every extra field lowers completion.

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

The homepage carries about 310 words of visible text.

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