steadyrack.com website review

24 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

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

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

8 third-party services load with your homepage (Google Tag Manager, negate.io and Shopify and others), adding 2.6 MB and 1.4 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 341 ms of main-thread work and 342 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 218 ms of main-thread work and 941 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.

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

videowise.com costs a phone 108 ms of main-thread work and 834 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.

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

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

12 KiB JavaScript is shipped twice across bundles.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 16.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to make our site work and ensure …”.

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

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

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

For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.

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

Scripts block taps and scrolling for 269 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-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 277 requests on a phone: images 2.1 MB (38), scripts 1.6 MB (101) and other files 800 KiB (114). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example Pro_Narrow_White_Close_Up.webp at 1,400 px wide, shown at 300 px. Resized copies would save about 1.5 MB.

4 images (2.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 1.45 g of CO₂e: 173.9 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.

Your title is 71 characters, so Google will cut it off around 60: “Bike Storage | Innovative Bike & Gear Storage Solutions – Steadyrack NA”.

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

The homepage links to 205 pages on steadyrack.com and 15 external pages.

/pages/subscription, /pages/shipping, /collections/bike-racks, /collections/proflex-range, /collections/classic-range and /collections/gearmate-range and 3 others use the same meta description. A description written for each page earns more clicks.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“`<source src>` with a `<picture>` parent is invalid and therefore ignored. Please use `<source srcs…”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

1 link go through two or more redirects, for example https://steadyrack-na-b2b.myshopify.com/.

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.

steadyrack.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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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,136 words of visible text.

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, Klaviyo and Meta Pixel 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 31 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 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.