How do I test mobile devices?

Open the published site on a real phone (or use your browser's device toolbar as a fallback) and check layout, tap targets, forms and navigation at common breakpoints.

Submit every form with valid, invalid and empty data, confirm error messages appear, and check that submitted data actually lands where it should (database, inbox or integration).

How do I test user registration?

Sign up with a real and a duplicate email, confirm verification emails arrive, check password rules, and confirm a new account only gets the access it should.

How do I test password reset?

Request a reset with a real account, confirm the email arrives with a working link, complete the reset, and confirm the old password stops working and the reset link can't be reused.

How do I test payments?

Run a real Stripe test-mode transaction end to end — checkout, webhook, database update and confirmation email — before switching to live keys.

How do I test admin permissions?

Log in as a non-admin account and try to reach every admin action directly (URLs, buttons, API calls) to confirm the server — not just the UI — blocks it.

Try reading and writing data as a different logged-in user and as a logged-out visitor to confirm row-level security actually blocks what it should, rather than assuming the policy is correct.

Check that every page has a unique title and meta description, images have alt text, the site generates a sitemap, and preview the page as a search engine or social share would see it.

How do I test website speed?

Run the published (not local) URL through a tool like Google PageSpeed Insights or WebPageTest, and check real load times on mobile data, not just your fast office wifi.

How do I test different browsers?

Open the published site in at least Chrome, Safari and Firefox on both desktop and mobile, and check layout, forms and any browser-specific features work in each.

How do I check for broken links?

Click through every nav item, footer link and CTA yourself, or ask Lovable to list every link on the site so you can verify each one resolves before launch.

How do I check for console errors?

Open your browser's developer console on every key page of the published site and look for red error messages — then ask Lovable to fix each one by name.

How do I back up my project before launch?

Bookmark the current state in Version history, and push to a connected GitHub/GitLab repo via Git sync so you have a full backup outside Lovable too.

What should I check before launching a Lovable website?

Q: How do I test my Lovable app?

Work through core user flows manually in Preview and on a published link, on desktop and mobile, as a logged-out user and as a normal account — not just as the builder.

Last checked 31 Aug 2026

Short answer

Run through security, forms, auth, payments, mobile display, browser compatibility, speed, SEO basics and broken links before you hit Publish.

The pre-launch pass

Treat launch like a checklist, not a feeling. Work through these in order:

Security — RLS on every table, no exposed secrets, admin actions enforced server-side. See /questions/what-security-checks-should-i-do-before-launching.
Core flows — sign-up, login, password reset, forms, and payments all tested end to end, not just visually.
Permissions — a normal user account can't reach admin routes or another user's data.
Mobile and browsers — layout and interactions work on a real phone and in at least Chrome, Safari and Firefox.
Performance — page loads reasonably fast; check with a real speed tool, not just "it feels fine".
Content basics — page titles, meta descriptions, a favicon, no placeholder ("Lorem ipsum") text left behind.
No console errors on the published preview.
No broken links, especially in the footer/nav and any legal pages (privacy policy, terms).
Custom domain and SSL connected and verified, if you're using one.
A backed-up version you can revert to — see /questions/how-do-i-back-up-my-project-before-launch.

A prompt to kick off the review

I'm about to launch this project. Check for console errors, broken links, missing form validation, and confirm RLS is enabled on every table. List anything that needs fixing before I publish.

What usually goes wrong

Publishing straight after a feature is "working" in the builder's own test account, without trying it as a fresh visitor.
Forgetting the custom domain's SSL certificate can take time to provision — don't do this the minute before launch.
Leaving analytics, error tracking or a contact-form email address unconfigured, so you find out about problems from users instead of from data.

Individual test types are covered in their own pages — start with /questions/how-do-i-test-my-lovable-app.

Sources

Security overview

Was this answer helpful?