peakdesign.com website review

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

Shopify costs a phone 1.1 s of main-thread work and 7.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and alia-prod.com and others), adding 10.1 MB and 2.6 s of main-thread time.

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

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

Google Tag Manager costs a phone 500 ms of main-thread work and 719 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.

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

alia-prod.com costs a phone 392 ms of main-thread work and 670 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.

withremark.com costs a phone 273 ms of main-thread work and 650 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 285 ms. During a long task the page ignores taps.

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

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

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

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

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.

2 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 195 ms to 195 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 3.0 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.5 MB in 437 requests on a phone: images 6.9 MB (71), scripts 3.0 MB (214) and fonts 965 KiB (21). Under 2 MB keeps phones on slow connections fast.

Home-Hero-CE-Desktop-web.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).

1 image (298 KiB) 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 3.26 g of CO₂e: 391.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 51 pages on peakdesign.com and 12 external pages.

There is no /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.

/collections/charging, /pages/charging, /collections/travel-bags, /collections/packing-cubes, /collections/outdoor-bags and /collections/phone-cases and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/sf-store has 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.

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

4 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://d3djbgmgf0l8ev.cloudfront.net/scripts/www.peakdesign.com/custom.json' violates the following Con…”.

Chrome logged issues while loading the page (“Content security policy”).

Social proof on the homepage: 3 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 386 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 25 cookies, 1 of them by other companies (measured from a US location before any click).

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