rontomson.com website review

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

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

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

17 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

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

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

8 third-party services load with your homepage (Noibu, Clarity and Shopify and others), adding 2.4 MB and 367 ms of main-thread time.

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

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

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

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

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.

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 page becomes fully interactive after 22.8 s. Good is under 3.8 s.

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TAILORING Cut in Houndstooth. SHOP THE SUIT ALL SUITS Hound…”.

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

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

Visually, the page fills in at 5.1 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 196 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.5 MB in 251 requests on a phone: images 2.3 MB (30), scripts 952 KiB (80) and other files 792 KiB (120). Under 2 MB keeps phones on slow connections fast.

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

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

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

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//rontomson.com/cdn/shop/files/LOGO-IPEK-white_def4f9e4…”.

The homepage links to 598 pages on rontomson.com and 5 external pages.

https://rontomson.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://rontomson.com/pages/contact declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://rontomson.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://rontomson.com/pages/contact all use the title “Ron Tomson | Designer Clothing - Fashion Forward”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rontomson.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187019793&Ver=2&mid=241f85ab-18b9-4f09-9a5a-64019a52e16d&bo=1&sid=7abdaa10d9fa11f192812f59939d5837&vid=7ac22fa0d9fa11f1b6b497dc37d7ce79&vids=1&msclkid=N&pi=918639831&l.

15 of 71 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 “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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

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