step.com website review

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

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

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

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

2 third-party services load with your homepage (Cookiebot and ctfassets.net), adding 322 KiB and 63 ms of main-thread time.

1 file is served with short cache lifetimes, so returning visitors download them again (33 KiB).

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

1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Home_Hero_020726.png”.

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

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

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 213 ms in total while the page loads. Good is under 200 ms.

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

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

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

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

The homepage links to 38 pages on step.com and 15 external pages.

https://step.com/earlypay-get-paid-before-payday and https://step.com/earlypay/phone-verification all use the title “Get Cash Before Payday with Step EarlyPay | Step”. Search engines can't tell which page to show for a search, so each competes with the others.

https://step.com/earlypay-get-paid-before-payday and https://step.com/earlypay/phone-verification use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://step.com/earlypay/phone-verification, whose canonical is https://step.com/earlypay-get-paid-before-payday. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://step.com/press has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 2,050 words of visible text.

Opening the homepage sets 2 cookies (measured from a US location before any click).

Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.