Skip to content
https://beta.locumnet.in

Content

· 9 checks — Internal links, mixed-content guards, Open Graph previews, and structured data rolled into one auditable list.
SCORE
78
GRADE
C
FIX
1
REVIEW
3
PASS
5
INFO
0
Checks
9
5 PASS 3 REVIEW 1 FIX
F
Image Optimization
Action
7 issues found across 18 images
FIX
7 issues found across 18 images
Warning::
17 images significantly larger than display size
Resizing to display dimensions could save approximately 824 KB.
Got: ~824 KB wasted
Warning::
18 images missing explicit width/height
Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
Info::
17 below-fold images missing loading="lazy"
Lazy loading defers below-fold images, reducing initial page weight.
Info::
13 of 18 images use legacy formats
Warning::
Total image weight: 1033 KB (1.0 MB)
Consider compressing images, using modern formats, and serving appropriately sized images.
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://beta.locumnet.in/assets/images/hero-illustration.png.
Info::
4 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://beta.locumnet.in/assets/images/logo.png, https://beta.locumnet.in/assets/images/solutions/for-hospitals.png, https://beta.locumnet.in/assets/images/solutions/for-doctors.png (+1 more).
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.
C
Brand Presence
Action
Site-name consistency, favicon, social image, meta tags, schema, and contact signals
REVIEW

Brand Presence

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

C

65/100

Site name appears as

Page titleHealthcare Staffing for Hospitals and Doctors
og:site_name—
twitter:site—
Organization.name—

Consistent

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

0/15

Contact info discoverable

5/10

contact page

Findings

  • Missing brand name in: og:site_name, twitter:site, Organization.name
  • 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.

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
Open Graph tags are well configured for social sharing.
PASS
Open Graph tags are well configured for social sharing.
Warning::
og:image is not an image
The og:image URL returned MIME type "text/html", which is not an image.
Got: text/html Expected: image/*
Info::
Missing og:site_name
The og:site_name tag displays the website name in social previews.
URL: text/html

The og:image URL returned MIME type "text/html", which is not an image.

Expected: image/*
Why this matters

og:image pointing at HTML or a 404 means social cards render with no image — engagement plummets vs image-cards.

Learn more ▾

Social platforms validate og:image's Content-Type. If the URL returns text/html (404 page) or any non-image type, the platform skips the image and renders a text-only card. Verify your og:image URL returns image/png, image/jpeg, or image/webp with a 200 response.

Source: Open Graph Protocol

The og:site_name tag displays the website name in social previews.

Why this matters

Without og:site_name, social cards omit the brand attribution — users see the post but not who published it.

Learn more ▾

og:site_name appears in the social card chrome (above the title in Facebook/LinkedIn previews). Without it, posts read as anonymous URLs. Set it to your brand name to get free attribution on every share.

Source: Open Graph Protocol

Preview

beta.locumnet.in

LocumNet | Connecting Quality Care

Healthcare staffing workflows for hospitals and doctors across urgent, planned and permanent requirements.

Preview quality · Twitter/X A+ · 100/100
  • twitter:card — summary_large_image
  • twitter:title — LocumNet | Connecting Quality Care
  • twitter:description — Healthcare staffing workflows for hospitals and doctors.
  • twitter:image — https://locumnet.in/assets/images/hero-illustration.png

BETA.LOCUMNET.IN

LocumNet | Connecting Quality Care

Healthcare staffing workflows for hospitals and doctors across urgent, planned and permanent requirements.

Preview quality · Facebook A · 85/100
  • og:title — LocumNet | Connecting Quality Care
  • og:description — Healthcare staffing workflows for hospitals and doctors across urgent, planned and permanent requirements.
  • og:image — https://locumnet.in/assets/images/hero-illustration.png
  • og:type — website
  • og:url — https://locumnet.in/
  • og:site_name — Add og:site_name — Recommended — site-level brand line in the preview

LocumNet | Connecting Quality Care

beta.locumnet.in

Preview quality · LinkedIn A+ · 100/100
  • og:title — LocumNet | Connecting Quality Care
  • og:description — Healthcare staffing workflows for hospitals and doctors across urgent, planned and permanent requirements.
  • og:image — https://locumnet.in/assets/images/hero-illustration.png

beta.locumnet.in

LocumNet | Connecting Quality Care

Healthcare staffing workflows for hospitals and doctors across urgent, planned and permanent requirements.

Preview quality · Slack A+ · 100/100
  • og:title — LocumNet | Connecting Quality Care
  • og:description — Healthcare staffing workflows for hospitals and doctors across urgent, planned and permanent requirements.
  • og:image — https://locumnet.in/assets/images/hero-illustration.png

Social preview quality

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

A+ · 96/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::
1 Twitter Card field(s) differ from Open Graph counterparts
Twitter Cards inherit values from Open Graph tags when the Twitter-specific tag is absent (`twitter:title` falls back to `og:title`, etc.). Explicitly-set Twitter values that DIFFER from OG are usually stale -- the marketing team updates `og:title` for FB/LinkedIn previews and forgets to update `twitter:title` separately, leaving Twitter showing the old text. Mismatches: - description: twitter="Healthcare staffing workflows for hospit...", og="Healthcare staffing workflows for hospit..." Fix: either remove the redundant Twitter-specific tags (rely on inheritance) or sync them when updating OG.
Got: 1 field(s) differ
A+
Autoplay Media
No autoplay media on the page
PASS
No autoplay media on the page
Info::
No autoplay media on the page
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback