shorebrand.com website review

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

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

26 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

8 third-party services load with your homepage (POWr, Klaviyo and Shopify and others), adding 2.2 MB and 1.3 s of main-thread time.

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

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

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

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

POWr costs a phone 404 ms of main-thread work and 13 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.

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

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

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

rebuyengine.com costs a phone 109 ms of main-thread work and 355 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.

rise-ai.com costs a phone 99 ms of main-thread work and 306 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 205 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.

Polyfills for old browsers add 67 KiB JavaScript that modern phones do not need.

56 KiB could be saved by minifying JavaScript.

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

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

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.

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

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

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

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

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

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

The first text or image appears after 2.4 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 192 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 22.3 MB in 492 requests on a phone: images 10.7 MB (70), media 7.4 MB (3) and scripts 2.5 MB (181). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

23 images have no alt text, which hurts accessibility and image search.

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

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

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

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

Your <h1> is empty.

The homepage links to 139 pages on shorebrand.com and 1 external page.

https://shorebrand.com/collections/all, https://shorebrand.com/policies/shipping-policy, https://shorebrand.com/collections/sweaters, https://shorebrand.com/collections/womens-tops, https://shorebrand.com/collections/skirts-shorts and https://shorebrand.com/collections/womens-pants-new and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://shorebrand.com/collections/all, https://shorebrand.com/collections/womens-new-arrivals, https://shorebrand.com/collections/all-womens-dresses-new, https://shorebrand.com/collections/sweaters, https://shorebrand.com/collections/womens-tops and https://shorebrand.com/collections/skirts-shorts and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://shorebrand.com/collections/womens-tops and https://shorebrand.com/collections/womens-pants-new 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://shorebrand.com/policies/shipping-policy, https://shorebrand.com/collections/womens-new-arrivals, https://shorebrand.com/collections/all-womens-dresses-new, https://shorebrand.com/collections/womens-tops, https://shorebrand.com/collections/skirts-shorts and https://shorebrand.com/collections/womens-pants-new and 3 others took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

Large scripts ship without source maps.

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.

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 10 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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