122 of 124 basic checks passed; performance is scored separately.
What to fix first
Based on public HTML, sitemaps, and one mobile Lighthouse lab test.
P1Mobile above-the-fold content loads slowlyHomepage Lighthouse lab test · High confidence
Performance score 57; FCP 3.2s and time to interactive 11.6s. Inspect above-the-fold JavaScript, fonts, and the rendering path, then verify each change in Lighthouse.
P2No usable robots.txtSite-wide · High confidence
The root /robots.txt returns 404; the same path under the project returns HTML.
If you control the GitHub Pages root, publish a plain-text robots.txt and declare the existing sitemap.
P3No JSON-LD found on sampled pages24 of 24 pages · High confidence
No application/ld+json was detected on the homepage or the 23 sampled API documentation pages.
Add SoftwareApplication to the homepage and BreadcrumbList to documentation pages, then validate them with testing tools.
P3API documentation HTML is largeSampled API pages are about 221–257 KB
The 23 sampled API pages return roughly 221–257 KB of server-rendered HTML.
Measure repeated navigation and code markup, reduce duplicate DOM first, then retest representative API pages.
PassedCore page tags are complete and sitemap coverage is broad24 of 24 sampled pages passed core checks
All 24 pages returned 200 and had unique titles, descriptions, canonicals, and exactly one H1.
sitemap.xml contains 246 URLs; llms.txt and llms-full.txt also help AI tools understand the documentation structure.
- Homepage title: RazorConsole: C# Terminal UI Framework with Razor
- Homepage description length: 151 characters
- Sample: homepage + first 23 API pages in the sitemap
Identify the LCP element and blocking resources, then save a performance baseline.
Publish a valid robots.txt and add homepage and breadcrumb structured data.
Reduce API-page HTML and rerun mobile Lighthouse to verify the changes.