mobiel.nl website review

Fastly costs a phone 1.9 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.

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

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

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

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

4 third-party services load with your homepage (Fastly, Mixpanel and Google Tag Manager and others), adding 2.7 MB and 2.0 s of main-thread time.

Your mobile performance score is 55 (desktop: 77). Pages that score under 90 lose visitors before the first paint.

The HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 876 ms on a phone.

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

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

imgix costs a phone 0 ms of main-thread work and 1.4 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.

Your server takes 976 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

1 file is served with short cache lifetimes, so returning visitors download them again (31 KiB).

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

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.

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

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

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

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

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

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-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.1 MB in 135 requests on a phone: images 1.4 MB (75), scripts 1.3 MB (44) and fonts 337 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

<td> elements in a large <table> do not have table headers. (1 element).

There are 2 <h1> headlines (“Te veel betalen voor hetzelfde abonnement?” and “Te veel betalen voor hetzelfde abonnement?”). One clear main headline is easier for people and search engines.

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

The homepage links to 552 pages on mobiel.nl and 11 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.

There is no https://www.mobiel.nl/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.

https://www.mobiel.nl/cookies, https://www.mobiel.nl/abonnement/hollandsnieuwe/aanbiedingen and https://www.mobiel.nl/abonnement/odido/aanbiedingen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.mobiel.nl/cookies, https://www.mobiel.nl/winkelwagen and https://www.mobiel.nl/vragen-en-contact have no meta description, so Google writes the search snippet from whatever text it finds.

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

Large scripts ship without source maps.

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 2,181 words of visible text.

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