We found 4 issueson calckernel.orgworth fixing.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
How the composite score works
The overall score is a weighted average: Visual 18.75%, Accessibility 25%, Buttons and links 31.25%, Under the hood 12.5%, and Mobile 12.5%. Unassessed categories are excluded and the remaining weights are normalized.
Product categories start at 100. Each distinct verified finding deducts 30 points for a reproduced flow defect, or 18 for critical, 12 for high, 7 for medium, and 3 for low stored detector severity. Scores stop at zero and round to whole numbers. All verified findings count, including those beyond the displayed list. The formula is fixed and versioned, so the same saved evidence always receives the same score.
The backends comparison table runs off the phone screen
On /docs/backends/ at a 390px wide viewport, the backend comparison table extends past the right edge of the screen. The fourth column starts at the viewport boundary, so only the first one or two pixels of each of its three text lines render, while the WebAssembly row's first three columns fit. Body text in the sections below the table wraps normally within the same width, so the overflow is the table's own layout.
Try it: Open /docs/backends/ on a phone or a 390px wide browser window and scroll to the backend comparison table; the rightmost column is clipped at the screen edge.
The capability details table is cut off on mobile
On /docs/backends/ at a 390px wide viewport, the "Capability details (advanced)" table runs past the right edge of the screen. The fourth column is sliced at the viewport boundary: only the leading glyph of its header and of each cell value renders, so entries such as the "Yes / No" style answers in that column cannot be read. The first three columns ("Output", "Typical command", "Checked overflow / bounds") render in full, and there is at least one further column beyond the clipped one.
Try it: Open /docs/backends/ on a phone or a 390px wide browser window and scroll to the "Capability details (advanced)" table; the fourth column is cut in half at the right edge.
The homepage head has no canonical or social preview tags
The entry document at / declares a title, a meta description, and an SVG icon, but no canonical URL, no og:title, no og:description, no og:image, and no twitter:card. Links to the project shared on social platforms and chat clients fall back to whatever those clients can scrape, with no controlled title, summary, or preview image. Without a canonical declaration, any duplicate or parameterized URL for the homepage is left to be resolved by search engines on their own.
Try it: Load https://calckernel.org/ and view source, then search the head for "canonical", "og:" and "twitter:card".
Four security response headers are missing
The response from https://calckernel.org/ is missing Strict-Transport-Security, Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, and Cross-Origin-Resource-Policy.
Try it: Run curl -sI https://calckernel.org/ and check the response for Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, and Cross-Origin-Resource-Policy.
A rough edge in the layout
The first table cell's label wraps mid-word, leaving a two-character fragment orphaned on its own line inside the narrow column.
A rough edge in the layout
The command code spans in the second table column wrap across five lines with each fragment keeping its own pill background, producing broken, uneven inline chips.
A rough edge in the layout
The inline code chip for the Windows compiler filename wraps across two lines, splitting its pink pill background into two fragments mid-token.
A rough edge in the layout
The inline code fragments in the Typical command column wrap onto five separate lines with ragged highlight blocks of differing widths, breaking a single command across many lines.
Probie fixes this for you.
This report came from one visit. When installed on your project, Probie watches real sessions, reproduces failures, and opens tested fixes as pull requests.
Sign up and get this fixedFree inspection
What should Probie inspect next?
Enter a project URL. There is nothing to install.
Probie checks every issue twice, respects robots.txt, and backs off at bot challenges.
Enter an address and we will email the report card link.


