Website review, no card needed

artra.nl logo

artra.nl website review

Visit site (opens in a new tab)Reviewed 21 October 202644 issues · 90 checks

This review found 44 issues worth fixing on artra.nl, 18 of them high impact, across 90 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of artra.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. artra.nl at 1.0 s1.0 s
  2. artra.nl at 1.9 s1.9 s
  3. artra.nl at 2.9 s2.9 s
  4. artra.nl at 3.8 s3.8 s
  5. artra.nl at 4.8 s4.8 s
  6. artra.nl at 5.7 s5.7 s
  7. artra.nl at 6.7 s6.7 s
  8. artra.nl at 7.6 s7.6 s

Speed

12 to fix21
  • Improve image delivery

    7.7 s · 1.8 MB

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

  • Render-blocking requests

    4.9 s

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

  • Mobile performance score: 21

    21/100

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

  • Main-thread work: 4.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Clarity and others), adding 1.0 MB and 1.2 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 305 KiB

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

  • Google Tag Manager adds 664 ms

    664 ms

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

  • Font display

    700 ms

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

  • Reduce unused CSS

    450 ms · 204 KiB

    About 204 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 14 long tasks on the main thread

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

  • FontAwesome CDN adds 271 ms

    271 ms

    FontAwesome CDN costs a phone 271 ms of main-thread work and 246 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.

  • 2,477 HTML elements

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

  • Use efficient cache lifetimes

    150 ms · 47 KiB

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

  • Minify CSS

    150 ms · 14 KiB

    14 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Phones get a much slower page than desktops

    Desktop scores 72 but mobile only 21. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Forced reflow

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

1 checks passed
  • Server response: 330 ms

    330 ms

    Your server sent the HTML in 330 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix24
  • Largest Contentful Paint: 22.3 s

    22.3 s

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

  • Time to Interactive: 22.9 s

    22.9 s

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

  • First Contentful Paint: 6.1 s

    6.1 s

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

  • Speed Index: 10.6 s

    10.6 s

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

  • Cumulative Layout Shift: 0.32

    0.32

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

  • Total Blocking Time: 794 ms

    794 ms

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    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.

Images and page weight

5 to fix28
  • Page weight: 6.0 MB in 152 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 152 requests on a phone: images 4.3 MB (64), scripts 1.3 MB (42) and fonts 145 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    wat-ga-jij-morgen-doen.png weighs 620 KiB. On a phone connection a single image that size takes seconds.

  • 18 images in older formats

    18 images (2.3 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.

  • 16 images below the first screen load straight away

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

  • 1 image far larger than shown

    258 KiB

    1 image is downloaded at several times the size a phone draws it, for example team-artra-scaled.jpg at 2,560 px wide, shown at 366 px. Resized copies would save about 258 KiB.

  • About 1.7 g of CO₂ per visit

    1.69 g

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

Accessibility

11 to fixGoogle 8489
  • Unlabelled dropdowns

    3 dropdowns have no label.

  • 21 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (16 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

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

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • ARIA role should be appropriate for the element (9 elements)

    ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.

  • Table header text should not be empty (1 element)

    Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

2 checks passed
  • Every image has alt text

    All 61 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 62 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

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

  • No XML sitemap

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

  • 111 internal links, 7 external

    The homepage links to 111 pages on artra.nl and 7 external pages.

5 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “artra is de opleider voor arbeidsmarktprofessionals. Werk jij in de flexbranche en wil je je ontwikkelen? Bekijk dan sn…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “artra | dé opleider voor arbeidsmarktprofessionals”.

  • Canonical URL set

    The canonical URL is https://www.artra.nl/.

  • Structured data in place

    Structured data found: Article, Organization, Person, Place and WebPage.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,724 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://artra.nl/evalueren is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://artra.nl/evalueren and https://artra.nl/inloggen-bij-artra have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages slow to respond

    https://artra.nl/opleidingen/commercieel, https://artra.nl/opleidingen/communicatie, https://artra.nl/opleidingen/detachering, https://artra.nl/opleidingen/kennis, https://artra.nl/opleidingen/recruitment and https://artra.nl/opleidingen/e-learning and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97226923&tm=gtm002&Ver=2&mid=52cb217f-3dc6-4ea9-9837-0ab133e72df3&bo=1&sid=c5d040c0cda411f1b59c59d27d5c5f45&vid=c5d061d0cda411f197aaefc2caa0bce9&vids=1&msclkid=N&gtm_t.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.artra.nl/wp-content/plugins/vuejs-signup-form/dist/fonts/Montserrat-Regular.otf' from or…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    24 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No call to action on the first 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.

  • Local business without LocalBusiness data

    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.

  • No opening hours

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

  • 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,896 words of copy

    The homepage carries about 1,896 words of visible text.

6 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Contact & Advies”.

  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 147 testimonial or review blocks and 14 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.

  • 15 cookies set on arrival

    15

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 artra.nl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on artra.nl, including 19 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25