Small details.
Better websites.
Look beneath the surface. Inspect your HTML, CSS, JavaScript and the details that help a page work, load and get discovered.
Fetching the page and linked files, validating source, and checking discovery details. This can take up to 45 seconds.
One page. A clearer picture.
Find what needs fixing, understand why it matters, and take an actionable report back to your editor.
Document & markup
Doctype, HTML5 structure, unclosed tags and legacy markup.
Styles & colors
CSS syntax, property values and CSS2.1 compatibility.
JavaScript
Script and module syntax, plus common lint findings.
Metadata & discovery
Meta tags, favicon, robots.txt and sitemap XML.
Optimization
Page weight, blocking scripts, caching and image dimensions.
Accessibility basics
Language, labels, alternative text and semantic markup.
A source inspection, with clear coverage notes. Browser rendering, runtime behavior and a full website crawl need separate testing.
Inspection report
Inspection coverage
Findings & fixes
No findings match these filters. Try a different topic or clear your search.
Resources inspected
Directly fetched files and their responses. Imported stylesheets, imported modules, frames and dynamically loaded files are outside this inspection.
| Resource | Response | Size |
|---|
Discovered metadata
Metadata from the document head, displayed as text.
| Tag | Value |
|---|
What this report covers
HTML4/XHTML declarations are detected. Legacy markup is reviewed against HTML5 rules, with a separate XML well-formedness check for XHTML. CSS2.1 mode checks the property list and selected modern features; it is not full CSS2.1 conformance testing. No report here certifies a page as error-free.
For a formal legacy document or CSS profile check, use the W3C markup validator or W3C CSS validator. Local checks use HTML-validate, CSSTree, PostCSS and Acorn.
Limits: 2 MB HTML; six linked stylesheets and six linked scripts, up to 1 MB each; two icons and two sitemap files; 30 seconds for fetching. Limits, missing files and failed fetches appear in the findings. No report is saved automatically.