gottexswim.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 2.3 MB and 1.1 s of main-thread time.

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

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

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

Google Tag Manager costs a phone 346 ms of main-thread work and 686 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 195 ms of main-thread work and 633 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.

Klaviyo costs a phone 115 ms of main-thread work and 331 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 54 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.

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

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

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

10 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 8.0 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 7.3 s (Speed Index). Good is under 3.4 s.

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

Your homepage downloads 6.0 MB in 496 requests on a phone: scripts 2.6 MB (157), images 1.7 MB (23) and other files 1.4 MB (284). Under 2 MB keeps phones on slow connections fast.

a24dc74e-67d1-4e0b-b511-ec330e1b775d.jpeg weighs 1.2 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example a24dc74e-67d1-4e0b-b511-ec330e1b775d.jpeg at 1,311 px wide, shown at 185 px. Resized copies would save about 996 KiB.

1 image (1.2 MB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

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

Some list items are not inside a list.

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (4 elements).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Shopping from the USA or Canada?” and “Gottex Swimwear”). One clear main headline is easier for people and search engines.

The homepage links to 230 pages on gottexswim.com and 2 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://gottexswim.com/collections/new-collection and https://gottexswim.com/collections/new-swimwear all use the title “New in Swimwear - 2025 Collection | Gottex Swimwear”. Search engines can't tell which page to show for a search, so each competes with the others.

https://gottexswim.com/pages/new-collection-2024, https://gottexswim.com/collections/new-swimwear, https://gottexswim.com/collections/black-one-piece and https://gottexswim.com/collections/swimsuit-shop-all have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://gottexswim.com/pages/new-collection-2024, whose canonical is https://gottexswim.com/pages/collections. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 739 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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