archipelago-store.com website review

About 716 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.

hcaptcha.com costs a phone 1.4 s of main-thread work and 1.2 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 23. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (hcaptcha.com, Shopify and Google CDN and others), adding 3.5 MB and 2.0 s of main-thread time.

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

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

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

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

Google CDN costs a phone 192 ms of main-thread work and 298 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.

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

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

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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 5.6 MB in 520 requests on a phone: scripts 2.5 MB (262), images 1.1 MB (29) and other files 1.0 MB (175). Under 2 MB keeps phones on slow connections fast.

20 images further down the page (778 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

Your <h1> is empty.

The homepage links to 79 pages on archipelago-store.com and 0 external pages.

https://archipelago-store.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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

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