Website review, no card needed
harmonie.nl website review
Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 86 checks
This review found 39 issues worth fixing on harmonie.nl, 12 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 931 ms |
| May 2, 2026 | 911 ms |
| May 9, 2026 | 905 ms |
| May 16, 2026 | 897 ms |
| May 23, 2026 | 811 ms |
| May 30, 2026 | 794 ms |
| Jun 6, 2026 | 801 ms |
| Jun 13, 2026 | 798 ms |
| Jun 20, 2026 | 853 ms |
| Jun 27, 2026 | 924 ms |
| Jul 4, 2026 | 957 ms |
| Jul 11, 2026 | 975 ms |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 984 ms |
| Aug 1, 2026 | 963 ms |
| Aug 8, 2026 | 964 ms |
| Aug 15, 2026 | 905 ms |
| Aug 22, 2026 | 887 ms |
| Aug 29, 2026 | 858 ms |
| Sep 5, 2026 | 824 ms |
| Sep 12, 2026 | 843 ms |
| Sep 19, 2026 | 851 ms |
| Sep 26, 2026 | 855 ms |
| Oct 3, 2026 | 865 ms |
| Oct 10, 2026 | 846 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 97 ms |
| May 2, 2026 | 96 ms |
| May 9, 2026 | 96 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 97 ms |
| Jul 4, 2026 | 98 ms |
| Jul 11, 2026 | 97 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 97 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 100 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 106 ms |
| Oct 3, 2026 | 108 ms |
| Oct 10, 2026 | 110 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
Speed
Use efficient cache lifetimes
3.6 s · 2.1 MB32 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).
Render-blocking requests
1.9 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Improve image delivery
550 ms · 596 KiB16 images could be 596 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 77). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 179 KiBAbout 179 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (jQuery CDN, Google Tag Manager and Clarity and others), adding 2.4 MB and 234 ms of main-thread time.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 ms of main-thread work and 1.7 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.
Reduce unused CSS
140 ms · 141 KiBAbout 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
Legacy JavaScript
200 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 70 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 349 ms of it running JavaScript. That is comfortably low.
Server response: 180 ms
180 msYour server sent the HTML in 180 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.1 s
12.1 sYour largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 14.2 s
14.2 sThe page becomes fully interactive after 14.2 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 97 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%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).
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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 110 ms
110 msReal visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 383 ms
383 msReal visitors wait 383 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 14 ms
14 msScripts block the page for only 14 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.0 MB in 70 requests
3.0 MBYour homepage downloads 3.0 MB in 70 requests on a phone: images 1.7 MB (27), fonts 648 KiB (11) and scripts 407 KiB (14). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.1 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.
9 images below the first screen load straight away
9 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 100.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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (22 elements)
All page content should be contained by landmarks: 22 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.
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.
22 links without text
22 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.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (27 characters)
Your title is only 27 characters: “Stadsschouwburg De Harmonie”. Between 30 and 65 characters leaves room to say what you do and for whom.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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://harmonie.nl/sitemap.xml, so Google discovers your pages only by following links.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
86 internal links, 17 external
The homepage links to 86 pages on harmonie.nl and 17 external pages.
3 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “Bekijk welke voorstellingen we op onze agenda hebben staan en bestel! De officiële aanbieder van tickets.”.
Structured data in place
Structured data found: Organization.
robots.txt in place
robots.txt is in place.
AI search readiness
No llms.txt
There is no https://harmonie.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 (822 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
/, https://harmonie.nl/steun-ons/steun-ons and https://harmonie.nl/english all use the title “Stadsschouwburg De Harmonie”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://harmonie.nl/steun-ons/steun-ons and https://harmonie.nl/english have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://harmonie.nl/agenda has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 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.
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
25 small tap targets
25 of 56 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
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 844 words of copy
The homepage carries about 844 words of visible text.
4 checks passed
1 short form
A short form (5 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 6 phone links and 6 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Clarity (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
14 other companies contacted
Loading the homepage contacts 14 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 harmonie.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
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Company
- Founded
- 1994
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on harmonie.nl, including 12 speed issues, 7 SEO issues and 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.