What should I check before launching a Lovable website?

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

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.

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

How do I test mobile devices?

Last checked 31 Aug 2026

Short answer

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.

Why the browser preview isn't enough

Resizing a desktop browser window approximates mobile layout but misses real-world issues: actual touch targets, on-screen keyboard behaviour, mobile Safari quirks, and real network speed. Test on an actual device wherever you can.

How to test properly

Open the published link on your own phone — both iOS and Android if you have access to both.
Check at minimum:
- Navigation menu opens/closes correctly and doesn't trap scrolling.
- Buttons and links are large enough to tap accurately (not cramped together).
- Forms: tapping an input brings up the right keyboard type (email, number) and doesn't break layout when the keyboard appears.
- Images and text scale properly — no horizontal scroll, no overflowing text.
- Any modal or drawer component is dismissable on touch.
If you don't have a second device, use your browser's built-in device toolbar (Chrome/Firefox/Safari dev tools "responsive design mode") as a first pass, but don't rely on it exclusively — it doesn't fully simulate touch or mobile browser rendering quirks.
Ask Lovable to fix specific issues you find:

On mobile, the [nav/form/section] overlaps at narrow widths — make it responsive down to 375px wide.

What usually goes wrong

A layout that looks fine at "iPhone" preview width but breaks on smaller/older devices (check down to ~360-375px).
Fixed-position elements (sticky headers, chat widgets) covering content or form fields once the mobile keyboard opens.
Hover-only interactions (tooltips, dropdown-on-hover) that have no equivalent tap behaviour on touch devices.
Forgetting to test in landscape orientation.

See also /questions/how-do-i-test-different-browsers for the equivalent desktop check.

Was this answer helpful?