What your Deep Dive report looks like
Below is a complete example report. Use the tabs to jump between sections — your real report follows the same shape, built from live scans of your own website.
Illustrative sample — fictional business and synthetic scan data
Maple & Main Bakery is a fictional business and every score, finding and excerpt on this page is synthetic, created to show what your report looks like. Your real Deep Dive is generated from live scans of your actual website — nothing is invented.
Instant Website Deep Dive · sample report
Maple & Main Bakery: solid bones, slow first impression
Prepared for Maple & Main Bakery · https://maple-and-main-bakery.example · fictional business, synthetic data
This fictional bakery's site looks charming but loads slowly on phones, hides its most important action, and is only partly readable to AI assistants. The fixes are mostly small and high-impact — exactly the kind of quick wins a Deep Dive is built to surface.
Performance
Mobile speed needs work
Search visibility
Basics mostly covered
Accessibility
Some visitors excluded
Best practices
Solid foundation
AI readiness (Cloudflare's scanner in real reports)
AI assistants can reach the homepage, but key pages are harder for them to read. In a real report this section comes from Cloudflare's Agent Readiness Scanner and shows Cloudflare's own 0–5 level.
2/5
Emerging (synthetic)
| Metric (synthetic) | Value | Reading |
|---|---|---|
| First Contentful Paint | 1.8 s | Needs work |
| Largest Contentful Paint | 4.6 s | Poor |
| Total Blocking Time | 430 ms | Needs work |
| Cumulative Layout Shift | 0.18 | Needs work |
| Speed Index | 5.4 s | Poor |
| Time to Interactive | 6.3 s | Needs work |
Synthetic example — a real report cites the actual scan output for your site here.
Priority findings
The highest-impact items from across the report, in the order we'd tackle them.
- 1
Compress and resize the hero image
The largest image on the homepage loads at full camera resolution on phones. In a real report this is usually the single biggest speed win.
High impactLow effort - 2
Add a clear call-to-action above the fold on mobile
Mobile visitors see a photo and a headline but no button to order or call. Real reports flag this when scan data shows weak lead paths.
High impactLow effort - 3
Write unique meta descriptions for the menu and contact pages
Two key pages share the same generic description, so Google often rewrites the snippet. A quick fix that helps clicks from search.
Worth fixingLow effort - 4
Let AI assistants read the menu page
Synthetic example: the menu loads as an image-only section, so AI crawlers see no text. Real reports show exactly what Cloudflare's scanner could and could not read.
Worth fixingMedium effort - 5
Fix form labels and contrast on the contact form
Placeholder-only labels and light gray text make the form hard to use for visitors with low vision — and harder for everyone on a sunny day.
Worth fixingLow effort
Performance
How quickly the site loads and responds on a phone. In a real report these numbers come straight from Google's PageSpeed Insights mobile run — here they are synthetic examples.
- High impactLow effort
Hero image is far larger than phones need
The main photo is served at full resolution to every visitor. Resizing and compressing it for mobile is typically the fastest meaningful speed win on image-heavy sites.
Example evidence: “Largest Contentful Paint 4.6 s — hero image 2.9 MB (synthetic)”
- Worth fixingMedium effort
Scripts block the first paint
Several third-party scripts load before the page can render. Deferring non-essential scripts lets visitors see content sooner.
Example evidence: “Reduce unused JavaScript — potential saving 380 KB (synthetic)”
- Worth fixingLow effort
No long-term caching for static assets
Returning visitors re-download every image and stylesheet. Cache headers would make repeat visits feel much faster.
Example evidence: “Serve static assets with an efficient cache policy — 11 resources (synthetic)”
Synthetic example — a real report cites the actual scan output for your site here.
Search & AI Visibility
Whether search engines and AI assistants can find, read and describe the business. Real reports combine Google's SEO audit with Cloudflare's agent readiness scan.
- Worth fixingLow effort
Menu and contact pages share one generic description
Duplicate meta descriptions make search snippets interchangeable, so Google often rewrites them. Unique descriptions help the right page earn the click.
Example evidence: “2 of 6 pages share the same meta description (synthetic)”
- Worth fixingMedium effort
No structured data for a local business
Without LocalBusiness schema, search engines and AI assistants must guess the bakery's name, address and hours instead of reading them as facts.
Example evidence: “No LocalBusiness structured data detected (synthetic)”
- Worth fixingMedium effort
Menu is an image, so AI assistants can't read it
AI tools increasingly answer “what's on the menu?” questions. Text-based content gives them something to quote; an image gives them nothing.
Example evidence: “Cloudflare readiness level 2 of 5 — key content not machine-readable (synthetic)”
- Good to knowLow effort
Title tags are clear and unique
Every page has a distinct, descriptive title — an example of a finding that tells you what to leave alone.
Example evidence: “Document has a <title> element — passed (synthetic)”
Synthetic example — a real report cites the actual scan output for your site here.
Accessibility & Usability
Whether every visitor can read and use the site, including people with low vision or motor impairments. Real reports use Google's accessibility audit.
- Worth fixingLow effort
Light gray text falls below contrast guidelines
Body text at low contrast is hard to read for visitors with low vision and for anyone on a phone outdoors.
Example evidence: “Background and foreground colors do not have a sufficient contrast ratio — 9 elements (synthetic)”
- Worth fixingLow effort
Contact form fields have no labels
Placeholders disappear as visitors type and screen readers announce nothing. Proper labels fix both.
Example evidence: “Form elements do not have associated labels — 4 fields (synthetic)”
- Worth fixingLow effort
Gallery images have no alternative text
Screen readers can't describe the photos, and search engines can't index what they show.
Example evidence: “Image elements do not have [alt] attributes — 7 images (synthetic)”
Synthetic example — a real report cites the actual scan output for your site here.
Lead Path
What the evidence suggests about how easily a visitor becomes a customer. Real reports only describe what the scans can show and say so.
- High impactLow effort
No visible action above the fold on mobile
The first mobile screen is a photo and a headline with no button. Visitors who came ready to order have to hunt for how.
Example evidence: “No link or button visible in the initial mobile viewport (synthetic)”
- Worth fixingLow effort
Phone number is plain text, not tap-to-call
On a phone, a callable link turns “I should call them” into one tap. Plain text adds friction at the exact moment of intent.
Example evidence: “Phone number not wrapped in a tel: link (synthetic)”
- Worth fixingLow effort
Ordering link is buried in the footer
The most valuable action on the site is the hardest to find. Moving it into the header and hero is a common high-impact change.
Example evidence: “Primary conversion link appears only in the footer (synthetic)”
Synthetic example — a real report cites the actual scan output for your site here.
Action plan
Every finding distilled into a sequenced to-do list with effort estimates.
- 1Low effort
Compress and resize the hero image
Export at phone-appropriate dimensions; expect the biggest single speed gain.
- 2Low effort
Add an “Order ahead” button to the mobile hero and header
One clear action, visible without scrolling.
- 3Low effort
Write unique meta descriptions for the menu and contact pages
A sentence each, written for the searcher.
- 4Low effort
Fix contact form labels and text contrast
Accessibility wins that help every visitor.
- 5Medium effort
Rebuild the menu as text with LocalBusiness schema
Makes the menu readable to search engines and AI assistants.
- 6Medium effort
Defer non-essential third-party scripts and add cache headers
Technical cleanup for a faster first visit and repeat visits.
Scope & limitations
In a real report this section lists exactly what the scans could not measure for your site, so you always know what is evidence and what is out of scope.
- Real visitor traffic, rankings and revenue — scans measure the site, not its results.
- Real-user (field) speed data, which depends on your actual visitors' devices and connections.
- Content quality, pricing and whether your offer is compelling — that judgment needs a human.
- Anything behind a login or checkout — scanners only see public pages.
- Competitor comparisons — a Deep Dive measures your site on its own.
Synthetic example — a real report cites the actual scan output for your site here.
Get the real report for your website
Your Instant Website Deep Dive scans your actual site and delivers a private report like this one within minutes of payment — automated and on-demand, with no call to schedule. After you read it, we're here if you want help acting on it.
This report — automated, instant, $49. No call, no manual review.
Website & AI Growth Audit — $295: a scheduled, private 30-minute live review with Michelle.
Website Growth Roadmap: a hands-on, Michelle-prepared strategy deliverable with a written 90-day plan.
Your report link is private and unguessable — only this sample is public.