nashermiles.com website review

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

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

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

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

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

7 third-party services load with your homepage (flash-speed.com, Shopify and Google Fonts and others), adding 3.7 MB and 12 ms of main-thread time.

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

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

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

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 10.0 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 10.0 s. Good is under 3.8 s.

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 411 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

Real visitors wait 984 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 12.7 MB in 124 requests on a phone: media 9.7 MB (1), images 1.7 MB (48) and scripts 751 KiB (39). Under 2 MB keeps phones on slow connections fast.

800_x_800_Luggage_banner_13a133c7-5437-4e08-8d48-e17ecf1cdee 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).

11 images (677 KiB) 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 3.60 g of CO₂e: 432.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/5_4763a613-93da-4749-813f-4a891481ab3a.png")”.

14 links have no real href, so search engines can't follow them.

The homepage links to 402 pages on nashermiles.com and 17 external pages.

https://nashermiles.com/pages/harry-potter and https://nashermiles.com/collections/harry-potter all use the title “Harry Potter – Nasher Miles”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nashermiles.com/collections/harry-potter-backpacks, https://nashermiles.com/collections/harry-potter-duffle, https://nashermiles.com/collections/harry-potter-accessories and https://nashermiles.com/collections/harry-potter use the same meta description. A description written for each page earns more clicks.

https://nashermiles.com/collections/backpack, https://nashermiles.com/collections/harry-potter-backpacks, https://nashermiles.com/collections/harry-potter-accessories, https://nashermiles.com/collections/harry-potter, https://nashermiles.com/collections/luggage and https://nashermiles.com/collections/hardside and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://nashermiles.com/collections/polypropylene-trolley-bags and https://nashermiles.com/collections/large-trolley-bags took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://nashermiles.com/cdn/shop/files/1920_x_710_Luggage_Banne_37ddc56c-0752-43c0-816b-91b253870e2f_750x.webp?v=1791101006.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

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

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

Opening the homepage sets 4 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.