scanlantheodore.com website review

Shopify costs a phone 1.4 s of main-thread work and 24.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 669 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

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

Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Shopify, ZenDesk and Google Tag Manager and others), adding 25.7 MB and 2.5 s of main-thread time.

ZenDesk costs a phone 606 ms of main-thread work and 481 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.

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

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 26.6 MB in 196 requests on a phone: media 23.9 MB (7), scripts 1.7 MB (117) and other files 516 KiB (43). Under 2 MB keeps phones on slow connections fast.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Your title is 73 characters, so Google will cut it off around 60: “Scanlan Theodore United States | Official Online Store - Scanlan Theodore”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 52 pages on scanlantheodore.com and 7 external pages.

There is no https://www.scanlantheodore.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to https://www.scanlantheodore.com/new-arrivals, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.scanlantheodore.com/us/boutiques and https://www.scanlantheodore.com/us/shipping use the same meta description. A description written for each page earns more clicks.

https://www.scanlantheodore.com/us/boutiques and https://www.scanlantheodore.com/us/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.scanlantheodore.com/us/collections/new-arrivals, https://www.scanlantheodore.com/us/collections/dresses, https://www.scanlantheodore.com/us/collections/tailoring, https://www.scanlantheodore.com/us/collections/jackets, https://www.scanlantheodore.com/us/collections/crepe-knit and https://www.scanlantheodore.com/us/collections/coordinating-sets and 4 others took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

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

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 121 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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