01
Cold start
The first visitor sees a blank screen
Assess whether waiting, retry and recovery are clear—not just a laboratory speed number.
Public-domain QA for Replit apps
Publishing from Replit? Check the first visit on the public domain.
Open the published Replit app without your session and review the first response, direct links and saved results. Preflight collects browser evidence on reachable pages; restarting the host and auditing storage are outside the run.
For public demos, internal tools and compact full-stack applications hosted on Replit.
01 / risk map
Where Replit builds need a real browser
Review these scenarios before sharing. The automated report records observable issues on the pages you select.
02
Session
The owner sees more than a guest
A clean session reveals dependencies on workspace state, saved cookies or pre-created data.
03
Storage
Data disappears after a restart
Repeat the key flow after reload and a new session to separate temporary memory from persisted output.
02 / visitor trace
Four steps for your manual review
Use this sequence alongside the report to review behavior that depends on your business rules and data.
Replit deployment / first visit
The report contains browser-confirmed issues with links to evidence. Use them as a queue of fixes before sharing the app again.
Open a sample report- 01
Open as a guest
Without a Replit workspace, owner cookie or local state.
- 02
Wait for first response
Inspect the waiting state and recovery from a slow start.
- 03
Create and persist
The core action leaves a result after refresh.
- 04
Return by URL
A direct address and new session lead to the expected place.
launch checklist
Before sharing a Replit link
- Cold start has a clear waiting state
- A guest cannot see owner-only data
- Created output persists after reload
- Public domain, direct URLs and OG preview work
03 / exact questions
Replit QA, without vague promises
What the run can and cannot prove.
Do you enter my Replit workspace?
No. Only the published app is tested; workspace and source access are not required.
Is a cold start automatically a failure?
No. It becomes a problem when the user gets a blank or dead-end experience without explanation or recovery.
ship with evidence