local.nl website review

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

17 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

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

About 250 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 670 ms faster on a phone.

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

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

6 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google Maps and others), adding 543 KiB and 233 ms of main-thread time.

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

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

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

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

Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Van spot naar spot on”. Most of its time is element render delay (2.2 s).

The first text or image appears after 2.5 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.

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 2.1 MB in 29 requests on a phone: images 1.3 MB (10), scripts 510 KiB (10) and fonts 243 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

Your title is only 12 characters: “Home - Local”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 16 characters: “Local is spot on”. 70 to 160 characters is enough to sell the click.

The homepage links to 15 pages on local.nl and 0 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 /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.

/over, /projecten, /team, /nieuws, /vacature-projectontwikkelaar-in-den-haag and /contact and 5 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /team, whose canonical is /over-local. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/projecten, /team, /nieuws, /vacature-projectontwikkelaar-in-den-haag, /contact and /nieuws/bouwvergunning-park-heuvellaan-hilversum-is-binnen have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/projecten, /team, /nieuws and /vacature-projectontwikkelaar-in-den-haag took over 3 s to send their HTML from our server.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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 Analytics and Google Tag Manager (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 2 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.