atomium.be website review

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

The page goes through 1 redirect before it starts loading, costing about 27.8 s. Link and advertise the final URL directly.

About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 21.8 s faster on a phone.

About 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.7 s faster on a phone.

34 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

189 KiB could be saved by minifying JavaScript.

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

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

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

70 KiB could be saved by minifying CSS.

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

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

3 third-party services load with your homepage (Cloudflare CDN, Google Fonts and Hubspot), adding 11 KiB and 6 ms of main-thread time.

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.

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

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.1 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 24.6 MB in 730 requests on a phone: images 13.7 MB (87), scripts 8.0 MB (540) and stylesheets 2.5 MB (98). Under 2 MB keeps phones on slow connections fast.

10 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

23 images (11.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.

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

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

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

29 tap targets are too small or too close together to hit reliably with a finger.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

Headings should not be empty: 25 elements on the page fail this check, rated minor by axe-core.

9 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.

Headings skip levels (h1 → h6, h1 → h6 and h1 → h6), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 7 characters: “Atomium”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://atomium.be/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at atomium.be/robots.txt, the first file search crawlers ask for.

3 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 113 pages on atomium.be and 8 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.

/, /Home/Index and /tickets all use the title “Atomium”. Search engines can't tell which page to show for a search, so each competes with the others.

/Home/Index, /atomium-opening_hours, /webshop, /contact, /offer_for_groups and /offer_for_schools and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/jobs has 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.

/discover, /practical_information, /offer_for_tourism_professionals, /jobs and /tickets took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://atomium.be/bundles/Flexpage/coockestyle' because its MIME type ('text/html') is no…”.

Large scripts ship without source maps.

15 links from your homepage to your own site are broken, for example https://atomium.be/Home/Index (500).

Your certificate from Let's Encrypt · YE1 expires in 4 days. If it doesn't renew automatically, visitors get a security warning.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

atomium.be has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 444 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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