motelrocks.com website review

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

Clarity costs a phone 2.2 s of main-thread work and 29 KiB 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 479 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

75 files are served with short cache lifetimes, so returning visitors download them again (10.1 MB).

8 third-party services load with your homepage (Clarity, Klaviyo and userway.org and others), adding 1.2 MB and 3.1 s of main-thread time.

About 116 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.

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

Klaviyo costs a phone 240 ms of main-thread work and 330 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.

userway.org costs a phone 172 ms of main-thread work and 489 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.

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

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

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

13 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 19.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Motel Denim + You. The perfect pair”.

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

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

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

The layout shifts by 0.352 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

6 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 41.8 MB in 508 requests on a phone: images 19.3 MB (55), media 18.3 MB (10) and other files 2.0 MB (304). Under 2 MB keeps phones on slow connections fast.

SMALL_BOX_NAV_760f2a43-e9c2-4fcb-94fa-68593958084e.jpg 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 11.84 g of CO₂e: 1420.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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.

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 74 characters, so Google will cut it off around 60: “Vintage & Printed Women's Fashion & Clothes - Motel Rocks – motelrocks.com”.

There are 4 <h1> headlines (“Meet me at midnight”, “Meet me at midnight” and “Motel Denim + You.”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

The homepage links to 244 pages on motelrocks.com and 23 external pages.

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

https://www.motelrocks.com/collections/new-in, https://www.motelrocks.com/collections/new-tops, https://www.motelrocks.com/collections/new-dresses, https://www.motelrocks.com/collections/new-jeans, https://www.motelrocks.com/collections/new-skirts and https://www.motelrocks.com/collections/new-knitwear and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.motelrocks.com/collections/new-tops and https://www.motelrocks.com/collections/new-dresses 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.

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

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

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

1 image is served at too low a resolution for sharp phone screens.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Analytics, Hotjar, Klaviyo and Microsoft Clarity (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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.