getstepr.com website review

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

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

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

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

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

8 third-party services load with your homepage (route.com, Google Tag Manager and Shopify and others), adding 3.4 MB and 2.3 s of main-thread time.

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

route.com costs a phone 668 ms of main-thread work and 1.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.

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

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

486 KiB JavaScript is shipped twice across bundles.

Google Tag Manager costs a phone 410 ms of main-thread work and 648 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.

Shopify costs a phone 374 ms of main-thread work and 545 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 348 ms. During a long task the page ignores taps.

15 KiB could be saved by minifying JavaScript.

PayPal costs a phone 243 ms of main-thread work and 392 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.

Klaviyo costs a phone 216 ms of main-thread work and 391 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.

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

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

16 KiB could be saved by minifying CSS.

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 30.6 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

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

Your homepage downloads 7.8 MB in 495 requests on a phone: scripts 4.6 MB (180), images 1.4 MB (60) and other files 1.0 MB (199). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (41 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your title is only 27 characters: “STEPR™ | Every Step Counts™”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 3 <h1> headlines (“”, “👟 Every. Step. Counts.™” and “protect”). One clear main headline is easier for people and search engines.

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 185 pages on getstepr.com and 23 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.

/pages/renewed-clearance-refurbs has no meta description, so Google writes the search snippet from whatever text it finds.

/pages/product-lineup-stepr, /collections/shop-now and /pages/blog have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343145338&Ver=2&mid=0e88dae1-1c42-4b2c-897a-f3517c0e7d74&bo=1&sid=d5cad090dbeb11f18d9ab72fdd6364f2&vid=d5cb04a0dbeb11f1a6f6b35af218940e&vids=1&msclkid=N&pi=918639831&l.

6 errors were logged to the browser console while the page loaded, for example “analytics is not defined”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

3 links go through two or more redirects, for example https://getstepr.com/checkout.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

getstepr.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

getstepr.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

The homepage carries about 683 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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