quiksilver.com website review

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

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

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

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

14 images could be 766 KiB 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.

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

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

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

Shopify costs a phone 411 ms of main-thread work and 472 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 239 ms of main-thread work and 612 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.

Optanon costs a phone 73 ms of main-thread work and 302 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.

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

About 62 KiB of CSS is downloaded but never applied on this page.

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

12 KiB could be saved by minifying JavaScript.

11 KiB JavaScript is shipped twice across bundles.

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.

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.

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

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

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

For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.

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

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

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

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

Your homepage downloads 13.8 MB in 563 requests on a phone: media 7.3 MB (2), images 2.8 MB (126) and scripts 2.0 MB (132). Under 2 MB keeps phones on slow connections fast.

7147da53daf7481fb149cfc51a89320d.thumbnail.0000000000.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 3.90 g of CO₂e: 468.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.quiksilver.com/search?q={search_term_string}")”.

The homepage links to 236 pages on quiksilver.com and 3 external pages.

There is no https://www.quiksilver.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.quiksilver.com/pages/gift-guide has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://www.ojrq.net/p/?return=&cid=53003&tpsync=no&auth=.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 32 cookies (measured from a US location before any click).

Loading the homepage contacts 59 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.