Website review, no card needed
monkeymoves.com website review
Visit site (opens in a new tab)Reviewed 20 October 202632 issues · 82 checks
This review found 32 issues worth fixing on monkeymoves.com, 14 of them high impact, across 82 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
86BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.0 s |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 967 ms |
| May 30, 2026 | 939 ms |
| Jun 6, 2026 | 939 ms |
| Jun 13, 2026 | 894 ms |
| Jun 20, 2026 | 893 ms |
| Jun 27, 2026 | 877 ms |
| Jul 4, 2026 | 834 ms |
| Jul 11, 2026 | 888 ms |
| Jul 18, 2026 | 856 ms |
| Jul 25, 2026 | 899 ms |
| Aug 1, 2026 | 969 ms |
| Aug 8, 2026 | 890 ms |
| Aug 15, 2026 | 886 ms |
| Aug 22, 2026 | 831 ms |
| Aug 29, 2026 | 835 ms |
| Sep 5, 2026 | 868 ms |
| Sep 12, 2026 | 920 ms |
| Sep 19, 2026 | 945 ms |
| Sep 26, 2026 | 959 ms |
| Oct 3, 2026 | 967 ms |
| Oct 10, 2026 | 962 ms |
| Oct 17, 2026 | 974 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 109 ms |
| May 9, 2026 | 110 ms |
| May 16, 2026 | 112 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 114 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 115 ms |
| Aug 8, 2026 | 118 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 122 ms |
| Sep 19, 2026 | 122 ms |
| Sep 26, 2026 | 125 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 130 ms |
| Oct 17, 2026 | 137 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
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Use efficient cache lifetimes
5.3 s · 8.3 MB72 files are served with short cache lifetimes, so returning visitors download them again (8.3 MB).
Render-blocking requests
5.2 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Reduce unused CSS
3.5 s · 732 KiBAbout 732 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Improve image delivery
850 ms · 3.2 MB12 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Vimeo, Cloudflare CDN and klantenvertellen.nl and others), adding 17.9 MB and 241 ms of main-thread time.
Vimeo adds 177 ms
177 msVimeo costs a phone 177 ms of main-thread work and 17.6 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.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 74). Pages that score under 90 lose visitors before the first paint.
Minify CSS
600 ms · 111 KiB111 KiB could be saved by minifying CSS.
Reduce unused JavaScript
411 KiBAbout 411 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 712 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 11 KiB11 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 58 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.8 s
14.8 sYour largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Multisport en beweegplezier voor kinderen bij Monkey Moves”.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 109 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 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.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 421 ms
421 msReal visitors wait 421 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.063
0.063The layout barely moves while loading (CLS 0.063, good is under 0.1).
Total Blocking Time: 8 ms
8 msScripts block the page for only 8 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 26.2 MB in 121 requests
26.2 MBYour homepage downloads 26.2 MB in 121 requests on a phone: other files 16.9 MB (30), images 7.5 MB (51) and stylesheets 839 KiB (14). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 3.9 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
1.2 MB6 images are downloaded at several times the size a phone draws them, for example apie-cookie.png at 1,254 px wide, shown at 150 px. Resized copies would save about 1.2 MB.
17 images in older formats
17 images (5.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.
7 images below the first screen load straight away
7 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.4 g of CO₂ per visit
7.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.43 g of CO₂e: 891.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
25 tap targets too small
25 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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.
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.
2 checks passed
Every image has alt text
All 75 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
94 internal links, 13 external
The homepage links to 94 pages on monkeymoves.com and 13 external pages.
8 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Monkey Moves: multisportlessen voor kinderen van 1,5 t/m 9 jaar, sportieve BSO, kinderfeestjes en kampen. Ontdek het aa…”.
One H1 headline
Your main headline reads: “Monkey Moves:groei door beweging”.
Title: 33 characters
Your title is a healthy 33 characters: “Monkey Moves: groei door beweging”.
Canonical URL set
The canonical URL is https://monkeymoves.com/.
Structured data in place
Structured data found: 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.
XML sitemap found
Your XML sitemap is reachable at https://monkeymoves.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://monkeymoves.com/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,776 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages hidden from search
https://monkeymoves.com/locatiezoeker-regio, https://monkeymoves.com/ja-dat-wil-ik, https://monkeymoves.com/locatiezoeker-kinderfeestjes and https://monkeymoves.com/locatiezoeker-kampen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 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.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'offsetHeight') measure (https://monkeymoves.com/v26d/assets/js/organisaties.js…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
18 of 19 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 68 testimonial or review blocks. 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 1,000 words of copy
The homepage carries about 1,000 words of visible text.
4 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Top Tips Download (GRATIS)” and “Cadeau Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies, 2 of them by other companies (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.
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 monkeymoves.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google 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 32 issues on monkeymoves.com, including 16 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.