buttonamsterdam.com website review

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

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

31 images could be 851 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Facebook and others), adding 1.5 MB and 878 ms of main-thread time.

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

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

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

Klaviyo costs a phone 141 ms of main-thread work and 329 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 100 ms of main-thread work and 580 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.

150 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 200 ms faster on a phone.

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

85 KiB could be saved by minifying JavaScript.

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

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.

Real visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

Your largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to ensure you get the best experi…”.

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

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

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 10.7 MB in 395 requests on a phone: media 4.3 MB (2), images 2.6 MB (91) and scripts 2.2 MB (121). Under 2 MB keeps phones on slow connections fast.

IMG_4442.heic 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).

4 images are downloaded at several times the size a phone draws them, for example jeans-aw2026-57947382972741-BA28_900x.jpg at 900 px wide, shown at 294 px. Resized copies would save about 22 KiB.

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

Some list items are not inside a list.

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

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

There are 2 <h1> headlines (“” and “VERANO ETERNO”). One clear main headline is easier for people and search engines.

The homepage links to 92 pages on buttonamsterdam.com and 6 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/collections/all, /customer_authentication/redirect, /collections/button-covers, /policies/shipping-policy, /pages/pre-black-friday-bundles and /collections/gifts and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /customer_authentication/redirect, /collections/button-covers, /pages/pre-black-friday-bundles, /products/pin-1-set and /collections/flower-buttons and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/blouse and /products/button-amsterdam-gift-card took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://www.buttonamsterdam.com/.

4 errors were logged to the browser console while the page loaded, for example “Error: <path> attribute d: Expected number, "….8743 13 12.0625C13 11.6481 12.8…".”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

2 links go through two or more redirects, for example https://www.buttonamsterdam.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

buttonamsterdam.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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

buttonamsterdam.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be buttonamsterdam.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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