Vehica 1.0.108 – Car Dealer & Listing WordPress Theme

I tested Vehica on a boring-but-real dealer site: 1,800 cars, imported from CSV, Elementor Pro already sitting there like a ticking bomb, LiteSpeed Cache on the server, and a client who wanted “something like AutoTrader but cheaper.” Classic.

The good news: Vehica actually works. The listing system is not some half-dead custom post type glued to a pretty homepage. Cars, fields, search forms, compare, favorites, dealer profiles — it’s all usable. I tested the GPL package on multiple local and staging installs, no domain lock, no weird “one site only” nonsense. Unlimited website usage worked fine in my setup.

Activation-wise, don’t expect magic. With a clean GPL build, I installed the theme, added the required Vehica Core plugin, then used the demo importer from the theme panel. No shady key dance was needed for basic operation. For updates, I did it manually: backup, upload the new ZIP, replace the theme, clear object cache, regenerate Elementor CSS. Boring, but safe.

What I actually liked

The search builder is the big win. In Vehica, I could build filters from custom fields without writing a disgusting pile of meta_query code in functions.php. Price, mileage, make, model, fuel type — all manageable from the admin panel instead of hardcoded templates.

Most visual stuff is Elementor-based. Homepage sections, listing cards, archive layout, single vehicle chunks — you can move a lot without touching PHP. That saved me hours, honestly. I hate admitting it, but for dealership sites, this theme is a lifesaver when the client changes “SUV” to “Family Cars” for the fifth time.

The field setup is inside the Vehica Panel, not hidden in some cursed ACF clone. I created extra fields for “Battery health” and “Warranty left” and mapped them into the single listing layout. No drama.

The annoying bits

Now the ugly part. Vehica is heavy. Not “a bit chunky” heavy. I opened DevTools → Network and saw multiple Elementor assets, Google font weights I never asked for, Swiper, icons, theme scripts, and AJAX calls for filters. On mobile, the DOM tree looked like someone built the page using nesting dolls.

The first thing I did was go to Elementor → Settings → Experiments and enable optimized asset loading. Then in Vehica typography settings, I killed extra font weights and forced just 400/600. After that, I used Perfmatters Script Manager to disable unused Elementor widgets on non-listing pages.

One dumb issue: delaying JS broke the listing search. LiteSpeed Cache was delaying jquery-core, and the filter panel started acting drunk. My fix was simple: exclude jquery-core, jquery-migrate, vehica.js, and elementor-frontend from delay. Not elegant, but it stopped the client from texting me screenshots at 11 PM.

Builder vs PHP: where the wall is

Here’s the practical split. In Vehica, you can change listing cards, hero blocks, search forms, single car layout sections, and archive templates through Elementor and the theme panel. Fine.

But once you want to change logic — not layout — welcome back to PHP hell. For example, changing how certain fields are rendered conditionally required digging into theme template parts, not just clicking around. I had to inspect files under /wp-content/themes/vehica/templates/ and override pieces through a child theme.

I also had to hook into wp_enqueue_scripts in functions.php to dequeue a couple of assets on static pages. Something like:

add_action('wp_enqueue_scripts', function () {
    if (is_page('about-us')) {
        wp_dequeue_script('vehica');
    }
}, 99);

Check the actual handles with Query Monitor, because theme updates may rename things. Don’t guess. Guessing is how you lose Saturdays.

Typical breakage I hit

The worst bug came from imported cars. Some CSV rows had empty price values, and Vehica still indexed them for search. The archive filter then showed nonsense ranges. I checked the DB and saw vehicle metadata stored in wp_postmeta, as expected, but the search cache needed rebuilding.

The fix: clean bad _price meta rows, re-save field settings in the panel, then flush cache. I also wrote a tiny WP-CLI cleanup script to normalize mileage and price before import. Dirty? Yes. Effective? Also yes.

Mobile menu was another small circus. It worked, but after minification the hamburger opened once and then died. Console showed an undefined click handler after combined JS loaded. I disabled JS combine for theme scripts and left CSS minification on. Sometimes the “optimization” is just not breaking the site.

Would I use it again?

Yes, but not blindly. Vehica is good for real car dealer projects where the client needs inventory, search, dealer accounts, and listing pages fast. I would not use it for a lightweight brochure site. It’s too much machine for that.

If you know WordPress, Elementor, caching plugins, and you’re not scared of child themes, Vehica is workable. If you expect perfect Core Web Vitals out of the box, pour coffee now. You’ll be in DevTools for a while.

FAQ

Why does the filter stop working after enabling LiteSpeed Cache?

Exclude jquery-core, vehica.js, and elementor-frontend from JS delay. Re-test in DevTools Console after clearing cache.

Can I change the single car page without PHP?

Mostly yes, through Elementor templates and Vehica widgets. Logic changes still need child theme overrides or hooks.

Why is the mobile page so heavy?

Elementor widgets, sliders, icons, and filter markup. Disable unused widgets, reduce font weights, and don’t load map/search blocks everywhere.

Do manual updates wipe custom edits?

Yes, if you edited parent theme files like an animal. Use a child theme, keep overrides separate, and backup before replacing the ZIP.