https://abhirachnadental.com/dentist-in-south-extension-part-1-delhi/

Cumulative Layout Shift should be under 0.1. Set explicit width/height on images, reserve space for embeds and ads, and avoid late-loading fonts that re-flow text.

<img src="photo.jpg">

<img src="photo.jpg" width="800" height="600" alt="...">

Potential hacked-site/injected-code signals found. Scan source for obfuscated scripts and hidden iframes, check for unexpected admin users and recently modified files, restore from a clean backup, update CMS/plugins, then request a review in Search Console.

<script>eval(atob("...base64..."))</script>

<!-- remove injected script; patch the vulnerability that allowed it -->

Server is slow. Investigate: enable a CDN, add page caching, optimise database queries, upgrade hosting. TTFB > 800ms hurts every Core Web Vital.

Every <img> needs an alt attribute. Alt text helps screen readers, image search ranking, and shows when the image fails to load. Use alt="" only for purely decorative images.

<img src="photo.jpg">

<img src="photo.jpg" alt="Descriptive text describing the image content">

Largest Contentful Paint should load within 2.5s. Optimise the largest above-the-fold element: compress hero images, preload critical assets, and eliminate render-blocking resources.

<img src="hero.jpg">

<link rel="preload" as="image" href="hero.webp">
<img src="hero.webp" fetchpriority="high" width="1200" height="600" alt="...">

Open Lighthouse in Chrome DevTools or PageSpeed Insights — the report lists specific opportunities ranked by impact.

First Contentful Paint should be under 1.8s. Inline critical CSS, defer non-critical CSS/JS, and use a CDN.

Set explicit width/height on every <img> to prevent Cumulative Layout Shift. Browser reserves the box before the image loads.

<img src="photo.jpg" alt="...">

<img src="photo.jpg" width="800" height="600" alt="...">

Show expertise: author bio with credentials, citations to reputable sources, in-depth coverage of the topic, technical accuracy.

Add trust signals: clear contact info, privacy policy, terms of service, customer reviews, security badges, real photos of team/location.

Meta description is outside the 120-160 character range. Too short = thin content; too long = truncated by Google.

<meta name="description" content="117 chars">

<meta name="description" content="Rewritten description, 120-160 chars, with the primary keyword and a value proposition.">

Enable gzip or Brotli compression on your server. Typically cuts text payload by 70-80% — easy LCP win.

Convert images to WebP or AVIF — typically 25-50% smaller than JPEG/PNG with no visible quality loss. Use <picture> for fallback.

<img src="photo.jpg">

<picture>
  <source type="image/avif" srcset="photo.avif">
  <source type="image/webp" srcset="photo.webp">
  <img src="photo.jpg" alt="...">
</picture>

Demonstrate first-hand experience: original photos, personal anecdotes, before/after results, screenshots from the actual product/service.

Build authoritativeness: links from respected sites in your niche, mentions in industry publications, About page detailing your expertise.

Add Strict-Transport-Security header so browsers refuse HTTP for your domain after the first visit. Bumps SSL Labs grade to A+.

Strict-Transport-Security: max-age=31536000; includeSubDomains

Add rel="noopener noreferrer" to target="_blank" links. Without noopener, the linked page can manipulate your window object — security + perf risk.

<a href="https://other.com" target="_blank">External</a>

<a href="https://other.com" target="_blank" rel="noopener noreferrer">External</a>

Publish an SPF record so receivers can verify which servers may send mail for your domain — reduces spoofing and improves deliverability. List only your real senders and end with ~all (soft-fail) or -all (hard-fail).

# no SPF TXT record

example.com.  IN  TXT  "v=spf1 include:_spf.google.com ~all"

Publish a DMARC record to tell receivers what to do with mail that fails SPF/DKIM, and where to send reports. Start at p=none to monitor, then tighten to quarantine/reject.

# no _dmarc TXT record

_dmarc.example.com.  IN  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

Lead each section with a direct, citable answer to the question users would ask. AI engines (ChatGPT, Perplexity) cite the clearest, most specific sentences.

Add concrete facts — numbers, dates, percentages, named sources. Vague prose doesn't get cited; specific data does.

Add bulleted lists, sub-headings, definitions, and TL;DR sections. AI engines prefer clearly structured content for extraction.

Cite authoritative external sources (links, references). Pages that cite reputable sources are themselves cited more often.

Headings should descend logically: H1 → H2 → H3, no jumps. Skipping levels (H1 → H3) breaks accessibility tools and confuses crawlers.

<h1>Page Title</h1>
<h3>Section</h3>  <!-- skipped H2 -->

<h1>Page Title</h1>
<h2>Section</h2>
<h3>Subsection</h3>

Add the recommended HTTP security headers at the server/CDN level to harden the site.

# missing headers

# nginx
add_header X-Frame-Options "SAMEORIGIN";
add_header X-Content-Type-Options "nosniff";
add_header Referrer-Policy "strict-origin-when-cross-origin";
add_header Permissions-Policy "geolocation=(), microphone=()";
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";

Add loading="lazy" to images below the fold. Saves bandwidth, speeds up initial page load.

<img src="below-fold.jpg">

<img src="below-fold.jpg" loading="lazy" width="..." height="..." alt="...">

Simplify your prose. Shorter sentences (15-20 words), smaller words (1-2 syllables), more paragraph breaks. Target 8th-grade reading level for a general audience.

Add X-Content-Type-Options: nosniff so browsers honour the Content-Type and don't MIME-sniff for malicious files.

X-Content-Type-Options: nosniff

Add a Content-Security-Policy header to block XSS by whitelisting allowed script/style sources.

Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline'