Website review, no card needed

banning.nl logo

banning.nl website review

Visit site (opens in a new tab)Reviewed 25 October 202629 issues · 85 checks

This review found 29 issues worth fixing on banning.nl, 14 of them high impact, across 85 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

Real-visitor load time (LCP)75th percentile, phones
1.5 s911 msMay 2Oct 171.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.1 s
May 9, 20261.0 s
May 16, 2026978 ms
May 23, 20261.0 s
May 30, 2026998 ms
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.1 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
77 ms64 msMay 2Oct 1769 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202670 ms
May 9, 202665 ms
May 16, 202669 ms
May 23, 202668 ms
May 30, 202666 ms
Jun 6, 202675 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202671 ms
Jul 4, 202669 ms
Jul 11, 202670 ms
Jul 18, 202670 ms
Jul 25, 202669 ms
Aug 1, 202670 ms
Aug 8, 202671 ms
Aug 15, 202670 ms
Aug 22, 202666 ms
Aug 29, 202667 ms
Sep 5, 202667 ms
Sep 12, 202667 ms
Sep 19, 202666 ms
Sep 26, 202670 ms
Oct 3, 202668 ms
Oct 10, 202666 ms
Oct 17, 202669 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 banning.nl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. banning.nl at 0.6 s0.6 s
  2. banning.nl at 1.1 s1.1 s
  3. banning.nl at 1.7 s1.7 s
  4. banning.nl at 2.3 s2.3 s
  5. banning.nl at 2.9 s2.9 s
  6. banning.nl at 3.5 s3.5 s
  7. banning.nl at 4.0 s4.0 s
  8. banning.nl at 4.6 s4.6 s

Speed

10 to fix42
  • Improve image delivery

    8.1 s · 1.6 MB

    4 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 8.1 s faster on a phone.

  • Use efficient cache lifetimes

    3.1 s · 569 KiB

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

  • Reduce unused JavaScript

    2.1 s · 1,011 KiB

    About 1,011 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42 (desktop: 56). 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.6 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 CDN, Google Tag Manager and Hubspot and others), adding 2.2 MB and 1.6 s of main-thread time.

  • Google CDN adds 691 ms

    691 ms

    Google CDN costs a phone 691 ms of main-thread work and 1.1 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.

  • Google Tag Manager adds 604 ms

    604 ms

    Google Tag Manager costs a phone 604 ms of main-thread work and 680 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 CSS

    450 ms · 36 KiB

    About 36 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    14 KiB

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

  • 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: 9 ms

    9 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 21.5 s

    21.5 s

    Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We gebruiken cookies om content en advertenties te personal…”.

  • Time to Interactive: 24.6 s

    24.6 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Total Blocking Time: 857 ms

    857 ms

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

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

    +17%

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

7 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 INP: 68 ms

    68 ms

    Real visitors wait 68 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: 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: 506 ms

    506 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix47
  • Page weight: 4.8 MB in 107 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 107 requests on a phone: scripts 2.3 MB (31), images 1.9 MB (28) and other files 388 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Paleis als Clubhuis (1).jpg weighs 925 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    Paleis als Clubhuis (1).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).

  • About 1.4 g of CO₂ per visit

    1.37 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9795
  • 7 text elements with low contrast

    7 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 (3 elements)

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

  • 3 form fields without a label

    3 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 (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Banning” and “Onze expertises”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 80 internal links, 3 external

    The homepage links to 80 pages on banning.nl and 3 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Banning Advocaten: Ondernemers voor ondernemers. Resultaatgericht, betrokken en bevlogen, ervaring met innovatieve juri…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Banning Advocaten: Advocatenkantoor Den Bosch en Amsterdam”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, LegalService and WebSite.

  • 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.banning.nl/sitemap.xml.

AI search readiness

100
4 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 (487 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.banning.nl/llms.txt (3 KiB, 24 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 12 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • 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 opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 488 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 2 calls to action

    The homepage has 2 calls 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: 2 phone links and 1 email link.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 11 cookies set on arrival

    11

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 banning.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
HubSpot CMS
Framework
Tailwind CSS
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 29 issues on banning.nl, including 15 speed issues, 2 SEO issues and 1 conversion gap. 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