proximat.net website review

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

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

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

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

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

7 third-party services load with your homepage (Shopify, Klaviyo and Google CDN and others), adding 608 KiB and 359 ms of main-thread time.

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

About 87 KiB of JavaScript is downloaded but never used on this page.

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

Polyfills for old browsers add 25 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.

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

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

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

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 2.9 MB in 254 requests on a phone: images 1.3 MB (23), scripts 705 KiB (108) and other files 683 KiB (83). Under 2 MB keeps phones on slow connections fast.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

12 visible links have no text or label, so screen readers cannot say where they go.

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

There are 2 <h1> headlines (“” and “17" x 28" Comfort Mat”). One clear main headline is easier for people and search engines.

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

The homepage links to 112 pages on proximat.net and 4 external pages.

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

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

https://proximat.net/customer_authentication/redirect, https://proximat.net/policies/shipping-policy, https://proximat.net/collections/all-proximat, https://proximat.net/collections/vr-mats, https://proximat.net/collections/special-edition and https://proximat.net/collections/vr-yoga-mats and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://proximat.net/customer_authentication/redirect, https://proximat.net/apps/return_prime and https://proximat.net/pages/how-to-set-up-your-proximat-virtual-reality-mat have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were 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…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 22 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.

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

The homepage carries about 716 words of visible text.

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