inkster.nl website review

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

ablyft.com costs a phone 1.3 s of main-thread work and 36 KiB 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.

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

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

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

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

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

About 85 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

Google Tag Manager costs a phone 602 ms of main-thread work and 803 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 590 ms of main-thread work and 788 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.

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

Klaviyo costs a phone 164 ms of main-thread work and 373 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 56 KiB JavaScript that modern phones do not need.

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

16 KiB could be saved by minifying JavaScript.

3 images could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

5 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 170 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 399 requests on a phone: scripts 2.8 MB (133), other files 1.0 MB (120) and images 834 KiB (121). Under 2 MB keeps phones on slow connections fast.

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

3 buttons have no accessible name, so screen readers announce just “button”.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 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).

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

1 link has no real href, so search engines can't follow it.

The homepage links to 440 pages on inkster.nl 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://inkster.nl/collections/alle-produkte and https://inkster.nl/collections/anime-drop all use the title “Alle Tijdelijke Tatoeages | Inkster”. Search engines can't tell which page to show for a search, so each competes with the others.

https://inkster.nl/collections/maskulin, https://inkster.nl/collections/custom-tattoos, https://inkster.nl/collections/komplementarprodukte, https://inkster.nl/pages/unser-team and https://inkster.nl/collections/tattoo-sleeves have no meta description, so Google writes the search snippet from whatever text it finds.

https://inkster.nl/collections/alle-produkte, https://inkster.nl/collections/neue-designs, https://inkster.nl/collections/maskulin, https://inkster.nl/collections/anime-drop, https://inkster.nl/collections/tattoo-stift-alle-produkte and https://inkster.nl/products/winter-starter-set-deal and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://inkster.nl/.

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

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

Requests the notification permission on page load.

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 907 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 5 mores (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 32 cookies, 2 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 63 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.