The free production readiness check
What the free check looks at, what each result means, and how to go from a report to a live site.
What it is
A free, automated check of a website or web app before you put it online. It runs the real production build, the same way a ProHostiva deployment does, and looks for the problems that most often break a site or leak something in production. You get a report that says what it found and how to fix each thing.
You don't need an account, and the report is useful even if you host somewhere else.
It isn't an audit
Run a check
Open the check
Go to Check my project.
Give it your project
Paste the address of a public GitHub repository (you can also name a branch), or upload a ZIP. For a private repository, download it from GitHub as a ZIP and upload that.
Wait for the report
Most checks take a few minutes, mostly for the build. Keep the page open, or keep the link and come back: the report has its own private address.
What it looks at
| Area | What's checked |
|---|---|
| Project | The framework, runtime, package manager and versions, detected the way a deployment detects them. |
| Build | Dependencies are installed and the production build is run in an isolated, resource-limited container. Also flags packages your code imports but doesn't list. |
| Deployment | Whether ProHostiva can deploy this kind of project, and if not, what would need to change. |
| Security | Well-known key and token formats, private keys, committed .env files, secrets exposed to the browser and a few risky settings. |
| Environment | The environment variables your code reads: which ones we set for you and which ones you'll need to provide. |
| Performance | Oversized images, videos, files and JavaScript bundles, and dependency or build folders included by mistake. |
| SEO | Page title, description, mobile viewport, canonical link, language, robots.txt, sitemap and structured data, where SEO applies. |
Reading the results
The report starts with one of three results:
| Result | Meaning |
|---|---|
| Ready | None of our checks found anything that needs fixing first. Any suggestions listed are optional. |
| Needs attention | It can probably be deployed, but some findings are worth fixing first. |
| Not ready | Something would stop a deployment as the project is now. Those findings are marked Blocks publishing. |
Each finding is marked with how it ended:
- ✓ Verified: checked, nothing to do.
- ⚠ Needs attention: worth fixing. Low-importance ones are labelled Suggestion and never change the result.
- ℹ Not applicable: doesn't apply to this kind of project (for example SEO for an API).
- ? Could not determine: we couldn't check it this time, and we say why rather than guess.
Findings also say whether they were verified (we actually did it, such as running the build) or inferred (read from your files, so it could be wrong). If the build couldn't run, the result is never "Ready".
From report to live site
- Fix and check again. For a GitHub repository, push your fixes and click Re-run the check: it checks the latest commit. For a ZIP, upload the updated file.
- Publish with ProHostiva. From the report, create your account; the checked project comes with you. A GitHub repository is connected to your new website once you've connected GitHub. A checked static site from a ZIP becomes your website's files directly; for other projects from a ZIP, upload it on your website's page (see Deploying from a ZIP).
Your code and privacy
- Your project's files are deleted as soon as the check finishes. The one exception: an uploaded ZIP of a static site is kept for up to 72 hours, so it can become your website if you sign up.
- The report is kept for 30 days at its private link, then deleted.
- Secret values found in your code are never stored or shown: the report only says what kind of secret and where (for example
src/config.ts:12). - The build runs with no access to your ProHostiva account, other customers or our systems, and is thrown away afterwards.
Limits
- ZIP uploads up to 25 MB; public repositories up to 100 MB.
- Up to 6 checks an hour and 20 a day from one connection.
- When many checks are waiting, new ones are paused for a few minutes. If today's free builds are used up, the check still runs but reports the build as not verified.