Website review, no card needed

appm.nl logo

appm.nl website review

Visit site (opens in a new tab)Reviewed 24 October 202631 issues · 77 checks

This review found 31 issues worth fixing on appm.nl, 8 of them high impact, across 77 checks. The most urgent: page weight: 4.4 MB in 59 requests. 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.7 s599 msMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 2026969 ms
May 9, 20261.0 s
May 16, 2026969 ms
May 23, 2026822 ms
May 30, 2026825 ms
Jun 6, 2026725 ms
Jun 13, 2026921 ms
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
91 ms71 msMay 2Jun 2789 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202680 ms
May 9, 202679 ms
May 16, 202673 ms
May 23, 202675 ms
May 30, 202677 ms
Jun 6, 202676 ms
Jun 13, 202685 ms
Jun 20, 202688 ms
Jun 27, 202689 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 appm.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. appm.nl at 0.7 s0.7 s
  2. appm.nl at 1.4 s1.4 s
  3. appm.nl at 2.1 s2.1 s
  4. appm.nl at 2.7 s2.7 s
  5. appm.nl at 3.4 s3.4 s
  6. appm.nl at 4.1 s4.1 s
  7. appm.nl at 4.8 s4.8 s
  8. appm.nl at 5.5 s5.5 s

Speed

7 to fix87
  • Improve image delivery

    1.9 MB

    23 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 87

    87/100

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

  • Render-blocking requests

    500 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 500 ms.

  • Reduce unused JavaScript

    300 ms · 134 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, LightWidget and cloudfront.net and others), adding 3.1 MB and 82 ms of main-thread time.

  • Use efficient cache lifetimes

    299 KiB

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

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 2.9 MB 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 long tasks on the main thread

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

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 255 ms of it running JavaScript. That is comfortably low.

  • Server response: 211 ms

    211 ms

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

Core Web Vitals

5 to fix100
  • Speed Index: 10.7 s

    10.7 s

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

  • Time to Interactive: 13.0 s

    13.0 s

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

  • Largest content (LCP) got 42% slower for real visitors

    +42%

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

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nederland mooier maken. Dat is waar APPM voor staat en gaat…”. Most of its time is element render delay (4.4 s).

  • 1 image without width and height

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

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

    +11%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 80 ms to 89 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.3 s

    1.3 s

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

  • 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: 1.0 s

    1.0 s

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

  • Real-user TTFB: 738 ms

    738 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.029

    0.029

    The layout barely moves while loading (CLS 0.029, good is under 0.1).

  • Total Blocking Time: 23 ms

    23 ms

    Scripts block the page for only 23 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 4.4 MB in 59 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 59 requests on a phone: images 2.9 MB (27), fonts 904 KiB (3) and scripts 494 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    01KHX6T307K5Y1PRT2SVHEBZSA___responsive_425_283.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).

  • 21 images in older formats

    21 images (1.0 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.

  • About 1.2 g of CO₂ per visit

    1.25 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.25 g of CO₂e: 149.8 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

5 to fixGoogle 8791
  • 3 text elements with low contrast

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

  • 2 tap targets too small

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

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

    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.

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

4 to fixGoogle 10076
  • No H1 headline

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

  • Title is short (29 characters)

    Your title is only 29 characters: “Nederland mooier maken - APPM”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • No robots.txt

    There is no robots.txt at appm.nl/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 51 internal links, 4 external

    The homepage links to 51 pages on appm.nl and 4 external pages.

4 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Nederland mooier maken. Dat is waar APPM voor staat en gaat. We werken aan opgaven in stedelijk én landelijk gebied. En…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: WebPage.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.appm.nl/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.appm.nl/expertises has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.appm.nl/werkvelden, https://www.appm.nl/expertises, https://www.appm.nl/appmers and https://www.appm.nl/over-appm have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.appm.nl/werkvelden and https://www.appm.nl/expertises have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 8 pages slow to respond

    https://www.appm.nl/werkvelden/gebiedsontwikkeling, https://www.appm.nl/werkvelden/infrastructuur, https://www.appm.nl/werkvelden/landelijk-gebied, https://www.appm.nl/werkvelden/water, https://www.appm.nl/expertises/beleid-en-strategie and https://www.appm.nl/expertises/bestuur-en-organisatie 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 35 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.

  • 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 9696
  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 332 words of visible text.

3 checks passed
  • 1 call to action

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 4 other companies contacted

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

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics

Company

Employees
110
Headquarters
Hoofddorp

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on appm.nl, including 12 speed issues, 4 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