technicum-engineering.nl website review

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

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

6 third-party services load with your homepage (Google Tag Manager, Clarity and JSDelivr CDN and others), adding 719 KiB and 607 ms of main-thread time.

Google Tag Manager costs a phone 475 ms of main-thread work and 389 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

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

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

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

About 18 KiB of CSS is downloaded but never applied on this page.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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.

technicum-engineering-teamwork-empower.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example technicum-engineering-teamwork-empower.webp at 1,680 px wide, shown at 390 px. Resized copies would save about 49 KiB.

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 28 characters: “Voor technisch professionals”. 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.

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

No XML sitemap at https://usgengineering.nl/sitemap-index.xml, so Google discovers your pages only by following links.

The homepage links to 109 pages on technicum-engineering.nl and 6 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.

/ik-zoek-werk/vacatures/per-provincie and /ik-zoek-werk/vacatures/per-provincie/meer-provincies all use the title “Per provincie”. Search engines can't tell which page to show for a search, so each competes with the others.

/professionals, /opdrachtgevers, /ik-zoek-werk/vacatures/per-provincie and /ik-zoek-werk/vacatures/per-provincie/meer-provincies have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /ik-zoek-werk/vacatures/per-provincie/meer-provincies, whose canonical is /ik-zoek-werk/vacatures/per-provincie. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

5 of 9 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 “Refused to execute script from 'https://technicum-engineering.nl/Frontend-Assembly/Telerik.Sitefinity.Frontend/Mvc/Scri…”.

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 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 432 words of visible text.

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