surfsidesupply.com website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and rebuyengine.com and others), adding 1.4 MB and 1.2 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 265 ms of main-thread work and 345 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 127 ms of main-thread work and 332 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.

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 136 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.6 MB in 309 requests on a phone: scripts 2.1 MB (86), images 2.0 MB (34) and other files 1.1 MB (170). Under 2 MB keeps phones on slow connections fast.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

165 buttons have no accessible name, so screen readers announce just “button”.

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

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

All page content should be contained by landmarks: 10 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.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 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 meta description is 270 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, ClothingStore and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("www.surfsidesupply.com")”.

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

Your <h1> is empty.

The homepage links to 169 pages on surfsidesupply.com and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.surfsidesupply.com/collections/mens-fall-arrivals, https://www.surfsidesupply.com/collections/travel-essentials, https://www.surfsidesupply.com/collections/mens-shop-all/mens, https://www.surfsidesupply.com/collections/t-shirts-henleys-polos/mens, https://www.surfsidesupply.com/collections/shirts/mens and https://www.surfsidesupply.com/collections/sweatshirts-fleece/mens and 2 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.surfsidesupply.com/collections/overshirts-shirt-jackets and https://www.surfsidesupply.com/collections/shackets all use the title “Overshirts & Shirt Jackets – Surfside Supply Co.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.surfsidesupply.com/collections/sweaters has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.surfsidesupply.com/collections/sweatshirts-fleece and https://www.surfsidesupply.com/collections/sweatshirts-fleece/mens use the same meta description. A description written for each page earns more clicks.

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

115 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 error was 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.

Social proof on the homepage: 70 testimonial or review blocks. 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.

The homepage has only about 55 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.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Meta Pixel (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 15 cookies, 11 of them by other companies (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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.