https://www.drpaulsonline.com/

Every page must have a unique, descriptive <title> tag inside <head>. 30-60 characters, primary keyword first.

<head>
  <!-- no <title> tag -->
</head>

<head>
  <title>Your Page Title (30-60 chars)</title>
</head>

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="...">

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

Add an Open Graph image so links to this page render as a rich card on social platforms. Use 1200x630 px, JPEG/PNG, under 1MB.

<head>
  <!-- no og:image -->
</head>

<head>
  <meta property="og:image" content="https://yoursite.com/og-image.jpg">
  <meta property="og:image:width" content="1200">
  <meta property="og:image:height" content="630">
</head>

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">

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="...">

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.

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

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>

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.

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.

You're using deprecated schema types Google no longer surfaces. Remove them to reduce JSON-LD weight and replace with their successors (e.g., HowTo → How-To rich result is gone, use Article instead).

Restricted schema types (e.g., FAQPage) are now reserved for government/health sites. Using them on other sites does nothing useful and may flag as spam.

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>

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>

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="...">

Replace generic anchor text ("click here", "read more") with descriptive phrases containing the target page's keywords. Anchors are a strong relevance signal.

<a href="/laptops">click here</a>

<a href="/laptops">programming laptops review</a>

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'