Guide
Lovable Site Speed in WordPress: What Changes
A Lovable app ships as a JavaScript bundle; a WordPress block theme ships as HTML and CSS. After a conversion the browser usually has less work to do, so first paint tends to be quicker. The variables that decide real speed are your host, your images and the plugins you add, not the theme. This guide lists what changes, what to measure and what to fix first.
What actually changes when you move off Lovable
Lovable builds React and TypeScript apps styled with Tailwind CSS and shadcn/ui. Apps created from 13 May 2026 use TanStack Start and are server-rendered, so the first response already contains HTML. Older apps are React plus Vite and render in the browser: the server sends a small shell, the browser downloads the bundle, then the page appears.
A WordPress block theme is different in kind. PHP assembles HTML on the server, the browser gets markup and a stylesheet, and no framework has to boot before text is visible. The converted theme from our converter contains templates, template parts, patterns and a theme.json. There is no React runtime in it.
So the shape of the load changes. On an older client-rendered Lovable app, time to first content depends on the bundle. On WordPress it depends on how fast the server returns HTML and how heavy your images and plugins are. Neither is automatically faster; they fail in different places.
Where WordPress tends to win
These are the parts of the page that usually improve after a conversion, mostly because the work moves from the browser to the server or disappears altogether.
- No JavaScript needed for text — headings, paragraphs, lists and images are in the HTML of the first response. A slow phone on a bad connection still paints the page.
- Smaller CSS surface — Tailwind utility classes become block markup and design tokens in
theme.json. The palette, fonts and type scale load as a small set of CSS variables. - Images get responsive sizes — WordPress generates several sizes per upload and writes
srcset, so phones download smaller files than desktops. - Caching is ordinary — a page cache in front of PHP serves the same HTML to everyone. Most managed WordPress hosts do this by default.
- Crawlers see the same HTML as people — relevant if your old app was client-rendered. We cover the detail in Is Lovable good for SEO?.
Where WordPress tends to lose
WordPress is slow when you make it slow. The theme we generate is static markup, so almost every regression after launch comes from something you added.
Plugins are the usual cause. Each one can add queries, CSS files and scripts to every page. A page builder on top of a block theme is the worst case: you pay for both. Contact Form 7 and WooCommerce are fine, but WooCommerce in particular brings its own scripts and is worth measuring once installed.
Hosting is the second cause. Cheap shared PHP hosting answers slowly under load, and no amount of front-end tuning fixes a slow first byte. If your Lovable site was on a fast static host, a weak WordPress host will feel like a step back. We compare the options in Lovable hosting.
The third cause is uploads. Lovable projects often contain large PNG or JPG hero images. The converter copies the images into the theme as they are; it does not re-encode them. A 3 MB hero is 3 MB in both systems.
Measure before you change anything
Fix the real bottleneck, not the one you assume. Take a baseline on the Lovable site first, then the same measurements on WordPress, on the same pages and the same connection.
One caveat for older React plus Vite apps: Lovable prerenders them on request only for verified search engines, link-preview bots and AI crawlers. Third-party scanners often see an empty shell, so their scores for the Lovable version can be misleading. Trust a real browser test over a scanner.
- Pick three pages — the homepage, one content page and one heavy page, such as a gallery or a product listing.
- Record time to first byte — open the browser devtools network panel, reload with cache disabled, and note the wait time on the HTML document.
- Record first visible content — watch the filmstrip or screen recording, not just the numbers. Note when the heading and hero image appear.
- Note total page weight — the devtools network panel shows transferred bytes. Find the three largest files.
- Repeat on mobile throttling — set the network to a slow profile and run the same three pages again.
A speed checklist for the converted site
Work down this list in order. The first three items account for most of the difference on a typical converted marketing site.
If you are still at the review stage, you can see the converted theme next to the original inside WordPress Playground in the browser. That preview runs WordPress in your browser tab, so it is a layout check, not a performance test. Measure speed on your real host after installing the theme.
- Resize and re-encode large images — export heroes at the width they are displayed, then let WordPress generate the rest. See Lovable images in WordPress for where the files live in the theme.
- Turn on page caching at the host — ask your host what it already caches before installing a caching plugin. Running two cache layers causes odd bugs.
- Keep the plugin list short — start with only what the site needs: an SEO plugin, Contact Form 7 if you have a form, WooCommerce if you sell.
- Self-host your fonts or limit the weights — the converter writes Google Fonts into
theme.json. Three weights are usually enough; see Lovable fonts in WordPress. - Do not add a page builder — the theme is edited in the Site Editor under
Appearance → Editor. A builder plugin duplicates that and adds weight. - Check the header and footer template parts — they load on every page. A large logo file there costs you on every view.
What the converter does and does not do for speed
Our converter produces a block theme: templates, header and footer template parts, one pattern per page, a theme.json with your palette and fonts, and your images copied into the theme. That output is static markup, which is the fast starting point. Conversion, review and the theme download are free, and every account includes two free AI-fix attempts.
It does not optimise media. Images are copied, not compressed or converted to another format. It does not install a caching plugin, choose a host or minify anything beyond what WordPress does itself.
Some things that were heavy in the React app simply do not arrive. Animations convert as their final state, carousels are approximated, and custom React state, event handlers, canvas, Lottie and third-party widgets are not converted at all. That removes JavaScript, but it also removes behaviour you may want back. The full list is on supported features. If you re-add those effects with plugins, you re-add the weight too.
Launch settings that affect perceived speed
Two WordPress settings are easy to miss and both show up in testing. Under Settings → Reading there is a checkbox called "Discourage search engines from indexing this site". Keep it checked while you build on a staging URL, and uncheck it before launch. It does not change load time, but it changes whether anyone ever measures your site.
Also check Settings → Reading → "Your homepage displays". The converter sets the front page on activation, but confirm it points at the page you expect. A homepage that redirects adds a round trip to every first visit.
Finally, keep your URLs stable. Settings → Permalinks controls the structure, and old paths from public/_redirects are carried over by the converter. A redirect chain costs real milliseconds; see Lovable redirects in WordPress for how to keep them short.
For anything about how Lovable itself serves and caches your app, check Lovable's documentation rather than guessing from test numbers.
FAQ
Is a WordPress version of a Lovable site faster?
Usually the first paint is faster, because the browser receives finished HTML instead of a JavaScript bundle it has to run. Whether the whole page is faster depends on your host, your image sizes and the plugins you install. A converted block theme is a fast starting point, but a slow host or a 3 MB hero image will undo it.
Why did my WordPress site get slower after I added plugins?
Most plugins add CSS, JavaScript and database queries to every page, not just the pages that use them. Install only what the site needs, then re-measure after each addition. Page builders are the heaviest case on a block theme, because they duplicate what the Site Editor already does.
Does the IQDesk converter compress my images?
No. It copies the images from your Lovable project into the theme as they are. Resize and re-encode large images before or after conversion, then let WordPress generate the responsive sizes it serves to phones.
Can I test speed in WordPress Playground?
No. Playground runs WordPress inside your browser tab, so its timings reflect your own machine, not a server. Use it to check layout and content during the review step, then measure real speed on your live host after you install and activate the theme.
Do I still need a caching plugin on WordPress?
Often not. Many managed WordPress hosts already run a page cache in front of PHP, and adding a second layer can cause stale pages and odd bugs. Ask your host what it caches first, and only add a plugin if nothing is caching full pages.