larex.eu website review

1 image could be 437 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

5 third-party services load with your homepage (Google Tag Manager, Google Maps and Cookiebot and others), adding 570 KiB and 713 ms of main-thread time.

Google Tag Manager costs a phone 282 ms of main-thread work and 171 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 272 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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.

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.

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

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

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

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

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

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

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

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

selfie-01.jpg weighs 612 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example selfie-01.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 484 KiB.

1 image (612 KiB) is 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 0.37 g of CO₂e: 45.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your meta description is only 27 characters: “Home | Larex | EU Personnel”. 70 to 160 characters is enough to sell the click.

There are 7 <h1> headlines (“greetings from holland”, “Looking for a long term job in The Netherlands?” and “working with a certified, reliable temporary empl…”). One clear main headline is easier for people and search engines.

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 90 pages on larex.eu 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 https://www.larex.eu/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.larex.eu/en/for-employees/refer-a-craftsman and https://www.larex.eu/en/for-employees/from-freelance-to-employement- all use the title “From freelance to employment - Larex”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.larex.eu/en/vacancies, https://www.larex.eu/en/vacancies/electrical-engineering, https://www.larex.eu/en/vacancies/installation-technology, https://www.larex.eu/en/vacancies/construction, https://www.larex.eu/en/vacancies/dismantling and https://www.larex.eu/en/vacancies/civil-and-infrastructure and 9 others 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 https://www.larex.eu/en/for-employees/refer-a-craftsman, whose canonical is https://www.larex.eu/en/for-employees/from-freelance-to-employement-. 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 45 found) and read each the way a search engine does.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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.

The homepage carries about 604 words of visible text.

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

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

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