We found 4 issueson hackeratlas.comworth 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.
robots.txt serves an HTML page
A request to /robots.txt on hackeratlas.com returns 200 with an HTML document rather than crawler directives. Crawlers fetching that path get markup they cannot parse, so no allow, disallow, or sitemap rules are being published. This is the single-page app shell answering an unrouted path instead of a static text file.
Try it: Run curl -i https://hackeratlas.com/robots.txt and look at the content type and body: it returns an HTML document, not text directives.
The homepage head has no description or share metadata
The entry document at / carries only a title of "HN Atlas" and an inline SVG icon. There is no meta description, no canonical URL, no og:title, no og:description, no og:image, and no twitter:card. Search results and link previews for the project therefore have no summary text or preview image to draw from, and the page declares no preferred URL.
Try it: Open https://hackeratlas.com/ and view source, then search the head for "description", "canonical", "og:", and "twitter:".
Four security response headers are missing
The response from https://hackeratlas.com/ 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://hackeratlas.com/ and check for Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, and Cross-Origin-Resource-Policy.
Orange text fails the AA contrast threshold
On the home route, orange text on the near-white background sits at a 3.04:1 contrast ratio where WCAG 2 AA requires 4.5:1. The failing nodes are the "Atlas" word in the header wordmark (#f56300 on #fbfbfa, 17px bold) and the trend markers on the topic cards, for example the "↑ 1.4×" kickers on the AI governance and Apple ecosystem cards at 11px. axe-core classes the color-contrast rule at serious impact, and the same nodes fail on a fresh load.
Try it: Open the home page and run axe-core or any contrast checker against the orange "Atlas" wordmark and the "↑ 1.4×" card kickers; both measure 3.04:1.
A rough edge in the layout
The topic cards on mobile keep the desktop fixed height, leaving a tall empty gap between the description text and the posts footer row inside each card.
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.