narrowmindedrailworks.com website review

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

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

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

7 third-party services load with your homepage (hcaptcha.com, Shopify and emrld.ltd and others), adding 2.7 MB and 1.2 s of main-thread time.

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

hcaptcha.com costs a phone 829 ms of main-thread work and 1.2 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.

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

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

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

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

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

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

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

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.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your homepage downloads 7.8 MB in 461 requests on a phone: images 3.6 MB (44), scripts 2.2 MB (228) and other files 895 KiB (131). Under 2 MB keeps phones on slow connections fast.

98136fe0-97e5-447f-b73f-8e5f74811c02.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

6 tap targets are too small or too close together to hit reliably with a finger.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 23 characters: “Narrow Minded Railworks”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 6 <h1> headlines (“:root { --header-logo-width: 90px; }”, “Hand-Crafted 3D-Printed Narrow Gauge Kits for OO9…” and “Make your layout come alive”). One clear main headline is easier for people and search engines.

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

The homepage links to 195 pages on narrowmindedrailworks.com and 5 external pages.

https://narrowmindedrailworks.com/collections/oo9-scenery/OO9-Scenery and https://narrowmindedrailworks.com/collections/oo9-scenery all use the title “OO9 Scenery”. Search engines can't tell which page to show for a search, so each competes with the others.

https://narrowmindedrailworks.com/collections/all, https://narrowmindedrailworks.com/collections/oo9-wagon and https://narrowmindedrailworks.com/collections/cases have no meta description, so Google writes the search snippet from whatever text it finds.

https://narrowmindedrailworks.com/collections/oo9-scenery/OO9-Scenery and https://narrowmindedrailworks.com/collections/oo9-scenery use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://narrowmindedrailworks.com/collections/gn15-figures/GN15-Figures, whose canonical is https://narrowmindedrailworks.com/collections/gn15-figures/gn15-figures. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://narrowmindedrailworks.com/collections/all, https://narrowmindedrailworks.com/collections/gn15-wagons, https://narrowmindedrailworks.com/collections/gn15, https://narrowmindedrailworks.com/collections/gn15-figures/GN15-Figures, https://narrowmindedrailworks.com/collections/gn15-scenery and https://narrowmindedrailworks.com/collections/009-locos and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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