rmstator.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Key CDN and notify-me.io and others), adding 1.3 MB and 301 ms of main-thread time.

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

Shopify costs a phone 71 ms of main-thread work and 787 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.

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

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

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

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

About 49 KiB of CSS is downloaded but never applied on this page.

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

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.

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

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

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

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

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

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

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

Your homepage downloads 3.5 MB in 278 requests on a phone: scripts 1.2 MB (98), images 1.1 MB (31) and other files 936 KiB (101). Under 2 MB keeps phones on slow connections fast.

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

4 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: 12 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

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.

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

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

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 12 characters: “RMSTATOR.COM”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“RMSTATOR” and “THE RMSTATOR WAY”). One clear main headline is easier for people and search engines.

The homepage links to 137 pages on rmstator.com and 11 external pages.

The HTML your server sends has 693 of the 1,915 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://www.rmstator.com/collections/all-charging and https://www.rmstator.com/collections/all-charging-1 all use the title “All Charging – RMSTATOR”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rmstator.com/collections/all-charging, https://www.rmstator.com/collections/stators, https://www.rmstator.com/collections/voltage-regulator, https://www.rmstator.com/collections/universal-charging-parts, https://www.rmstator.com/collections/timing-plate and https://www.rmstator.com/collections/stator-cover-gasket and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.rmstator.com/collections/all-charging-1, whose canonical is https://www.rmstator.com/collections/all-charging. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

6 images failed to load on a phone, for example https://review-images.judgeme.com/rmstator/1793973423__1793973400615-df7bdd51-97b0-46b0-9fe3-19__original.jpg?quality=80&width=480.

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

3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.rmstator.com/cdn/shop/t/65/assets/popup-ymm-selector.css?v=12871' because its …”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 1,915 words of visible text.

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