We found 6 issueson deepopen.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.
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.
Try it: Open /, /login, /register and /creator in separate tabs and compare the tab titles; all four read "Deepopen - AI 创作平台".
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.
Try it: Load https://deepopen.com/ and view source, then search the head for "canonical", "og:" and "twitter:card".
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".
Try it: Open /login, focus the Email field, and check that the browser or password manager offers no saved credential; inspect both inputs and confirm autocomplete and name are absent.
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.
Try it: Open /register and inspect the three inputs; none has an autocomplete attribute on a form whose purpose is account creation.
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.
Try it: Run curl -sI https://deepopen.com/ and check the response headers for Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Cross-Origin-Resource-Policy.
Creator dropdowns have no accessible name
On /creator, the select triggers in the AI 创作台 row fail the axe-core button-name rule at critical impact. 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.
Try it: Open /creator on desktop and run axe-core, or inspect the select triggers in the AI 创作台 row and check for aria-label or accessible inner text.
A rough edge in the layout
The hero heading emoji wraps onto its own second line below the title text, leaving a large gap between the heading and the subtitle.
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.