Skip to content
https://pornhub.com

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
77
GRADE
C
FIX
3
REVIEW
0
PASS
6
INFO
0
Checks
9
6 PASS 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

pornhub.com

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

PORNHUB.COM

No title set

No description

Preview quality · Facebook F · 0/100

Title will be truncated (63 chars / 60 max)

Description will be truncated (157 chars / 155 max)

  • 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 — Add og:type — Recommended — tells Facebook the content category
  • og:url — Add og:url — Recommended — canonical URL for the share
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

  • Title will be truncated on Facebook (63 chars, max 60)

    → Shorten og:title to ≤60 characters

  • Description will be truncated on Facebook (157 chars, max 155)

    → Tighten og:description to ≤155 characters

  • No preview image for Facebook

    → Add og:image (recommended 1200×630)

No image set

No title set

pornhub.com

Preview quality · LinkedIn D · 50/100

Description will be truncated (157 chars / 150 max)

  • 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

  • Description will be truncated on LinkedIn (157 chars, max 150)

    → Tighten og:description to ≤150 characters

  • No preview image for LinkedIn

    → Add og:image (recommended 1200×627)

pornhub.com

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.

F · 35/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
5 issues found across 145 images
FIX
5 issues found across 145 images
Warning::
40 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
35 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Warning::
All 65 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.
Warning::
5 images missing alt text
Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
Warning::
2 above-fold image(s) marked loading="lazy" (LCP anti-pattern)
Above-fold images marked lazy delay LCP -- the browser waits for the IntersectionObserver to fire before fetching, even though the image is in the initial viewport. Remove `loading="lazy"` on above-the-fold images (especially the LCP candidate). Sample: https://ei.phncdn.com/videos/202302/15/425526421/original/(m=q3IO8_XbeafTGgaaaa)(mh=WdkPF4fxa-g3CJSw)0.jpg, https://pix-cdn77.phncdn.com/c6251/videos/202512/16/32944035/original/019b3797-29b0-7658-b7db-6718e7e56f61.jpg/plain/rs:fit:320:180?hash=dvNUmZJvty-KvpgS50XZVDLZiPQ=&validto=1783799144.
D
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.

D

42/100

Site name appears as

Page titlePornhub
og:site_name—
twitter:site—
Organization.namePornhub

Consistent

Brand assets

Favicon

8/15

single size only

Social share image

0/20

Meta completeness

4/20

Organization schema

15/15

has name, logo + url

Contact info discoverable

5/10

mailto link

Findings

  • Missing brand name in: og:site_name, twitter:site
  • No social share image — shared links render as bare URLs
  • Single favicon only — add apple-touch-icon for iOS home-screen and high-DPI support
  • og:title missing
  • og:image missing
  • twitter:card missing
  • Consider adding contactPoint — helps appear in "contact us" rich results
  • 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.

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
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.
Warning::
Missing required property "name" for WebSite
The "name" property is required for the WebSite schema type.
Info::
Missing recommended property "description" for WebSite
Adding "description" can improve how search engines display your content.
Info::
2 JSON-LD blocks found

The "name" property is required for the WebSite schema type.

Why this matters

Schema markup missing required properties is silently rejected by Google — your structured data appears in source but never as a rich result.

Learn more ▾

Each schema.org type has required properties (Article needs headline + author + datePublished; Product needs name + offers; etc.). Missing them means Google's rich-result eligibility check fails. The Search Console Rich Results Test surfaces specific gaps. Fix the missing property; rich results re-appear within hours.

Source: Google Search Central / schema.org

Adding "description" 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
4 properties Valid
Missing required property: name
{
  "@context": "http://schema.org",
  "@type": "WebSite",
  "url": "https://www.pornhub.com/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://www.pornhub.com/video/search?search={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
Block 2 : Organization
6 properties Valid
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "name": "Pornhub",
  "url": "https://www.pornhub.com/",
  "logo": "https://ki.phncdn.com/www-static/images/pornhub_logo_straight.png",
  "sameAs": [
    "https://twitter.com/pornhub",
    "https://www.instagram.com/pornhub",
    "https://www.youtube.com/channel/UCYsYJ6od6t1lWnQg-A0n6Yw"
  ]
}
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::
SiteLinks Search Box markup detected
The page declares a `WebSite` schema with a `potentialAction` of `SearchAction`. This makes the homepage eligible for Google's in-SERP search box -- a high-visibility SERP feature for branded queries.
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
4 media element(s) found, none autoplay
PASS
4 media element(s) found, none autoplay
Info::
4 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