nl-ix.net website review

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

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

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

8 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

8 images could be 753 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

Google CDN costs a phone 93 ms of main-thread work and 351 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.

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

4 third-party services load with your homepage (Google CDN, cookiefirst.com and Other Google APIs/SDKs and others), adding 567 KiB and 109 ms of main-thread time.

Polyfills for old browsers add 44 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.

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.

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

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

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We may place these for analysis of our visitor data, to imp…”. Most of its time is element render delay (4.7 s).

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

Real visitors wait 957 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 5.2 MB in 92 requests on a phone: images 3.4 MB (46), scripts 940 KiB (9) and other files 653 KiB (31). Under 2 MB keeps phones on slow connections fast.

40 images further down the page (3.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

34 images (3.1 MB) 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 1.46 g of CO₂e: 175.5 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”.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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.

Your title is 86 characters, so Google will cut it off around 60: “NL-ix | Europe’s Leading Internet Exchange – Peering, Cloud, and Connectivity Services”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 111 pages on nl-ix.net and 4 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.nl-ix.net/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.nl-ix.net/about/about-our-network/eu-stats and https://www.nl-ix.net/locations/datacenters 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.

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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.

The homepage carries about 742 words of visible text.

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