hogeklei2a.nl
Hoge Klei 2 A in Wassenaar Vrijstaand
1 failed · 7 warnings · 21 passed
Audited Mon, 20 Jul 2026 21:46:00 GMT · https://www.hogeklei2a.nl/
Meta & Head
22.9/25
Title, description, canonical, social tags — what search engines read first.
Canonical URLmedium impactlow effort
No <link rel="canonical"> found
When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.
Twitter card taglow impactlow effort
No twitter:card meta tag found
X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.
7 passing checks
- Title tag<title> is "Hoge Klei 2 A in Wassenaar Vrijstaand" (37 characters)
- Meta descriptionMeta description is "Hoge Klei 2 A in Wassenaar Vrijstaand Woonoppervlakte 163 m² Perceeloppervlakte 2725 m² Bouwjaar 1995 Aantal kamers 6 " (118 characters)
- Viewport meta tagViewport is "width=device-width"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Page allows indexingrobots: index,follow
Content & Structure
24.2/25
Headings, copy depth, images, structured data, internal linking.
Heading hierarchylow impactlow effort
Heading level jumps from h1 ("Hoge Klei 2 A") to h5 ("2242 XZ Wassenaar")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
7 passing checks
- Single H1 heading1 h1 found: "Hoge Klei 2 A"
- Word count6203 words of visible text
- Image alt text39 of 43 images have alt text
- Structured data (JSON-LD)JSON-LD types found: Product
- HTML lang attribute<html lang="nl-NL">
- JavaScript-dependent contentvisible text ~49881 chars in the initial HTML
- Internal linking60 internal, 24 external links
Technical
19.3/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
XML sitemap availablemedium impactlow effort
sitemap.xml exists but is not valid XML
Your sitemap exists but isn't valid XML, so search engines reject the whole file and you get none of its discovery benefit — worse than having no sitemap, because you probably believe it's working. Regenerate it with your framework's built-in generator or a sitemap library rather than hand-editing; unescaped ampersands in URLs (& instead of &) are the most common breakage. Validate before deploying, and check the Sitemaps report in Google Search Console afterwards — it surfaces parse errors explicitly.
Short redirect chainmedium impactlow effort
https://hogeklei2a.nl/ (301) → https://www.hogeklei2a.nl/
Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.
robots.txt present and permissivemedium impactlow effort
no robots.txt found
Without a robots.txt, crawlers assume everything is allowed — not fatal, but you lose the ability to keep them out of low-value areas (internal search results, carts, admin paths) and the standard place to advertise your sitemap. Create a plain-text robots.txt at the site root with at least a "User-agent: *" line and "Sitemap: https://www.example.com/sitemap.xml". Don't use it to hide sensitive URLs, though — the file is public, and disallowing a page doesn't remove it from the index; use noindex or authentication for that.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
Missing pages return 404low impactlow effort
missing paths return a non-404 status (soft 404)
URLs that don't exist on your site return a success status instead of 404 — search engines call these soft 404s, keep recrawling them, and may index the useless placeholder pages, wasting crawl budget that should go to real content. Configure your server or framework to return an actual 404 status (or 410 for permanently removed content) along with your error page. The classic mistake is serving a friendly "page not found" template with a 200 status — crawlers ignore the visible message; only the status code counts.
7 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Fast time to first byte462 ms
- Reasonable HTML size154.1 KB
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.