Your website has 3 high-impact issues. Three things deserve your attention first.
Start with the high-impact findings below.
Fix this first
3
Important improvement
5
Worth improving
0
Optional polish
0
Fix notes ready
8of 8
Findings by urgency
3Fix this first
5Important improvement
0Worth improving
0Optional polish
Filter findings:
01
Finding
Fix this first·Search Engine·Measured
Your main page takes too long to appear
What is happening
Observed: 2.8 s · Lighthouse lab
Why it matters
Visitors on slow mobile connections can leave before your key content appears.
How important
Fix this first
What should happen next
Compress hero imagery to WebP/AVIF format, add high-priority fetch tags, and defer unused scripts.
Can HubSEO prepare the fix
Yes. HubSEO can prepare this fix as a brief for Cursor, Claude Code, Copilot, Codex, or Aider.
Report a false positive
02
Finding
Fix this first·Search Engine·Measured
Reduce unused JavaScript
What is happening
Observed: Est savings of 178 KiB · Lighthouse lab
Why it matters
Lab results like this reflect how quickly and reliably visitors and crawlers can use the page.
How important
Fix this first
What should happen next
Use Lighthouse details, source maps, and the route bundle to identify the unused module or third-party resource.
Can HubSEO prepare the fix
Yes. HubSEO can prepare this fix as a brief for Cursor, Claude Code, Copilot, Codex, or Aider.
Report a false positive
03
Finding
Fix this first·Search Engine·Measured
Total Blocking Time
What is happening
Observed: 340 ms · Lighthouse lab
Why it matters
Lab results like this reflect how quickly and reliably visitors and crawlers can use the page.
How important
Fix this first
What should happen next
Reduce or defer third-party scripts (chat, ads, trackers) until after the page is interactive.
Can HubSEO prepare the fix
Yes. HubSEO can prepare this fix as a brief for Cursor, Claude Code, Copilot, Codex, or Aider.
Report a false positive
04
Finding
Important improvement·Search Engine·Measured
Issues were logged in the `Issues` panel in Chrome Devtools
What is happening
Observed: Lighthouse lab measurement
Why it matters
Lab results like this reflect how quickly and reliably visitors and crawlers can use the page.
How important
Important improvement
What should happen next
Inspect the audit detail, owning resource or element, route, and repository callers.
Can HubSEO prepare the fix
Yes. HubSEO can prepare this fix as a brief for Cursor, Claude Code, Copilot, Codex, or Aider.
Report a false positive
05
Finding
Important improvement·Search Engine·Measured
Minimize main-thread work
What is happening
Observed: 2.1 s · Lighthouse lab
Why it matters
Lab results like this reflect how quickly and reliably visitors and crawlers can use the page.
How important
Important improvement
What should happen next
Inspect the audit detail, owning resource or element, route, and repository callers.
Can HubSEO prepare the fix
Yes. HubSEO can prepare this fix as a brief for Cursor, Claude Code, Copilot, Codex, or Aider.
Report a false positive
Desktop visitor experience
100Page Speed & PerformanceGood
100Ease of Use (Accessibility)Good
92Web Standards & Best PracticesGood
100Search Engine Readiness (SEO)Good
Core Web Vitals
Initial Page Display (FCP)How quickly visitors see the first text, logo, or image appear on screen.
1.4 sGood
Good under 1.8 s Poor over 3.0 s Lab test
Main Content Load (LCP)How quickly your primary headline, hero image, or banner finishes loading.
2.8 sNeeds attention
Good under 2.5 s Poor over 4.0 s Lab test
Click & Tap Speed (INP)How smoothly pages react when visitors tap buttons or links. Measured from real users.
Not measuredNot measured
Good under 200 ms Poor over 500 ms
Visual Layout Stability (CLS)Ensures text and buttons stay steady and do not jump around unexpectedly while loading.
0.001Good
Good under 0.1 Poor over 0.25 Lab test
Responsiveness Delay (TBT)How long visitor clicks are delayed by busy scripts before the page can smoothly respond.
340 msNeeds attention
Good under 200 ms Poor over 600 ms Lab test
Web Server Speed (TTFB)How fast your hosting server starts sending the page to the visitor's browser.
Root document took 0 msGood
Good under 800 ms Poor over 1.8 s Lab test
Desktop lab
Initial Page Display (FCP)How quickly visitors see the first text, logo, or image appear on screen.
0.4 sGood
Good under 1.8 s Poor over 3.0 s Lab test
Main Content Load (LCP)How quickly your primary headline, hero image, or banner finishes loading.
0.7 sGood
Good under 2.5 s Poor over 4.0 s Lab test
Click & Tap Speed (INP)How smoothly pages react when visitors tap buttons or links. Measured from real users.
Not measuredNot measured
Good under 200 ms Poor over 500 ms
Visual Layout Stability (CLS)Ensures text and buttons stay steady and do not jump around unexpectedly while loading.
0Good
Good under 0.1 Poor over 0.25 Lab test
Responsiveness Delay (TBT)How long visitor clicks are delayed by busy scripts before the page can smoothly respond.
0 msGood
Good under 200 ms Poor over 600 ms Lab test
Web Server Speed (TTFB)How fast your hosting server starts sending the page to the visitor's browser.
Root document took 0 msGood
Good under 800 ms Poor over 1.8 s Lab test
Additional measurements
Desktop page loading speed100/100
AI search engine readiness checklist · Grade Strong100/100
11 of 11 measured AI-search checks passed. Experimental checklist only; not a ranking or citation prediction. Evaluates whether search engines and AI assistants (like ChatGPT, Claude, and Perplexity) can clearly read and cite your content.
AI-readiness signals
llms.txt observedIn place
GPTBot allows the audited public pathIn place
OAI-SearchBot allows the audited public pathIn place
ClaudeBot allows the audited public pathIn place
PerplexityBot allows the audited public pathIn place
Google-Extended allows the audited public pathIn place
Applebot-Extended allows the audited public pathIn place
JSON-LD types observed: Organization, HowTo, FAQPage, WebSite, Person, BreadcrumbListIn place
HTML5 semantic landmarks presentIn place
Entity disambiguation links observed (sameAs)In place
Captured HTML contains extractable textIn place
OAI-SearchBot user-agent simulationCould not check
GPTBot user-agent simulationCould not check
Claude-SearchBot user-agent simulationCould not check
ClaudeBot user-agent simulationCould not check
PerplexityBot user-agent simulationCould not check
Bingbot user-agent simulationCould not check
CCBot user-agent simulationCould not check
AI Search Visibility (AEO / GEO)100/100 AI readiness
How ready is Hubseo for AI search?
Measured AI readiness is 100/100. It scores whether crawlers and AI assistants can read this page. HubSEO does not run live AI citation tracking, so this report shows no citation score.
03 · Working well
Foundations performing as expected
7 technical and discoverability checks passed without issues.
No meta robots noindex detected
1 sitemap location in robots.txt
4 parseable JSON-LD block(s)
Organization schema valid
FAQPage schema valid
WebSite schema valid
BreadcrumbList schema valid
Local business hint
Serve a local area or city?
If you serve customers in a specific city or region, re-run with “This site serves a local area” selected. You will get clear insights on your Google Business Profile and local directory listings.
Pull up to 5 URLs from /sitemap.xml and audit them next · great for docs, pricing, or blog.
Google Search Console Integration
Read-only access
Pair Lab Scores with Real Google Traffic
Lab scores test page code in a simulated browser. Google Search Console reveals actual customer searches, impressions, and clicks. Connect Search Console to see which pages and queries a fix touches.
Read-only analytics permission. No DNS changes or code access required.
Site Quality · Crawl provenance
Multi-page Site Quality
Deterministic HTML crawl through the HubSEO gateway (robots → sitemap → same-origin BFS). Budget: 25 pages free · up to 50 on Pro. Findings are measured from fetched HTML · not Lighthouse lab scores or CrUX field data.
Every check examines your page content, headings, images, and security settings. Follow the recommended fixes to keep search engines and visitors happy.
4 parseable JSON-LD block(s)
Passed
Pass
No meta robots noindex detected
Passed
Pass
BreadcrumbList schema valid
Passed
Pass
FAQPage schema valid
Passed
Pass
FAQPage schema valid
Passed
Pass
Organization schema valid
Passed
Pass
WebSite schema valid
Passed
Pass
1 sitemap location in robots.txt
Passed
Pass
05 · Verify & share
Evidence-backed · Live re-scan
Don’t trust the fix. Verify it.
Once your changes are deployed, bring your website back into the scanner. We test live in a real browser, compare against your baseline, and confirm real-world improvement.
