WoodMart fix

WoodMart Store Slow? AJAX Filters, Swatches and What to Cut

WoodMart is not slow out of the box. It loads styles only for the elements a page uses and carries its own performance panel. Stores built on it get slow the way attics get full: a demo home page left as imported, a mega menu in every header, swatches on every product card and three plugins repeating what the theme already does.

pagespeed · woodmart home · mobile
Home page, by what loads
Six things loading before the first product
Slow LCP
Slider and hero images84%
Product carousels (5)72%
Mega menu HTML Blocks61%
Grid swatches, hover images55%
Doubled optimization scripts38%
Web fonts (4 families)27%
Illustrative — a demo home page still carrying every sectionmost can go

What you are seeing

  • The home page takes several seconds to settle on a phone
  • Shop and category pages lag behind the rest of the site
  • Filtering products pauses before anything changes
  • PageSpeed flags unused CSS, unused JavaScript and a slow main image
  • A cache plugin went in and the mobile score barely moved

Why it happens on WoodMart

Most common first.

  1. 1

    A demo home page kept as imported

    Prebuilt home pages stack a slider, several product carousels, banners, a brand strip and a blog feed, because their job is to show range. Each carousel is a product query and a script. A working store rarely needs all of them, and almost never above the fold.

  2. 2

    A header that carries a page of its own

    The Header Builder makes it easy to add a mega menu filled with HTML Blocks, a category dropdown, AJAX search, a side cart and separate desktop and mobile layouts. All of it is rendered on every page before the content. A mega menu assembled from builder sections can outweigh the page beneath it.

  3. 3

    Product cards doing too much

    Swatches on the grid, a second image on hover, quick view, wishlist and compare buttons, countdowns and stock bars all multiply by the number of products shown. Swatches cost the most, since the store has to look up each variable product's variations to draw them. Forty products per page turns a small cost into a large one.

  4. 4

    Performance options doubled, or never opened

    The Performance section in Theme Settings controls lazy loading, how scripts and styles load, fonts and preloading. On many stores it is either left at defaults or mirrored by an optimization plugin doing the same things. Images lazy loaded twice delay the main picture, and scripts deferred twice break carousels.

  5. 5

    Filters and uncacheable pages on small hosting

    Cart, checkout and account pages cannot be cached, and every filter click is a fresh database query that counts products per attribute. On a large catalog with hosting sized for a blog, that is where the pauses come from. No theme setting repairs a server that is out of capacity.

How to fix it, in order

Least invasive first. Stop at the step that fixes it.

  1. 1

    Test a category page, not only the home page

    Measure three pages on mobile in PageSpeed Insights, the home page, a category and a product, and keep the reports for comparison. Stores are slow in different places for different reasons, and a single home page score hides that. Make the changes on staging if you can.

  2. 2

    Prune the home page and the HTML Blocks

    Edit the home page and remove sections that do not sell: extra carousels, the second slider, the demo's blog feed. Then open the HTML Blocks screen in the WoodMart menu and delete blocks nothing uses. Keep the first screen simple, with one image that does not wait on a slider script.

  3. 3

    Slim the header

    In WoodMart, Header Builder, open the header in use and review the desktop and mobile layouts. Replace builder-heavy mega menus with plain dropdowns where you can, and drop elements nobody clicks. Whatever stays is paid for on every page view.

  4. 4

    Lighten the product grid

    In the product archive section of Theme Settings, reduce the products per page, show swatches on the grid only if shoppers use them and switch off hover images and buttons you do not need. Disable wishlist or compare entirely if the store has no use for them.

  5. 5

    Go through the Performance section, then undouble it

    Go to WoodMart, Theme Settings, Performance and work through it one option at a time, testing after each. Then open your optimization plugin and turn off anything the theme now handles, lazy loading above all. Deactivate plugins the store does not use: a second page builder, a slider plugin with no sliders.

  6. 6

    Then look at caching and hosting

    Use one page cache with cart, checkout and account excluded. Add a persistent object cache if the host offers one, which helps the pages that cannot be cached. If filter clicks and the dashboard are still slow after that, the server is the limit, and the WordPress speed guide linked below covers that layer.

Keep it from coming back

  • Treat every new home page section as a cost, and remove one when adding one
  • Reread the Performance section after each major theme update, since options change
  • Keep one optimization plugin and write down which features it owns
  • Measure a category page again whenever the catalog or the filters grow

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 demo weight is gone and the settings are right, what remains is the floor: a builder, a theme and WooCommerce assembling each page on request. A Next.js build with a custom CMS serves catalog pages as static files and sends only the code each page needs, which moves that floor a long way. It is the right conversation when speed is costing sales and the tuning has run out.

On WoodMart todayOn Next.js with a custom CMS
What you keep updatedWordPress, the theme, its builder and every bundled plugin, all in stepNothing on a schedule. There is no theme or plugin stack to fall out of step
How a page is servedBuilt from the database on each visit, through the theme and its builderBuilt ahead of time and served as finished files from servers near the visitor
How you edit itA general-purpose builder with every option the theme shipsA CMS built around what your business actually changes: services, prices, photos, posts
What can break itAn update to any one of those parts, or a license that lapsesA 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.

Free · No obligation

Want this fixed on your WoodMart 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

It can, when it is built with restraint and hosted decently, though nothing about a theme makes that automatic. The theme splits its styles by element and offers real performance controls. What weighs stores down is what was added on top: demo sections, header extras, grid features and overlapping plugins.

Both, for different jobs. The theme's settings decide what WoodMart itself loads and how. A cache plugin or host cache stores finished pages so the server does not rebuild them. Trouble starts when both try to lazy load images or defer the same scripts, so assign each feature to one of them.

They add work. To draw swatches on a product card the store has to load that product's variations, and it does so for every variable product in the grid. With a dozen products nobody notices. With several dozen per page on modest hosting it shows, so keep grid swatches only if shoppers really choose by color from the category page.

It fixes the server's share: slow first response, laggy filters, a sluggish cart and dashboard. It does not shrink a heavy page. If a phone still has to download a slider, five carousels and a mega menu, faster hosting delivers the same weight sooner. Do the pruning first, then judge the host.

Keep reading

CallGet a quote