Website review, no card needed
actief.be website review
Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 89 checks
This review found 33 issues worth fixing on actief.be, 14 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 145 ms |
| May 16, 2026 | 145 ms |
| May 23, 2026 | 147 ms |
| May 30, 2026 | 148 ms |
| Jun 6, 2026 | 151 ms |
| Jun 13, 2026 | 150 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 151 ms |
| Jul 4, 2026 | 151 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 150 ms |
| Jul 25, 2026 | 149 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 149 ms |
| Aug 15, 2026 | 148 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 140 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 144 ms |
| Oct 24, 2026 | 146 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.2 s · 381 KiBAbout 381 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.6 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 329 ms. During a long task the page ignores taps.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Use efficient cache lifetimes
272 KiB11 files are served with short cache lifetimes, so returning visitors download them again (272 KiB).
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Cookiebot and openai.com and others), adding 560 KiB and 360 ms of main-thread time.
Reduce unused CSS
200 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 200 ms faster on a phone.
Improve image delivery
150 ms · 26 KiB1 image could be 26 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
50 ms · 24 KiB24 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 961 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.1 s
6.1 sYour largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Homepagina Actief”.
Time to Interactive: 10.8 s
10.8 sThe page becomes fully interactive after 10.8 s. Good is under 3.8 s.
Total Blocking Time: 508 ms
508 msScripts block taps and scrolling for 508 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 145 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 472 ms
472 msReal visitors wait 472 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.073
0.073The layout barely moves while loading (CLS 0.073, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 53.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 46 requests
1.6 MBYour homepage downloads 1.6 MB in 46 requests on a phone: scripts 986 KiB (10), images 431 KiB (20) and fonts 69 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 13 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (17 characters)
Your title is only 17 characters: “Welkom bij Actief”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
90 internal links, 1 external
The homepage links to 90 pages on actief.be and 1 external page.
5 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Actief ✓ HR partner ✓ De leukste vacatures in jouw buurt ✓ Meer dan 8000 vacatures ✓ Meer dan 90 kantoren ✓ Solliciteer…”.
One H1 headline
Your main headline reads: “Welkom bij Actief”.
Canonical URL set
The canonical URL is https://www.actief.be/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.actief.be/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.actief.be/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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (832 words), so crawlers that don't run JavaScript still read it.
Other pages
14 linked pages are broken
Your homepage links to https://www.actief.be/nl/nl/vacatures, https://www.actief.be/nl/nl/vacatures/zoek-vacatures, https://www.actief.be/nl/nl/vacatures/schrijf-je-in, https://www.actief.be/nl/nl/vacatures/vacature-alert, https://www.actief.be/nl/nl/onze-diensten and https://www.actief.be/nl/nl/werkgevers and 8 others, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page points its canonical at the homepage
https://www.actief.be/fr declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
5 checks passed
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
58 of 62 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,004 words of copy
The homepage carries about 1,004 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
1 call to action
The homepage has 1 call to action, for example “Contact”.
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at actief.be, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Analytics
- Hosting
- Fundaments
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on actief.be, including 12 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.