Flatsome fix
Why Is My Flatsome Store So Slow? The Fixes That Move the Number
Flatsome is not an especially heavy theme, so a slow Flatsome store is usually a story about what was built on top of it. The demo home page arrives with sliders, banner grids and product carousels, and most stores go live with all of them. Speed returns when you decide what the first screen needs and let the theme's own performance options handle the rest.
What you are seeing
- The home page slider shows an empty band before its first image appears
- PageSpeed Insights names a banner as the largest element, and it arrives late
- Shop and category pages hesitate before any products show
- The store feels quick at your desk and slow for customers on phones
- A speed plugin went in and the mobile score barely moved
Why it happens on Flatsome
Most common first.
- 1
A first screen made of sliders
A full-width slider at the top of the page means several large images, a slider script and a first slide that cannot appear until that script has run. Put a banner grid and a product carousel beneath it and a phone has a great deal to do before it shows anything worth looking at. The demo was built to sell the theme. Your home page has a different job.
- 2
Banner images served at full size
Banner and image elements in UX Builder each carry an image size setting. Left on the original upload, a banner sends a phone the same file it sends a wide desktop monitor. A handful of those on one page can outweigh everything else the page loads.
- 3
Lazy loading aimed at the wrong images
Flatsome can lazy load images and the backgrounds of banners and sections, which is right for everything below the first screen. Applied to the top banner it delays the one image Google measures as Largest Contentful Paint. Add a second lazy loader from an optimization plugin and images can flicker, or arrive late twice.
- 4
Product elements that query on every view
Each product slider, category grid and featured row is a separate database query when the page is built. Behind a page cache those queries run once per refresh of the cache. Without one, or on pages that cannot be cached, they run for every visitor. Live search in the header adds uncached requests of its own as shoppers type.
- 5
The parts of a store no cache can hold
Cart, checkout and account pages are built fresh for each shopper, and the header cart's fragments request runs outside the page cache. Those depend on server speed, PHP version and the plugin list far more than on anything in the theme.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Measure the pages that earn money
Run the home page, one category page and one product page through PageSpeed Insights on mobile. Note the Largest Contentful Paint element on each. On a Flatsome store it is usually a slider or banner image, and it tells you where to work first.
- 2
Thin out the home page in UX Builder
Do this on a staging copy. Open the home page in UX Builder and replace the top slider with a single banner, or cut it to one slide. Remove product rows nobody scrolls to. Each element you remove takes its images and its queries with it.
- 3
Set an image size on every banner
Select each banner and image element and choose a size that fits how it is displayed, not the original upload. Before uploading a new hero image, export it at the width it is actually shown and in a modern format.
- 4
Set lazy loading once, in one place
Under Flatsome, Advanced, open the performance settings and turn on lazy loading for images and for banner and section backgrounds. Then make sure the first banner on each key page is not lazy loaded, using whatever exclusion your version or optimization plugin offers, and switch off duplicate lazy loading everywhere else.
- 5
Trim what loads on every page
In the same performance settings, turn off what the store does not use. Depending on the version, that includes emoji scripts and block editor styles. Cut web fonts to the families and weights in use in the theme's typography settings. Review the UX Blocks placed in the header, footer and menus, since anything there loads on every page.
- 6
Cache last, and check the cart
Add or tune one page cache with cart, checkout and account pages excluded, then confirm the header cart still updates. If uncached pages remain slow to respond, what is left is hosting and plugins, and the general WordPress speed guide takes it from there.
Keep it from coming back
- Give every new banner an image size and a compressed upload
- Add a home page element only after removing another
- Re-test on a phone after each Flatsome update, since performance options change between releases
- Keep one lazy loader and one page cache, each with a clear job
The permanent fix
A faster Next.js build, with a CMS made for your business
If the store is still slow on phones after the home page is thinned, the images are sized and the caching is right, what remains is WordPress and WooCommerce assembling pages on demand with a full plugin stack behind them. A Next.js build serves product and content pages as static files and loads only the code each page uses, with a custom CMS for the catalog and the copy. That is worth considering when speed is costing orders, and not before the cheaper fixes have been tried.
| On Flatsome today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Flatsome site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Yes, when the store lets it be. Its own stylesheet and scripts are modest next to many multipurpose themes, and it includes lazy loading and other performance switches. Whether a given store is fast depends far more on the home page design, image sizes, plugins and hosting than on the theme underneath.
No. Turn on what matches how the store works and test after each change. Lazy loading is nearly always worth having below the first screen. Options that remove scripts or styles can break a plugin that depends on them, so change one, check the cart and checkout, then move to the next.
Yes, or caching from your host. Flatsome's options reduce what a page loads. They do not store the finished page. A page cache is what spares the server from rebuilding the home page and its product queries for every visitor. Use one cache, and keep the theme and the plugin from doing the same job twice.
It rarely does. Visitors tend to see the first slide and scroll on, so the slides after it are loaded for very few people. A single strong banner with one offer appears sooner and gives the visitor one thing to do. If you are unsure, keep one slide and compare orders over a few weeks.
Keep reading
- ServiceSite Speed & Core Web VitalsA slow site loses the customer before they see your offer. We fix what makes pages crawl — heavy images, bloated scripts, blocked rendering — and prove it with numbers.
- ServiceWordPress Speed & OptimizationA slow site loses customers before they read a word. We tune WordPress for speed, stability, and search — measured, not guessed.
- ServiceeCommerce DevelopmentBuild a store that makes buying feel simple. We shape product pages, checkout, payments, tracking, and store workflows so customers can act with confidence.