primeivfcentre.com
Issues affecting most of your site
Issues that appear on 50%+ of audited pages — usually living in your shared template/layout. Fix once, resolve everywhere.
Lead each section with a direct, citable answer to the question users would ask. AI engines (ChatGPT, Perplexity) cite the clearest, most specific sentences.
Affected URLs (1)
Add concrete facts — numbers, dates, percentages, named sources. Vague prose doesn't get cited; specific data does.
Affected URLs (1)
Add bulleted lists, sub-headings, definitions, and TL;DR sections. AI engines prefer clearly structured content for extraction.
Affected URLs (1)
Cite authoritative external sources (links, references). Pages that cite reputable sources are themselves cited more often.
Affected URLs (1)
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">
Affected URLs (1)
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="...">
Affected URLs (1)
Internal links returning 4xx/5xx waste crawl budget and frustrate users. Fix the URL, redirect it, or remove the link entirely.
<a href="/old-page">{{actual}}</a>
<a href="/new-page">Link text</a>
Affected URLs (1)
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="...">
Affected URLs (1)
First Contentful Paint should be under 1.8s. Inline critical CSS, defer non-critical CSS/JS, and use a CDN.
Affected URLs (1)
Your JSON-LD has a syntax error. Validate at https://validator.schema.org/. Invalid JSON is silently ignored by Google — you get zero benefit from it.
<script type="application/ld+json">{ broken json }</script>
<script type="application/ld+json">{"@context":"https://schema.org","@type":"WebPage","name":"Page name"}</script>
Affected URLs (1)
Page breakdown (1)
| Path | Score | Critical / High / Medium | Last audit | Actions |
|---|---|---|---|---|
| / | 73 | 0 / 11 / 12 | 6 months ago | View History |
Template-level fixes appear first (biggest ROI), then per-page fixes.