PROBIE
Fix these issues
Report readyDispatch 45

Nothing ondeepopen.comworth reporting.

Probie inspected deepopen.com the way a new customer would. 4 pages, desktop and phone, 7 minutes. Sep 25, 2026.

4 pages visited101 controls found35 clicked
deepopen.com's report cardSep 25, 2026

Nothing serious broke.

0 issues
See the breakdown
Probie doesn't stop at the report.Sign up and turn these findings into tested pull requests.
Fix these issues →
Probie on site

Watch the inspection.

We navigate your site the way customers would. Idle time is skipped.

Inspect your own site
scores · out of 100
100Getting the productEvery step checked between arriving and paying worked.
100Trust before buyingNo contradictions or broken pages found before buying.
100MobileNo verified phone layout problems on the pages a buyer needs.
100SpeedNo verified slow pages or slow responses on the pages a buyer needs.
72Polish and auditFour routes share one page title
How the composite score works

The overall score is a weighted average of the categories: Getting the product 40%, Trust before buying 20%, Mobile 15%, Speed 15%, and Polish and audit 10%. It is never more than 10 points above the Getting the product score, because a product a visitor cannot get cannot score well on anything else, and never more than 25 points above the weakest category, so one badly broken area is not averaged away. Any issue in the main list caps it at 89, so a score above 90 means nothing worth fixing was found.

Each category starts at 100 and stays there when nothing was found in it, whether or not the inspection got that far. Each distinct verified finding deducts 60 points for a serious problem on the path from arriving to paying, 40 for another serious problem, 30, 15 or 8 by high, medium or low severity otherwise, and 4 for an audit finding. Each additional finding below the list takes 2 more points off the overall score, up to 10. Scores stop at zero and round to whole numbers. The formula is fixed and versioned, so the same saved evidence always receives the same score.

issues
No issues found in the pages and actions checked.
additional findings
Medium

Four routes share one page title

The routes /, /login, /register and /creator all render the same document title, "Deepopen - AI 创作平台". Distinct pages with distinct purposes are indistinguishable in browser tabs, bookmarks, history, and search result listings. The login, register, and creator screens carry no title text of their own.

Medium

The homepage head has no canonical or social preview tags

The entry document at / carries a title and description 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 apps therefore have no declared preview title, summary, or image, and search engines get no canonical declaration for the homepage. The favicon link is present and returns 200, so browser identity is intact.

Medium

The sign in fields block password manager autofill

On /login, neither credential field carries an autocomplete hint: input#login-email and input#login-password both have autocomplete unset, and neither input has a name attribute. Browsers and password managers rely on those hints to offer saved credentials, so the email and password fields on the only sign in form are not reliably autofilled. The form element also has no action and defaults to method="get".

Medium

The sign up fields have no autocomplete hints

On /register, the three sign up fields carry no autocomplete attribute: input#register-name (Display name), input#register-email (Email, type=email), and input#register-password (Password). Browsers and password managers therefore get no hint for name, email, or new-password on an account creation form, so saved values are not offered and generated passwords are not reliably stored. The expected tokens for this form are name, email, and new-password.

Medium

Six security response headers are missing

The response from https://deepopen.com/ is missing Strict-Transport-Security, Content-Security-Policy, CSP frame-ancestors or X-Frame-Options, X-Content-Type-Options: nosniff, Referrer-Policy, and Cross-Origin-Resource-Policy.

Medium

Creator dropdowns have no accessible name

The model picker (.min-w-[190px]) and the aspect ratio, resolution, and duration selects (.w-[120px].border-input.pr-2) are rendered as role="combobox" buttons with no inner text exposed to screen readers, no aria-label, no aria-labelledby, and no title attribute. The visible values such as "16:9", "720p", and "5s" sit inside the control, but nothing announces what each control sets, and the disabled model trigger shows only placeholder styling. This maps to WCAG 2.1 A, 4.1.2.

Medium

The language toggle label fails color contrast

On /login, the active language toggle button labelled "EN" renders teal text (#008f82) on a white background at 11px, a contrast ratio of 3.99:1 against the 4.5:1 required by WCAG 2.1 AA for text this size. The button sits above the sign-in card and is the control that switches the interface between Chinese and English.

from report to pull request

Probie fixes this for you.

Stop customers hitting the same friction. Connect your codebase and Probie reproduces these failures, tests the fix, and opens a pull request for your review.

Sign up and get this fixed
PRFixes, one PR at a time
probie/fix-1+12−4checks passing

Free 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.

Send this report to an inbox.

Enter an address and we will email the report card link.