Website review, no card needed

staad-groep.nl logo

staad-groep.nl website review

Visit site (opens in a new tab)Reviewed 18 October 202640 issues · 89 checks

This review found 40 issues worth fixing on staad-groep.nl, 16 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
1.0 s754 msApr 25Oct 10787 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026944 ms
May 2, 2026923 ms
May 9, 2026923 ms
May 16, 2026855 ms
May 23, 2026838 ms
May 30, 2026799 ms
Jun 6, 2026847 ms
Jun 13, 2026891 ms
Jun 20, 2026944 ms
Jun 27, 2026944 ms
Jul 4, 2026913 ms
Jul 11, 2026886 ms
Jul 18, 2026836 ms
Jul 25, 2026790 ms
Aug 1, 2026799 ms
Aug 8, 2026799 ms
Aug 15, 2026825 ms
Aug 22, 20261.0 s
Aug 29, 2026981 ms
Sep 5, 2026981 ms
Sep 12, 2026981 ms
Sep 19, 2026933 ms
Sep 26, 2026904 ms
Oct 3, 2026879 ms
Oct 10, 2026787 ms
Real-visitor tap response (INP)75th percentile, phones
144 ms91 msApr 25Oct 10138 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026102 ms
May 2, 2026102 ms
May 9, 202697 ms
May 16, 2026101 ms
May 23, 2026104 ms
May 30, 2026104 ms
Jun 6, 2026111 ms
Jun 13, 2026111 ms
Jun 20, 2026106 ms
Jun 27, 2026112 ms
Jul 4, 2026111 ms
Jul 11, 2026112 ms
Jul 18, 2026117 ms
Jul 25, 2026121 ms
Aug 1, 2026124 ms
Aug 8, 2026128 ms
Aug 15, 2026128 ms
Aug 22, 2026132 ms
Aug 29, 2026135 ms
Sep 5, 2026132 ms
Sep 12, 2026135 ms
Sep 19, 2026137 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026138 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

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

How it loaded on a phone

  1. staad-groep.nl at 1.0 s1.0 s
  2. staad-groep.nl at 1.9 s1.9 s
  3. staad-groep.nl at 2.9 s2.9 s
  4. staad-groep.nl at 3.9 s3.9 s
  5. staad-groep.nl at 4.8 s4.8 s
  6. staad-groep.nl at 5.8 s5.8 s
  7. staad-groep.nl at 6.7 s6.7 s
  8. staad-groep.nl at 7.7 s7.7 s

Speed

11 to fix13
  • Use efficient cache lifetimes

    3.0 s · 1.3 MB

    40 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

  • Render-blocking requests

    4.0 s

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

  • Improve image delivery

    1.3 s · 1.6 MB

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

  • Reduce unused CSS

    1.6 s · 265 KiB

    About 265 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Mobile performance score: 13

    13/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 961 KiB and 1.8 s of main-thread time.

  • Google Tag Manager adds 992 ms

    992 ms

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

  • Reduce unused JavaScript

    539 KiB

    About 539 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.5 s

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

  • 11 long tasks on the main thread

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

  • Facebook adds 325 ms

    325 ms

    Facebook costs a phone 325 ms of main-thread work and 223 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.

  • Document request latency

    92 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    88 KiB

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

  • Font display

    50 ms

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

  • Minify JavaScript

    45 KiB

    45 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 42 but mobile only 13. 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: 306 ms

    306 ms

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

Core Web Vitals

8 to fix100
  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Staad is een toonaangevend Nederlands familiebedrijf opgeri…”.

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Cumulative Layout Shift: 0.691

    0.691

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

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Tap response (INP) got 35% slower for real visitors

    +35%

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

  • Speed Index: 5.8 s

    5.8 s

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

  • 24 images without width and height

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

6 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.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

Images and page weight

4 to fix52
  • Page weight: 4.7 MB in 91 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 91 requests on a phone: images 2.7 MB (27), scripts 1.3 MB (25) and stylesheets 480 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 11 images in older formats

    11 images (1.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.

  • An image on the first screen is lazy-loaded

    staad-bg_staad17w.jpg 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).

  • 5 images below the first screen load straight away

    5 images further down the page (539 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.33 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 7386
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 10 text elements with low contrast

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

  • Hidden but focusable

    6 elements hidden from screen readers can still receive keyboard focus.

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 27 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.

  • 7 links without text

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

  • Alternative text of images should not be repeated as text (15 elements)

    Alternative text of images should not be repeated as text: 15 elements on the page fail this check, rated minor by axe-core.

  • 2 form fields without a label

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

  • Headings should not be empty (1 element)

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

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 8585
  • Title is long (106 characters)

    Your title is 106 characters, so Google will cut it off around 60: “Staad Groep - Erkend Develon importeur en dealer. En dealer van STAAD elektrische graafma…”.

  • Meta description is long (214 characters)

    Your meta description is 214 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 77 internal links, 10 external

    The homepage links to 77 pages on staad-groep.nl and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Importeur en dealer van (elektrische) grondverzetmachines”.

  • Canonical URL set

    The canonical URL is https://www.staad-groep.nl/.

  • Structured data in place

    Structured data found: BreadcrumbList and Organization.

  • 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.staad-groep.nl/sitemap/.

AI search readiness

100
  • No llms.txt

    There is no https://www.staad-groep.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 9 pages without a meta description

    https://www.staad-groep.nl/laadinfra, https://www.staad-groep.nl/offerte, https://www.staad-groep.nl/elektrische-graafmachines/staad-23lcr, https://www.staad-groep.nl/nieuws/staad-wint-if-design-awards-2026, https://www.staad-groep.nl/nieuws/staad-gaat-zelf-machines-bouwen and https://www.staad-groep.nl/elektrische-graafmachines/staad-17w and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://www.staad-groep.nl/ons-team took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 37 small tap targets

    37 of 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

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

    The homepage carries about 915 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 3 email links.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 mores (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.

  • 10 cookies set on arrival

    10

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 staad-groep.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
Vrolijk Online
Framework
jQuery
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 40 issues on staad-groep.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