Website review, no card needed
vesteda.com website review
Visit site (opens in a new tab)Reviewed 19 November 202635 issues · 81 checks
This review found 35 issues worth fixing on vesteda.com, 10 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 973 ms |
| Jun 6, 2026 | 960 ms |
| Jun 13, 2026 | 958 ms |
| Jun 20, 2026 | 955 ms |
| Jun 27, 2026 | 957 ms |
| Jul 4, 2026 | 972 ms |
| Jul 11, 2026 | 983 ms |
| Jul 18, 2026 | 976 ms |
| Jul 25, 2026 | 980 ms |
| Aug 1, 2026 | 976 ms |
| Aug 8, 2026 | 962 ms |
| Aug 15, 2026 | 973 ms |
| Aug 22, 2026 | 959 ms |
| Aug 29, 2026 | 940 ms |
| Sep 5, 2026 | 928 ms |
| Sep 12, 2026 | 909 ms |
| Sep 19, 2026 | 903 ms |
| Sep 26, 2026 | 907 ms |
| Oct 3, 2026 | 904 ms |
| Oct 10, 2026 | 896 ms |
| Oct 17, 2026 | 884 ms |
| Oct 24, 2026 | 875 ms |
| Oct 31, 2026 | 873 ms |
| Nov 7, 2026 | 872 ms |
| Nov 14, 2026 | 858 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 123 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 124 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 124 ms |
| Jul 18, 2026 | 125 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 123 ms |
| Sep 19, 2026 | 124 ms |
| Sep 26, 2026 | 125 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 126 ms |
| Oct 24, 2026 | 126 ms |
| Oct 31, 2026 | 125 ms |
| Nov 7, 2026 | 124 ms |
| Nov 14, 2026 | 122 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.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Improve image delivery
5.3 s · 3.4 MB26 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.
Reduce unused JavaScript
4.8 s · 991 KiBAbout 991 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Use efficient cache lifetimes
2.3 s · 411 KiB14 files are served with short cache lifetimes, so returning visitors download them again (411 KiB).
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Cookiebot and others), adding 6.0 MB and 824 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 202 KiBAbout 202 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
800 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
YouTube adds 455 ms
455 msYouTube costs a phone 455 ms of main-thread work and 1,020 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.
azurefd.net adds 0 ms
0 msazurefd.net costs a phone 0 ms of main-thread work and 4.2 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,507 HTML elements
The page has 1,507 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
viktorvanvesteda.com adds 58 ms
58 msviktorvanvesteda.com costs a phone 58 ms of main-thread work and 374 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 149 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).
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: 102 ms
102 msYour server sent the HTML in 102 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 18.7 s
18.7 sYour largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 19.2 s
19.2 sThe page becomes fully interactive after 19.2 s. Good is under 3.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 386 ms
386 msScripts block taps and scrolling for 386 ms in total while the page loads. Good is under 200 ms.
30 images without width and height
30 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.164
0.164The layout shifts by 0.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 123 ms to 122 ms 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: 131 ms
131 msReal visitors wait 131 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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 349 ms
349 msReal visitors wait 349 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 6.4 MB in 68 requests
6.4 MBYour homepage downloads 6.4 MB in 68 requests on a phone: images 4.2 MB (31), scripts 1.7 MB (15) and stylesheets 165 KiB (5). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 999 KiB together. On a phone connection a single image that size takes seconds.
16 images in older formats
16 images (3.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.
An image on the first screen is lazy-loaded
vesteda-home_young-urban-op_ladder-istock-939497206-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.8 g of CO₂ per visit
1.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.82 g of CO₂e: 218.1 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
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 38 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (BreadcrumbList and WebSite) but with 2 problems, for example “WebSite: url is not an absolute URL ("https://www.vesteda.com/nl")”.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
133 internal links, 25 external
The homepage links to 133 pages on vesteda.com and 25 external pages.
7 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Bekijk het woningaanbod van Vesteda in heel Nederland. Een appartement of eengezinswoning huren? Schrijf u gratis in vo…”.
One H1 headline
Your main headline reads: “Welkom bij Vesteda”.
Title: 40 characters
Your title is a healthy 40 characters: “Huurwoningen in heel Nederland | Vesteda”.
Canonical URL set
The canonical URL is https://www.vesteda.com/nl.
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://www.vesteda.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (888 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.vesteda.com/llms.txt (13 KiB, 104 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.vesteda.com/nl and https://www.vesteda.com/nl/consument all use the title “Huurwoningen in heel Nederland | Vesteda”. Search engines can't tell which page to show for a search, so each competes with the others.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.vesteda.com/nl/consument/aanbod-bekijken, whose canonical is https://www.vesteda.com/nl/woning-zoeken. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.vesteda.com/nl/consument/aanbod-bekijken 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 75 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
13 small tap targets
13 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
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 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 706 words of copy
The homepage carries about 706 words of visible text.
3 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Service en contact”, “Contact” and “Contact Acquisitions & Development”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 of them by other companies (measured from a US location before any click).
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.
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 vesteda.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 Tag Manager
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on vesteda.com, including 18 speed issues, 2 SEO issues and 3 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.