mrsbowtie.com website review

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

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

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

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

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

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

Reviews.io costs a phone 2 ms of main-thread work and 364 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.

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

8 third-party services load with your homepage (linkgraph.com, rapidlercdn.com and Reviews.io and others), adding 438 KiB and 63 ms of main-thread time.

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

4 images could be 30 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

12 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

download-9.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 0.43 g of CO₂e: 51.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (27 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 67 characters, so Google will cut it off around 60: “Men's Ties & Bow Ties | Original British Bowtie Brand - Mrs Bow Tie”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 211 pages on mrsbowtie.com and 5 external pages.

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

https://mrsbowtie.com/pages/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.

https://mrsbowtie.com/collections/brown-bow-ties, https://mrsbowtie.com/collections/blue-bow-ties, https://mrsbowtie.com/collections/dusty-blue-bow-ties, https://mrsbowtie.com/collections/sage-green-bow-ties and https://mrsbowtie.com/collections/dark-green-bow-ties took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

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

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