Skip to content
https://bodonu.no

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
4
PASS
2
INFO
0
Checks
9
2 PASS 4 REVIEW 3 FIX
F
Open Graph
Action
No Open Graph tags found — social sharing previews will be generic.
FIX
No Open Graph tags found — social sharing previews will be generic.
Warning::
No Open Graph meta tags found
Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared.

Why this matters

Without Open Graph tags, social shares show a broken or empty preview card.

Learn more ▾

When someone shares your URL on Facebook, LinkedIn, Slack, iMessage, or any modern chat app, the preview comes from <meta property="og:*"> tags. Without them you get either no card or whatever fragment the social platform guesses — usually unflattering. The four core og: tags (title, description, image, url) cover what every major platform actually reads.

Source: Open Graph Protocol

Preview

No image set

bodonu.no

No title set

No description

Preview quality · Twitter/X F · 20/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from <title>
  • twitter:description — falling back from <meta name=description>
  • twitter:image — Add twitter:image — preview card without an image looks broken

  • twitter:card is missing

    → Add <meta name="twitter:card" content="summary_large_image">

  • No preview image for Twitter/X

    → Add og:image or twitter:image (≥300×157 for summary_large_image)

No image set

BODONU.NO

No title set

No description

Preview quality · Facebook D · 55/100
  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken
  • og:type — frontpage
  • og:url — https://www.bodonu.no/
  • og:site_name — Bodø Nu

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

No title set

bodonu.no

Preview quality · LinkedIn D · 55/100
  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

bodonu.no

No title set

No description

Preview quality · Slack C · 70/100
  • og:title — falling back from <title>
  • og:description — falling back from <meta name=description>
  • og:image — Add og:image — preview card without an image looks broken

  • No preview image — Slack unfurl will be text-only

    → Add og:image or twitter:image

Social preview quality

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

D · 50/100
FieldTwitter/XFacebookLinkedInSlack
og:title⚠⚠⚠
og:description⚠⚠⚠
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image———
F
Image Optimization
Action
6 issues found across 50 images
FIX
6 issues found across 50 images
Warning::
7 images significantly larger than display size
Resizing to display dimensions could save approximately 194 KB.
Got: ~194 KB wasted
Warning::
2 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
7 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Info::
8 of 50 images use legacy formats
Info::
1 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://assets.acdn.no/local/v3/publications/www.bodonu.no/gfx/small.svg.
Info::
6 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://assets.acdn.no/local/v3/publications/www.bodonu.no/gfx/small.svg, https://g.acdn.no/api/lumina/version/ami-large/https%3A%2F%2Fsmooth-storage.aptoma.no%2Fusers%2Fdrf-amedia%2Fimages%2F151652317.jpg%3FaccessToken%3D9e4de4161c8858f9a292cb6b0c31c153e15f14cdf29acdc07e0746474e80c089, https://g.acdn.no/api/lumina/version/ami-large/https%3A%2F%2Fsmooth-storage.aptoma.no%2Fusers%2Fdrf-amedia%2Fimages%2F113450223.jpg%3FaccessToken%3D0adf801c1fef70fc5627268ac7de3421bae749956628628816c1ca7cc9eb6530 (+3 more).
F
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

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

F

26/100

Site name appears as

Page titleArtikkelen er for abonnenter
og:site_nameBodø Nu
twitter:siteBodø Nu
Organization.name—

Inconsistent — names differ across channels

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

0/20

Meta completeness

4/20

Organization schema

0/15

Contact info discoverable

5/10

mailto link + tel link

Findings

  • Brand name differs across channels — users see inconsistent identity
  • No social share image — shared links render as bare URLs
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • og:title missing
  • og:image missing
  • twitter:card missing
  • No Organization schema — Google can't render your logo in the knowledge panel
  • Only partial contact info discoverable — consider adding a dedicated contact page or mailto/tel link

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

C
Structured Data
Action
No structured data (JSON-LD) found.
REVIEW
No structured data (JSON-LD) found.
Info::
No structured data (JSON-LD) found
Adding structured data helps search engines understand your content and can enable rich results.

Adding structured data helps search engines understand your content and can enable rich results.

Why this matters

Without schema.org markup, your pages can't appear as rich results (stars, FAQs, recipes) in search.

Learn more ▾

Structured data is what unlocks rich snippets — review stars, FAQ accordions, recipe cards, breadcrumbs, etc. — that take up more SERP space and dramatically improve click-through. The schema.org vocabulary is well-documented and JSON-LD is the easiest format.

Source: Google Search Central / schema.org

No structured data found

Structured data (JSON-LD) helps search engines understand your content better. Adding it can improve your search result appearance.

Common types include:

  • WebSite — your site identity and search box
  • Organization — your company information
  • Article — blog posts and news articles
  • Product — e-commerce product pages
  • BreadcrumbList — navigation paths
Learn more at schema.org
C
Rich Results Eligibility
Action
No JSON-LD found -- no rich-result eligibility
REVIEW
No JSON-LD found -- no rich-result eligibility
Info::
No JSON-LD structured data on the page
No `<script type="application/ld+json">` blocks found. Without structured data, search engines fall back to inferring page meaning from raw HTML -- which works but doesn't unlock SERP features (rich snippets, knowledge panel, FAQ accordion, breadcrumb trail). Adding even basic JSON-LD (Organization for the site identity, BreadcrumbList for navigation context) is a low-effort SEO win.
B
Autoplay Media
2 autoplay media element(s) -- all muted
REVIEW
2 autoplay media element(s) -- all muted
Info::
2 autoplay media element(s) on page (muted)
Autoplay video transfers bytes whether the user engages or not -- a sustainability concern even when muted. Consider replacing with a static poster image and a click-to-play overlay; the user opts in to the bandwidth cost.
A+
Mixed Content
No mixed content detected — all resources use HTTPS.
PASS
No mixed content detected — all resources use HTTPS.
Info::
No mixed content detected — all resources use HTTPS
A+
Open Graph / Twitter Card Depth
No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)
PASS
No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)
Info::
No OG image / Twitter card to evaluate
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback