timetohire.nl website review

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

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Hubspot and others), adding 486 KiB and 462 ms of main-thread time.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We gebruiken cookies om uw browse-ervaring te verbeteren, g…”. Most of its time is element render delay (5.4 s).

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

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

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

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 33.9 MB in 82 requests on a phone: media 32.4 MB (4), images 639 KiB (32) and scripts 508 KiB (19). Under 2 MB keeps phones on slow connections fast.

6 images (336 KiB) 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 9.60 g of CO₂e: 1152.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Contentinfo landmark should not be contained in another landmark: 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.

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

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

Your meta description is only 29 characters: “Bold Moves, Brilliant People.”. 70 to 160 characters is enough to sell the click.

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

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

The homepage links to 76 pages on timetohire.nl and 16 external pages.

There is no https://timetohire.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.

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

1 image failed to load on a phone, for example https://z.strds.nl/jq.png?id=94be5961&c=%7B%22_stfv%22%3A1792793520.1655092%2C%22hubspotutk%22%3A%22e582615c5886b45ad071df91e1c73bda%22%2C%22c%22%3A6%2C%22f%22%3A0%2C%22h%22%3A2%2C%22p%22%3A5%2C%22w%2.

4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'ready')”.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 7 cookies (measured from a US location before any click).

Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.