Report loading
mecfssciencedigest.org
Preparing the full page inventory and screenshots.
Score
73
Issues
Analyzed
Report loading
Preparing the full page inventory and screenshots.
Good
Health Score
Here's the simple version
75/100 - good. Good enough to understand, not good enough to ignore. Significant visual instability and accessibility barriers currently undermine the user experience and search engine performance of _ME/CFS Science News_. The site successfully establishes a distinct, memorable brand identity through a consistent brutalist design language and high-value, niche-specific content. The semantic page structure and clear heading hierarchy support effective content extraction for both human readers and automated agents. A high-priority performance issue exists regarding Cumulative Layout Shift (CLS), which currently stands at 0.564—well above the Google-recommended threshold of 0.1. This visual instability, combined with serious accessibility concerns regarding insufficient color contrast ratios, creates a frustrating experience for users and negatively impacts search rankings. There is a major opportunity to optimize the site for the emerging AI-driven search landscape. While the site is currently discoverable by AI crawlers, the lack of JSON-LD structured data, a missing sitemap.xml, and an incomplete /llms.txt file prevent answer engines from fully indexing and citing the site's specialized research summaries with high precision. **First 30 Days** - Resolve high-priority Cumulative Layout Shift (CLS) issues by defining explicit dimensions for images and late-loading elements. - Correct color contrast deficiencies to meet WCAG 2 AA accessibility standards. - Implement a /sitemap.xml and basic JSON-LD structured data to improve machine readability.
Good
Health score
Launch blockers
No major launch blockers found.
The rest of the report is a fix queue, not a reason to panic.
Fix first
Start with the top 3.
These are the items most likely to improve trust, speed, or conversion.
Best next step
Hand the fix list to your builder or AI agent.
The technical detail is still here when they need evidence.
Biggest area to improve: SEO, which mostly means how search engines understand the page.
The full report has all the proof. This is the owner-friendly version of what to do first.
Plain-English reason
This affects speed and loading experience. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Investigate elements causing shifts, likely the late-loading Google AdSense iframe or font swaps. Ensure all containers for ads and dynamic content have reserved dimensions (width and height) to prevent layout jumps. Use `font-display: swap` and preloading for critical fonts.
The page has a CLS of 0.564, which is significantly above the Google recommended threshold of 0.1. This indicates significant visual instability as elements move around during loading, which can frustrate users and impact perceived quality.
Plain-English reason
This affects speed and loading experience. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Set explicit width/height on all images (see PERF-001), reserve space for ads and embeds with min-height, and use font-display:optional or size-adjust to prevent FOIT/FOUT-driven shifts. Cookie banners should overlay rather than push content.
CLS measures how much visible content unexpectedly shifts during page load. Banners that slide in, images without dimensions, and late-loading web fonts are the usual culprits. Google flags anything above 0.1 as needing improvement.
Plain-English reason
This affects whether everyone can use the site. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Element matching `article:nth-child(1) > div > .brutalist-meta > div > span:nth-child(1)` has contrast ratio 3.98; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds. Fix any of the following: Element has insufficient color contrast of 3.98 (foreground color: #ffffff, background color: #6972f0, font size: 8.3pt (11px), font weight: bold). Expected contrast ratio of 4.5:1
Same data as the full report, grouped by what a non-technical owner should do with it.
High-impact fixes that should usually be tackled before anything else.
Important fixes that may need more development time or a design decision.
Nothing in this bucket.
Polish and lower-priority work. Useful, but not where to start.
Need the detail?
The full report still has every finding, evidence, rule ID, filters, screenshots, and technical panels.
