Website review, no card needed
hotelalmere.nl website review
Visit site (opens in a new tab)Reviewed 22 October 202641 issues · 92 checks
This review found 41 issues worth fixing on hotelalmere.nl, 16 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 162 ms |
| May 9, 2026 | 163 ms |
| May 16, 2026 | 176 ms |
| May 23, 2026 | 177 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 199 ms |
| Jun 27, 2026 | 203 ms |
| Jul 4, 2026 | 208 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 199 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 199 ms |
| Aug 8, 2026 | 209 ms |
| Aug 15, 2026 | 215 ms |
| Aug 22, 2026 | 222 ms |
| Aug 29, 2026 | 229 ms |
| Sep 5, 2026 | 219 ms |
| Sep 12, 2026 | 219 ms |
| Sep 19, 2026 | 215 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 217 ms |
| Oct 17, 2026 | 211 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.7 s
1.3 s
2.0 s
2.6 s
3.3 s
3.9 s
4.6 s
5.2 s
Speed
Reduce unused JavaScript
7.6 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.6 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 812 KiB33 files are served with short cache lifetimes, so returning visitors download them again (812 KiB).
Render-blocking requests
1.8 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.8 s.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 67). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Google Maps and others), adding 3.2 MB and 1.5 s of main-thread time.
Reduce unused CSS
900 ms · 252 KiBAbout 252 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Google Tag Manager adds 668 ms
668 msGoogle Tag Manager costs a phone 668 ms of main-thread work and 613 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.
YouTube adds 467 ms
467 msYouTube costs a phone 467 ms of main-thread work and 978 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.
Improve image delivery
300 ms · 117 KiB4 images could be 117 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
valkenhorst.nl adds 82 ms
82 msvalkenhorst.nl costs a phone 82 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 Maps adds 143 ms
143 msGoogle Maps costs a phone 143 ms of main-thread work and 387 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 67 but mobile only 25. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 111 ms
111 msYour server sent the HTML in 111 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.54
0.54For real visitors the layout shifts by 0.54 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 24.3 s
24.3 sYour largest element takes 24.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wij gebruiken cookies en vergelijkbare technologieën”.
Time to Interactive: 25.6 s
25.6 sThe page becomes fully interactive after 25.6 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 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.
Total Blocking Time: 791 ms
791 msScripts block taps and scrolling for 791 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.284
0.284The layout shifts by 0.284 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 265 ms
265 msReal visitors wait 265 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 162 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 images without width and height
12 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.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
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: 531 ms
531 msReal visitors wait 531 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.8 MB in 92 requests
3.8 MBYour homepage downloads 3.8 MB in 92 requests on a phone: scripts 2.7 MB (26), images 519 KiB (23) and fonts 207 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 130.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
45 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: 45 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Van der Valk Hotel Almere | Hotel, Restaurant & Events - Hotel Almere”.
Structured data has 1 problem
Structured data found (Hotel) but with 1 problem, for example “Hotel: logo is not an absolute URL ("//cdn.valkexclusief.com/BLW26VG3/at/vqwbr8vz4ggv4sfr2vktgjvf/O…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
76 internal links, 27 external
The homepage links to 76 pages on hotelalmere.nl and 27 external pages.
5 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Verblijf in luxe bij Van der Valk Hotel Almere. Geniet van comfortabele kamers, een sfeervol restaurant en moderne even…”.
One H1 headline
Your main headline reads: “Welkom bij Hotel Almere”.
Canonical URL set
The canonical URL is https://www.hotelalmere.nl/.
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.hotelalmere.nl/sitemap.xml.
AI search readiness
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: 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 (867 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hotelalmere.nl/llms.txt (47 KiB, 134 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.hotelalmere.nl/valkaccount/kies-je-account-type has no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://www.hotelalmere.nl/valkaccount/kies-je-account-type 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 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.
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 1 page that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=97058496&Ver=2&mid=dc3122ff-c66c-4234-b2c7-2497de3512f3&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Van%20der%20Valk%20Hotel%20Almere%20%7C%20Hotel,%20Rest.
25 small tap targets
25 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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 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 830 words of copy
The homepage carries about 830 words of visible text.
9 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
3 calls to action
The homepage has 3 calls to action, for example “Contact”.
6 short forms
6 short forms (4 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 3 email links.
Opening hours shown
Your opening hours are on the homepage.
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
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 1 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.
26 other companies contacted
Loading the homepage contacts 26 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 hotelalmere.nl, 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 Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on hotelalmere.nl, including 24 speed issues and 3 SEO issues. 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.