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 different browsers?

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

Last checked 31 Aug 2026

Short answer

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.

Why this matters

CSS, form behaviour and some JavaScript APIs render or behave slightly differently across browsers — especially Safari, which handles some things (date inputs, flexbox edge cases, autofill styling) differently from Chromium-based browsers.

How to test

Cover at minimum: Chrome, Safari and Firefox, on both desktop and a mobile device (Safari on iOS is especially worth checking separately from desktop Safari).
Check layout — spacing, fonts, alignment — is consistent, not just "not broken".
Check interactive elements — dropdowns, date pickers, modals, sticky headers — behave the same everywhere.
Submit a form in each browser to confirm validation and autofill don't misbehave.
Check the browser console for errors in each — an error that's silent in Chrome can sometimes surface differently elsewhere.
If you don't have access to every OS/browser combination, a cross-browser testing service (e.g. BrowserStack) can fill the gap — this is a genuine limitation of testing solo.

A prompt if something looks wrong

This [component] looks broken specifically in Safari — check for CSS or JS that Safari handles differently and fix it while keeping Chrome/Firefox working.

What usually goes wrong

Testing only in the browser you personally use, then discovering a layout bug in Safari after launch.
Custom date pickers or file inputs that behave inconsistently across browsers.
Fonts or icons that fail to load in one browser due to a missing fallback.
Not checking older but still common browser versions your actual audience might use, if you have any real usage data to check against.

See also /questions/how-do-i-test-mobile-devices for the mobile-specific pass.

Was this answer helpful?