Skip to content
https://www.zaanstad.nl

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
1
PASS
6
INFO
0
Checks
9
6 PASS 1 REVIEW 2 FIX
F
Image Optimization
Action
6 issues found across 9 images
FIX
6 issues found across 9 images
Warning::
2 images significantly larger than display size
Resizing to display dimensions could save approximately 293 KB.
Got: ~293 KB wasted
Warning::
7 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
5 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 6 images use legacy formats (JPEG/PNG/GIF)
WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
Info::
4 image(s) wider than 400px without srcset (no responsive serving)
These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / <picture> lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://www.zaanstad.nl/wp-content/uploads/2023/11/Stadhuis-by-night.jpg, https://openpub.zaanstad.nl/wp-content/uploads/2026/11/Trefplein-768x1024.jpg, https://openpub.zaanstad.nl/wp-content/uploads/2026/11/Opening-Toermalijnbrug-768x576.jpg (+1 more).
Info::
3 image(s) rendered at a different aspect ratio than the source
The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://www.zaanstad.nl/wp-content/uploads/2023/11/Stadhuis-by-night.jpg, https://openpub.zaanstad.nl/wp-content/uploads/2026/11/Trefplein-768x1024.jpg, https://www.zaanstad.nl/wp-content/uploads/2025/02/logo_Gemeente_Zaanstad_RGB.png.
B
Mixed Content
1 HTTP resource(s) loaded on HTTPS page
REVIEW
1 HTTP resource(s) loaded on HTTPS page
Critical::
HTTP link loaded on HTTPS page
Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.
Got: http://gmpg.org/xfn/11 Expected: https://gmpg.org/xfn/11
URL: http://gmpg.org/xfn/11

Modern browsers block or warn about HTTP resources on HTTPS pages. Change the URL to use HTTPS.

Expected: https://gmpg.org/xfn/11
Why this matters

Mixed content — HTTP resource on HTTPS page. Browser may block silently or warn user.

Source: Google Chrome Security

A
Open Graph
Open Graph tags are well configured for social sharing.
PASS
Open Graph tags are well configured for social sharing.
Critical::
og:image is not reachable
The og:image URL could not be fetched. Social platforms won't be able to display it.
Got: https://www.zaanstad.nl/wp-content/uploads/2023/11/Logo_Zaanstad_schild.png
Info::
og:title is short (24 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 24 chars Expected: 25–60 chars
URL: https://www.zaanstad.nl/wp-content/uploads/2023/11/Logo_Zaanstad_schild.png

The og:image URL could not be fetched. Social platforms won't be able to display it.

Why this matters

An unreachable og:image URL (404, DNS fail, slow timeout) means social platforms cache the failure and serve no image for hours.

Learn more ▾

Social platforms (Facebook, Twitter) cache OG metadata aggressively — including failed image fetches. A momentarily-broken og:image can leave your shares imageless for hours. Test og:image URLs in Facebook's Sharing Debugger to force re-cache after fixing.

Source: Open Graph Protocol / Facebook Sharing Debugger

URL: 24 chars

Ideal length is 25–60 characters for social sharing previews.

Expected: 25–60 chars
Why this matters

og:title very short — may render with awkward whitespace in social cards.

Source: Open Graph Protocol

Preview

www.zaanstad.nl

Home - Gemeente Zaanstad

Welkom! Blijf op de hoogte van nieuws uit de gemeente Zaanstad. Ook regelt u uw gemeentezaken gemakkelijk online. Volgt u ons al op social media?

Preview quality · Twitter/X A+ · 100/100
  • twitter:card — summary
  • twitter:title — Home - Gemeente Zaanstad
  • twitter:description — Welkom! Blijf op de hoogte van nieuws uit de gemeente Zaanstad. Ook regelt u uw gemeentezaken gemakkelijk online. Vol...
  • twitter:image — https://www.zaanstad.nl/wp-content/uploads/2023/11/Logo_Zaanstad_schild.png

WWW.ZAANSTAD.NL

Home - Gemeente Zaanstad

Welkom! Blijf op de hoogte van nieuws uit de gemeente Zaanstad. Ook regelt u uw gemeentezaken gemakkelijk online. Volgt u ons al op social media?

Preview quality · Facebook A+ · 100/100
  • og:title — Home - Gemeente Zaanstad
  • og:description — Welkom! Blijf op de hoogte van nieuws uit de gemeente Zaanstad. Ook regelt u uw gemeentezaken gemakkelijk online. Vol...
  • og:image — https://www.zaanstad.nl/wp-content/uploads/2023/11/Logo_Zaanstad_schild.png
  • og:type — website
  • og:url — https://www.zaanstad.nl/
  • og:site_name — Gemeente Zaanstad

  • og:image is below recommended size (1024×1024)

    → Upload an image ≥1200×630 for the large preview card

Home - Gemeente Zaanstad

www.zaanstad.nl

Preview quality · LinkedIn A+ · 100/100
  • og:title — Home - Gemeente Zaanstad
  • og:description — Welkom! Blijf op de hoogte van nieuws uit de gemeente Zaanstad. Ook regelt u uw gemeentezaken gemakkelijk online. Vol...
  • og:image — https://www.zaanstad.nl/wp-content/uploads/2023/11/Logo_Zaanstad_schild.png

www.zaanstad.nl

Home - Gemeente Zaanstad

Welkom! Blijf op de hoogte van nieuws uit de gemeente Zaanstad. Ook regelt u uw gemeentezaken gemakkelijk online. Volgt u ons al op social media?

Preview quality · Slack A+ · 100/100
  • og:title — Home - Gemeente Zaanstad
  • og:description — Welkom! Blijf op de hoogte van nieuws uit de gemeente Zaanstad. Ook regelt u uw gemeentezaken gemakkelijk online. Vol...
  • og:image — https://www.zaanstad.nl/wp-content/uploads/2023/11/Logo_Zaanstad_schild.png

Social preview quality

Averaged across Twitter/X, Facebook, LinkedIn, and Slack.

A+ · 100/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title———
twitter:description———
twitter:image———
A
Open Graph / Twitter Card Depth
1 OG/Twitter depth issue(s) detected
PASS
1 OG/Twitter depth issue(s) detected
Info::
og:image aspect ratio 1.00:1 (1024×1024) is outside Facebook's recommended ~1.91:1
Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 1024×1024 give a ratio of 1.00:1, which Facebook will crop center-to-fit; the result often clips important content from the top/bottom or sides. Use a wider/taller image close to 1.91:1, or accept the cropping consequences.
Got: 1.00:1 (1024×1024)
A+
Structured Data
2 JSON-LD block(s) found — structured data is well configured.
PASS
2 JSON-LD block(s) found — structured data is well configured.
Info::
Missing recommended property "potentialAction" for WebSite
Adding "potentialAction" can improve how search engines display your content.
Info::
2 JSON-LD blocks found

Adding "potentialAction" can improve how search engines display your content.

Why this matters

Recommended schema properties unlock richer SERP layouts — without them you get the basic rich result instead of the enhanced one.

Learn more ▾

Recommended properties expand what Google can render. E.g., adding aggregateRating to Product unlocks star ratings; adding image to Article unlocks the image-card variant. Each recommended property is a direct SERP-real-estate gain.

Source: Google Search Central / schema.org

JSON-LD Blocks

Block 1 : WebSite
8 properties Valid
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "@id": "https://www.zaanstad.nl/#website",
  "name": "Gemeente Zaanstad",
  "alternateName": "Gemeente Zaanstad",
  "description": "",
  "url": "https://www.zaanstad.nl",
  "publisher": {
    "@id": "https://www.zaanstad.nl/#organization"
  }
}
Block 2 : Organization
11 properties Valid
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Gemeente Zaanstad",
  "url": "https://www.zaanstad.nl",
  "alternateName": "Gemeente Zaanstad",
  "description": "Officiële website van de gemeente Zaanstad. Hier vindt u informatie, dienstverlening en nieuwsberichten van de Gemeente Zaanstad.",
  "logo": "https://www.zaanstad.nl/wp-content/uploads/2023/11/cropped-Logo_Zaanstad_schild.png",
  "sameAs": [
    "https://www.facebook.com/gemzaanstad",
    "https://x.com/GemZaanstad",
    "https://www.instagram.com/gemzaanstad/",
    "https://www.youtube.com/GemZaanstad",
    "https://www.linkedin.com/company/gemeente-zaanstad/"
  ],
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "telephone": "14075",
      "contactType": "customer support"
    }
  ],
  "telephone": "14075",
  "@id": "https://www.zaanstad.nl/#organization"
}
A+
Rich Results Eligibility
2 JSON-LD block(s) declaring 2 schema type(s)
PASS
2 JSON-LD block(s) declaring 2 schema type(s)
Info::
2 rich-result schema type(s) declared
Inventory of structured-data types on the page (each may unlock a different SERP feature): Organization, WebSite Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.
A+
Autoplay Media
No autoplay media on the page
PASS
No autoplay media on the page
Info::
No autoplay media on the page
A
Brand Presence
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
PASS

Brand Presence

Your brand name differs across channels — visitors see inconsistent identity.

A

85/100

Site name appears as

Page titleGemeente Zaanstad
og:site_nameGemeente Zaanstad
twitter:site@GemZaanstad
Organization.nameGemeente Zaanstad

Inconsistent — names differ across channels

Brand assets

Favicon

15/15

covers multiple sizes + apple-touch-icon

Social share image

20/20

og:image + twitter:image set

Meta completeness

20/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

10/10

contact page + tel link

Findings

  • Brand name differs across channels — users see inconsistent identity

How consistently your brand appears across channels — shared link previews, structured data, favicon, contact info.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback