zipr.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.5 s faster on a phone.

8 third-party services load with your homepage (YouTube, ZenDesk and Affirm and others), adding 3.6 MB and 1.4 s of main-thread time.

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

Your mobile performance score is 51 (desktop: 60). Pages that score under 90 lose visitors before the first paint.

YouTube costs a phone 747 ms of main-thread work and 2.1 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.

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

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

3 images could be 130 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

ZenDesk costs a phone 151 ms of main-thread work and 414 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.

Judge.me costs a phone 85 ms of main-thread work and 339 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.

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

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

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.

4 KiB could be saved by minifying CSS.

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

Your largest element takes 26.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man riding a blue mobility scooter on a sidewalk with flowe…”.

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

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

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

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

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

Your homepage downloads 5.3 MB in 258 requests on a phone: scripts 3.1 MB (94), other files 1.1 MB (132) and images 420 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

8 elements use ARIA attributes their role does not allow, which confuses screen readers.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 69 characters, so Google will cut it off around 60: “Best Online Mobility Scooters & Electric Wheelchairs | Zip'r Mobility”.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.zipr.com/search?q={search_term_string}")”.

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

The homepage links to 180 pages on zipr.com and 16 external pages.

Your homepage links to https://www.zipr.com/collections/mobility-scooter-accessories and https://www.zipr.com/collections/knee-scooters, which answer with an error. Visitors hit a dead end and search engines drop them.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=137027529&Ver=2&mid=92345162-bd00-4d2b-80d5-e4d6e003102b&bo=1&sid=1c5b9710cf5a11f1815a03ea9bdaea1e&vid=1c5bab60cf5a11f1a7abf958b63e758b&vids=1&msclkid=N&pi=918639831&l.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

The homepage carries about 1,414 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 16 cookies, 1 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 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.