Lovable test data

Each of the three fixed briefs (a ceramics shop, a café and a wedding photographer) was pasted in full into Lovable's chat. The clock ran from sending the brief to the first draft being live at a public address.

The shop was live in about 4 minutes, the café in about 3.5 minutes and the photographer in about 4 minutes.

Lovable asked one question in all three builds: whether to set up a Shopify store for the shop. I skipped it. Publishing is one click and puts the site on a lovable.app address.

At the end of each build the AI listed what it had and hadn't done, including that online payment wasn't working yet and that it had made the product photos itself.

Every page of the three first drafts (5 per site) was checked at 360, 768 and 1440 pixels wide and on a phone-sized screen. Faults were counted once per type on each page: horizontal scrolling, low-contrast text (WCAG AA), placeholder text or images, broken images, overlapping elements and tap targets that are too small.

No page scrolled sideways, nothing was left as a placeholder and no image was broken. The designs look polished and fit each business.

Small tap targets were found on all 15 pages, mostly the menu links. Small, light labels failed the contrast check on 7 pages, all five photographer pages among them.

An "Edit with Lovable" badge sits in the bottom corner of every page until you switch it off on a paid plan. It was not counted as a fault.

Each brief has 20 checkable facts (prices, address, hours, phone, policies, pages). Each live first draft was read page by page and every fact marked right, missing or wrong. Anything the AI added that was not in the brief was listed as invented.

All 60 facts were right: 20 on the shop, 20 on the café and 20 on the photographer site. Every page the briefs asked for was there.

Nothing was invented: no testimonials, no extra products, no made-up addresses or hours. The only thing the AI made itself was the photos, and it said so.

The same twelve edits for every builder, done on the café site: move a section, change the font site-wide, change the colours site-wide, add a page with its menu link, edit the footer, add a form field, replace an image and choose what part shows, change a button's link, duplicate a section, change the phone layout on its own, embed custom code, and rewrite one section from a written instruction. On Lovable each edit is a chat message.

All twelve worked without a workaround, and each was checked on the published site.

Each edit took 33 seconds to about 2 minutes, except the new photo, which the AI generated in about 5 minutes. The AI checked its own work every time and said what it had changed.

The phone-only change stayed on phones: the headline became 30 px and centred there, and stayed 60 px and left-aligned on desktop.

Lighthouse mobile tests on the home page and one inner page of each live site, three runs each, 18 runs in all.

Every page scored between 74 and 92. The median of the 18 runs was 84.

The main content appeared after about 3.6 seconds (median) on a simulated phone connection. Pages weigh only 0.3 to 1.1 MB.

• Speed is retested on the live tool pages; this grade uses the 22 October runs.

The twelve points were checked in the published HTML and files of all three sites. Lovable has no SEO settings screen, so anything missing was asked for in the chat and checked live.

Present: unique titles and meta descriptions written by the AI on every page, one H1 per page, alt text on all 20 photos, clean URLs, robots.txt and Open Graph tags.

Done by asking: a 301 redirect (/old-menu to /menu) was live about 3 minutes after I asked, and a noindex tag on each site took under a minute.

Missing: no sitemap.xml, no canonical tags and no structured data (schema) on any page. The AI can add them, but they are not there by default.

• Images are sent as JPEG only (no WebP or AVIF), and 9 of 20 are larger than shown.

Each point was asked for in the chat (or set up in Lovable Cloud) and then tried on a live site.

Our test subdomain was live with HTTPS 4 minutes 39 seconds after starting, and the lovable.app address now redirects to it.

Form emails need a sending domain first (one TXT and two NS records); it was ready in about 8 minutes, then a booking-form email reached our inbox within about 15 seconds.

The AI built a blog and wrote the first post in 48 seconds. Variants, shipping rules and visitor analytics work. Email marketing stops at a sign-up box (sending needs Klaviyo or Mailchimp), and bookings are a form, not a calendar.

With payments switched on, a $107 test order (a mug, a gift-wrapped bowl and a $12 PDF guide) went through Stripe's test checkout with the right totals, and the PDF downloaded from the thank-you page. Sales tax can't be switched on in test mode, and the PDF link works for anyone who has it.

• Sales tax was not available in Stripe's test mode, so it counts as not met.

I downloaded the code, built it and ran it on my own computer, exported the database and read Lovable's terms.

"Download codebase" gave a 297 KB zip of the café's full source code in under a second. It built in 10 seconds and ran on plain Node.js, every page the same as the live site.

Form entries and other data export from the database as CSV. Two-way sync with GitHub, GitLab or Bitbucket is built in.

Lovable's pricing FAQ says "You own your code", including the AI's output and your customers' data.

• The site needs a small server (not a plain static host), and forms and the database still use Lovable Cloud unless you move them.

The same three questions went to each support channel: connecting a domain bought elsewhere, contact-form messages not arriving, and changing the card and switching from monthly to yearly billing.

The docs assistant asked for a CAPTCHA, which I don't solve. Lovable's in-app AI in Chat mode (no credits used) answered all three correctly in 23 to 33 seconds.

Its form answer pointed to exactly what I later had to set up: an email sending domain. A human channel exists: email and a support form on paid plans, plus a Discord community.

• The human channel's reply time was not measured.

Every plan was read on Lovable's US pricing page on 22 October 2026, monthly and yearly. The figure graded is the yearly cost of the cheapest plan that connects your own domain and removes the Lovable badge.

The cheapest plan for that is Pro at $21 a month billed yearly ($252 a year), or $25 a month billed monthly. The price is the same at renewal.

Pro includes 100 credits a month. Every build and edit uses credits (the café's 14 messages used 12.2), and unused monthly credits expire after two months.

Lovable's payments charge 2.9% + 30¢ per sale. The free plan has a lovable.app address and the badge.

• Prices change often; the price tracker rechecks them every day.