takeaware.nl website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Hubspot and others), adding 983 KiB and 626 ms of main-thread time.

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

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

Shopify costs a phone 178 ms of main-thread work and 326 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 163 ms of main-thread work and 324 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.

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

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

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

1 image could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

7 KiB could be saved by minifying CSS.

7 KiB could be saved by minifying JavaScript.

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 17.9 s. Good is under 3.8 s.

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

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

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

Real visitors wait 211 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 187 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 275 requests on a phone: scripts 1.6 MB (128), other files 763 KiB (98) and fonts 344 KiB (12). Under 2 MB keeps phones on slow connections fast.

3 images (143 KiB) are 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 0.89 g of CO₂e: 107.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

Headings skip levels (h2 → h5), 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 is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 207 pages on takeaware.nl and 15 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://takeaware.nl/pages/producten-bedrukken-offerte, whose canonical is https://takeaware.nl/collections/bedrukte-producten. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://takeaware.nl/pages/snelle-levering, https://takeaware.nl/pages/verzendkosten, https://takeaware.nl/pages/producten-bedrukken-offerte, https://takeaware.nl/collections/snacks, https://takeaware.nl/collections/snackbakjes and https://takeaware.nl/collections/hamburgerbakjes and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://takeaware.nl/collections/puntzakken, https://takeaware.nl/collections/kids-menuboxen, https://takeaware.nl/collections/sausbakjes, https://takeaware.nl/collections/vetvrij-papier, https://takeaware.nl/collections/foodbuckets and https://takeaware.nl/collections/saladebakken-en-bowls took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://takeaware.nl/.

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

1 error was 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.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 183 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

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

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