weekendswim.com website review

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

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

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

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

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

6 third-party services load with your homepage (route.com, Klaviyo and Shopify and others), adding 1.3 MB and 526 ms of main-thread time.

route.com costs a phone 425 ms of main-thread work and 1.1 MB 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.

485 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “COMBanners-FloralGingham-Launch-Mobile_2_2x_d8126566-ed10-4…”.

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

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

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

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 7.7 MB in 291 requests on a phone: images 5.1 MB (118), scripts 1.5 MB (57) and other files 767 KiB (96). Under 2 MB keeps phones on slow connections fast.

COMBanners-WSPoolsidePetals-Launch-Mobile_2x_d6f10c3c-2fdb-4 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 2.17 g of CO₂e: 260.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

[aria-*] attributes do not have valid values (1 element).

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h2 → h6), 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 12 characters: “Weekend Swim”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 221 pages on weekendswim.com and 4 external pages.

https://www.weekendswim.com/collections/all, https://www.weekendswim.com/collections/new-arrivals, https://www.weekendswim.com/collections/labor-day-sale, https://www.weekendswim.com/collections/vacation-collection, https://www.weekendswim.com/collections/saturday and https://www.weekendswim.com/collections/sunday have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.weekendswim.com/products/green-ruffle-sleeve-rashgaurd-swimsuit and https://www.weekendswim.com/products/pink-ruffle-sleeve-rashgaurd-swimsuit use the same meta description. A description written for each page earns more clicks.

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Amplitude, 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 10 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.