We found 5 issueson opusjake.aiworth 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 about page headshot renders as a 2000px tall strip
On /about/jake-schincariol the hero portrait (main.wrap>section.hero>figure.portrait-shell>img.portrait, images/opusjake-headshot.webp) is laid out at 317 by 2000 CSS pixels from a square 2000 by 2000 source. With object-fit: cover, the square photo is cropped to an extreme vertical sliver and scaled up, so on desktop the face is blown up across more than two full viewport heights and only hair, forehead, and part of a face are visible at any one scroll position. The same 317 by 2000 box is measured on mobile, where the portrait card runs past the bottom of the screen. The figure dominates the page layout and pushes the surrounding text content into a narrow left column.
Try it: Open /about/jake-schincariol on desktop and scroll the hero: the portrait box is 317px wide and 2000px tall, and the headshot is cropped to a vertical strip of the face.
Five security response headers are missing
The response from https://opusjake.ai/ is missing Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, X-Content-Type-Options: nosniff, Referrer-Policy, and Cross-Origin-Resource-Policy.
Try it: Run curl -I https://opusjake.ai/ and check the response headers for Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Cross-Origin-Resource-Policy.
Search and footer text fail color contrast
Several text elements on the project fall below the WCAG AA contrast minimum of 4.5:1. The library search placeholder "search the library…" renders at #8f8cb8 on #ffffff for a ratio of 3.17:1 at 13.5px, and the footer copyright line plus the "About Jake" footer link render at #8f8cb8 on #fafaf7 for a ratio of 3.03:1 at 10.5px. The same failures appear on /, /blog, /about/jake-schincariol and the blog article routes. axe-core classes the color-contrast rule at serious impact.
Try it: Open / and scroll to the grow section, then check the search field placeholder and the footer text against a contrast checker; the pale lilac on white measures around 3:1.
The profile photo renders as a full-screen face crop on mobile
On /about/jake-schincariol at a 390px wide viewport, the profile photo is rendered at a scale where one screen height shows only hair, forehead and eyes. The image spans the full content width and continues past the top and bottom of the viewport, so the whole second screen of the page is a blurry close-up with no text beside or around it. Upscaling also makes the image visibly soft at this size. Nothing else is painted in that stretch of the page.
Try it: Open /about/jake-schincariol on a phone or a 390px wide window and scroll to the profile photo, which fills more than a full screen with a cropped close-up of the face.
The about page portrait is cropped to a mouth on mobile
On mobile, /about/jake-schincariol renders the profile portrait at an extreme magnification: an entire viewport height at scroll offset 1328 is filled with a blurred nose, mouth and chin, with no face, head or surrounding layout visible. The image is heavily upscaled, so edges and skin detail are soft and pixelated at the rendered size. The crop stays the same across loads, so the whole screen is taken up by an unrecognizable fragment of the photo.
Try it: Open /about/jake-schincariol on a phone and scroll to the portrait, around 1300px down the page.
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.