studioesr.com website review

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

About 319 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

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

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

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

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

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

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

8 third-party services load with your homepage (Affirm, Twitter and Hexton and others), adding 662 KiB and 256 ms of main-thread time.

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 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.

4 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 5.5 MB in 475 requests on a phone: images 3.5 MB (286), other files 840 KiB (125) and scripts 727 KiB (48). Under 2 MB keeps phones on slow connections fast.

10 images further down the page (233 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 dropdown has no label.

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

Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 10 characters: “Studio ESR”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

Your <h1> is empty.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 297 pages on studioesr.com and 17 external pages.

https://studioesr.com/collections, https://studioesr.com/collections/t-shirts, https://studioesr.com/collections/hoodies, https://studioesr.com/collections/long-sleeves, https://studioesr.com/collections/bottoms and https://studioesr.com/collections/socks and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

49 of 70 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_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 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: 372 testimonial or review blocks. 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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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