Website review, no card needed

berghauserpont.nl logo

berghauserpont.nl website review

Visit site (opens in a new tab)Reviewed 19 October 202648 issues · 85 checks

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

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

How it loaded on a phone

  1. berghauserpont.nl at 0.4 s0.4 s
  2. berghauserpont.nl at 0.8 s0.8 s
  3. berghauserpont.nl at 1.1 s1.1 s
  4. berghauserpont.nl at 1.5 s1.5 s
  5. berghauserpont.nl at 1.9 s1.9 s
  6. berghauserpont.nl at 2.3 s2.3 s
  7. berghauserpont.nl at 2.6 s2.6 s
  8. berghauserpont.nl at 3.0 s3.0 s

Speed

12 to fix50
  • Use efficient cache lifetimes

    3.7 s · 17.6 MB

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

  • Render-blocking requests

    4.7 s

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

  • Reduce unused CSS

    1.4 s · 302 KiB

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

  • Improve image delivery

    13.7 MB

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

  • Reduce unused JavaScript

    900 ms · 787 KiB

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

  • 8 third-party services on the page

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

  • Mobile performance score: 50

    50/100

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

  • Google CDN adds 439 ms

    439 ms

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

  • Minify JavaScript

    300 ms · 125 KiB

    125 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 377 ms

    377 ms

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

    350 ms

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

  • Main-thread work: 2.9 s

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

  • 13 long tasks on the main thread

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

  • Minify CSS

    150 ms · 25 KiB

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

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

    3 ms

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

Core Web Vitals

6 to fix61
  • Speed Index: 22.9 s

    22.9 s

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

  • Time to Interactive: 65.0 s

    65.0 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “De Berghauser Pont Mediagroep beoogt met PONT een bijdrage …”.

  • 34 images without width and height

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

  • Total Blocking Time: 409 ms

    409 ms

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 19.3 MB in 119 requests

    19.3 MB

    Your homepage downloads 19.3 MB in 119 requests on a phone: images 16.5 MB (44), scripts 1.9 MB (39) and stylesheets 378 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 13 images far larger than shown

    10.7 MB

    13 images are downloaded at several times the size a phone draws them, for example 030321_Header-Design_BP-Websites-25.png at 7,474 px wide, shown at 390 px. Resized copies would save about 10.7 MB.

  • 5 images over 500 KB

    5 images weigh 10.2 MB together. On a phone connection a single image that size takes seconds.

  • 14 images in older formats

    14 images (11.5 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.

  • 11 images below the first screen load straight away

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

  • About 5.5 g of CO₂ per visit

    5.47 g

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

Accessibility

11 to fixGoogle 6083
  • Images must have alternative text (8 elements)

    Images must have alternative text: 8 elements on the page fail this check, rated critical by axe-core.

  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

  • Hidden but focusable

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 13 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 11 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 9281
  • No H1 headline

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

  • Meta description is long (232 characters)

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

  • No XML sitemap

    No XML sitemap at http://berghauserpont.nl/chondromycesnib.xml, so Google discovers your pages only by following links.

  • 37 internal links, 13 external

    The homepage links to 37 pages on berghauserpont.nl and 13 external pages.

5 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “Berghauser Pont | het kennis- en opleidingsinstituut”.

  • Canonical URL set

    The canonical URL is https://berghauserpont.nl/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 1 linked page hidden from search

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

  • 12 pages without a meta description

    https://berghauserpont.nl/over-ons, https://berghauserpont.nl/inhetnieuws, https://berghauserpont.nl/winkelwagen, https://berghauserpont.nl/nieuws, https://berghauserpont.nl/kennis and https://berghauserpont.nl/cursussen-en-opleidingen and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://berghauserpont.nl/over-ons, https://berghauserpont.nl/inhetnieuws, https://berghauserpont.nl/winkel, https://berghauserpont.nl/winkelwagen, https://berghauserpont.nl/nieuws and https://berghauserpont.nl/kennis and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://berghauserpont.nl/nieuws has 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.

  • 1 page slow to respond

    https://berghauserpont.nl/winkel/digitalisering/digitalisering-privacy/wet-en-regelgeving-privacy-in-het-arbeidsrecht took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 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 a title

    All 14 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6970
  • 3 broken images

    3 images failed to load on a phone, for example https://sociaalweb.nl/wp-content/themes/sociaalweb-v2/assets/img/PONT_logoZ&S.png.

  • 7 small tap targets

    7 of 17 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 “Uncaught (in promise) InvalidValueError: initMap is not a function”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • 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: 6 customer or partner logos. 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 451 words of copy

    The homepage carries about 451 words of visible text.

4 checks passed
  • 1 call to action

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

  • 1 short form

    A short form (1 field at most) is 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.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 berghauserpont.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 48 issues on berghauserpont.nl, including 18 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