Skip to content
https://legalporno.net

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
78
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Checks
9
4 PASS 3 REVIEW 2 FIX
F
Image Optimization
Action
4 issues found across 2 images
FIX
4 issues found across 2 images
Warning::
1 images significantly larger than display size
Resizing to display dimensions could save approximately 47 KB.
Got: ~47 KB wasted
Warning::
2 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Warning::
All 2 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::
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://legalporno.net/templates/legalpornonet/images/slide1.jpg.
F
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
FIX

Brand Presence

Partial brand coverage — a few channels are missing brand signals.

F

30/100

Site name appears as

Page titleLegalPorno.net
og:site_nameLegalPorno.net
twitter:site—
Organization.name—

Consistent

Brand assets

Favicon

12/15

covers apple-touch-icon

Social share image

0/20

Meta completeness

8/20

Organization schema

0/15

Contact info discoverable

0/10

no contact info discoverable

Findings

  • Missing brand name in: twitter:site, Organization.name
  • No social share image — shared links render as bare URLs
  • Add an apple-touch-icon and at least two PNG sizes (32x32 + 192x192)
  • og:image missing
  • twitter:card missing
  • No Organization schema — Google can't render your logo in the knowledge panel
  • No discoverable contact info — trust signal is weak, legal risk is higher in regulated regions

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

C
Open Graph
Action
Open Graph tags are partially configured — some improvements recommended.
REVIEW
Open Graph tags are partially configured — some improvements recommended.
Warning::
Missing og:image
The og:image tag provides a preview image for social sharing.
Info::
og:title is short (14 characters)
Ideal length is 25–60 characters for social sharing previews.
Got: 14 chars Expected: 25–60 chars
Info::
og:description is short (14 characters)
Ideal length is 55–200 characters for social sharing previews.
Got: 14 chars Expected: 55–200 chars
Info::
Missing og:url
The og:url tag specifies the canonical URL for the shared content.
Info::
Missing twitter:card
Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

The og:image tag provides a preview image for social sharing.

Why this matters

No og:image means social shares are imageless — measurably less engaging than image-cards across every major platform.

Learn more ▾

Twitter, Facebook, and LinkedIn all use og:image (or twitter:image as a fallback) for share-card thumbnails. Without one, the post renders as a text-only card. A 1200x630px image (Twitter's preferred size) covers all platforms.

Source: Open Graph Protocol

URL: 14 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

URL: 14 chars

Ideal length is 55–200 characters for social sharing previews.

Expected: 55–200 chars
Why this matters

og:description very short — provides little context in social cards.

Source: Open Graph Protocol

The og:url tag specifies the canonical URL for the shared content.

Why this matters

Without og:url, social platforms infer the canonical URL — often picking a tracking-param variant that pollutes share counts.

Learn more ▾

og:url tells the social platform which URL to count this share against. Without it, platforms use the literal URL the user pasted (which may include utm_* parameters, ref codes, etc.). Setting og:url to the canonical form keeps share-count attribution clean.

Source: Open Graph Protocol

Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control.

Why this matters

Without twitter:card, Twitter renders posts as plain text — no preview image, no structured layout.

Learn more ▾

Twitter requires `<meta name="twitter:card" content="summary_large_image">` (or summary) to render share-cards at all. Without it, links appear as raw text and engagement plummets vs cards. Twitter also falls back to og:image if twitter:image isn't set, so configure both.

Source: Twitter Developer Platform

Preview

No image set

legalporno.net

LegalPorno.net

LegalPorno.net

Preview quality · Twitter/X F · 20/100
  • twitter:card — Add <meta name="twitter:card" content="summary_large_image">
  • twitter:title — falling back from og:title
  • twitter:description — falling back from og: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

LEGALPORNO.NET

LegalPorno.net

LegalPorno.net

Preview quality · Facebook D · 50/100
  • og:title — LegalPorno.net
  • og:description — LegalPorno.net
  • og:image — Add og:image — preview card without an image looks broken
  • og:type — article
  • og:url — Add og:url — Recommended — canonical URL for the share
  • og:site_name — LegalPorno.net

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

LegalPorno.net

legalporno.net

Preview quality · LinkedIn C · 65/100
  • og:title — LegalPorno.net
  • og:description — LegalPorno.net
  • og:image — Add og:image — preview card without an image looks broken

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

legalporno.net

LegalPorno.net

LegalPorno.net

Preview quality · Slack B · 80/100
  • og:title — LegalPorno.net
  • og:description — LegalPorno.net
  • 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 · 53/100
FieldTwitter/XFacebookLinkedInSlack
og:title
og:description
og:image
og:type
og:url
og:site_name
twitter:card———
twitter:title⚠———
twitter:description⚠———
twitter:image———
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.
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
A+
Autoplay Media
24 media element(s) found, none autoplay
PASS
24 media element(s) found, none autoplay
Info::
24 media element(s) found, none autoplay
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback