BeautySpot 3.5.19 – Beauty Salon WordPress Theme

I’ve worked with BeautySpot on a small salon site, and yeah, it’s one of those themes that feels like it was built by someone who actually saw a booking website before. Not perfect. Not “clean code heaven.” But usable, and that already puts it above half the ThemeForest zoo.

The first good surprise: BeautySpot doesn’t try to reinvent WordPress entirely. Most visual stuff lives in Appearance -> Customize, especially colors, typography, header layout, footer blocks, and sidebar behavior. I like that. I absolutely hate themes that hide basic colors inside some cursed “Mega Panel Pro Ultimate” screen.

The annoying part? Some markup choices are baked deep into PHP templates, so if your client suddenly wants the service archive to behave differently, welcome back to the trenches.

What I could change without touching PHP

For normal client work, BeautySpot is friendly enough. Logo, main colors, fonts, header image, footer columns, and homepage section settings are handled through the Customizer. The salon-style pages — services, galleries, testimonials — are mostly managed through custom post types added by the theme toolkit plugin.

On my setup, the useful path was:

Appearance -> Customize -> Theme Options

That’s where I handled header style, primary accent color, typography, breadcrumbs, and some layout defaults. No drama there.

Widgets are still important in BeautySpot, especially for footer/contact blocks. I had to explain to the client that “the thing at the bottom” was not a page builder section but sitting in:

Appearance -> Widgets -> Footer Widgets

Old-school, but honestly, predictable.

Where BeautySpot made me swear a bit

The homepage looked fine until I opened Chrome DevTools and checked the Network tab. BeautySpot was loading multiple font weights I didn’t need, plus a couple of theme CSS files that were not huge, but still annoying on mobile 4G.

I saw font weights like 300, 400, 600, 700 being pulled when the design only used 400 and 700. I fixed it by overriding the Google Fonts enqueue in functions.php of the child theme. Not elegant, but I was not going to ship a salon website that downloads font weights like it’s preparing for a typography exam.

The bigger irritation was the service listing markup. The card structure is mostly controlled in:

template-parts/service.php
archive-lsvr_service.php

Changing the order from image-title-excerpt-button to title-image-price-button was not possible in the Customizer. I had to copy the template into the child theme and patch it there. Classic WordPress Tuesday.

Performance notes from DevTools

With BeautySpot, the DOM tree was okay, not Elementor-level ridiculous. That was a relief. I opened DevTools -> Lighthouse and the main complaints were render-blocking CSS, fonts, and image sizes from the demo import.

The theme scripts were not insane. I remember seeing handles like:

beautyspot-main
lsvr-frontend
jquery-core

When I used Autoptimize, combining JS worked, but delaying jQuery broke the mobile menu toggle. The console threw a lazy little $ is not defined error. My fix was boring but effective: exclude jquery-core and beautyspot-main.js from JS delay, but still minify CSS.

In WP Rocket, I used:

File Optimization -> Delay JavaScript execution -> Excluded JavaScript Files

and added:

jquery.min.js
beautyspot-main
lsvr-frontend

After that, mobile navigation stopped acting drunk.

Demo import, GPL use, and activation stuff

I tested BeautySpot as a GPL package, and it worked normally with unlimited website usage. No weird locked frontend, no “one domain only” tantrum, no missing admin screens.

Activation is not some magical SaaS ritual. You install the theme, install the required companion plugins from the admin notice, then import demo content. On my install, demo import was under the standard importer/plugin flow, not some over-engineered cloud dashboard.

For manual updates, I just replaced the theme folder through FTP or uploaded the new ZIP after switching briefly to another theme. Keep the child theme separate, obviously, unless you enjoy losing edits like a rookie.

No license key was needed for the site to run. If you expect automatic vendor updates from the official dashboard, that’s a different story. But for normal manual maintenance, BeautySpot behaved fine.

What is hardcoded and needs actual developer hands

The Customizer gets you 70% there. The rest is PHP mud wrestling.

Stuff I had to touch:

header.php — for custom tracking placement and header wrapper edits
footer.php — for removing theme credit structure cleanly
archive-lsvr_service.php — service archive layout
single-lsvr_service.php — service detail structure
template-parts/ — small repeated blocks that control cards and snippets

I also had to inspect wp_options because some Customizer settings were stored as theme_mods_beautyspot. Useful when migrating staging to production and wondering why colors suddenly went back to grandma-pink.

My actual verdict

I don’t love BeautySpot, but I respect it. That’s rare. It’s not bloated beyond repair, it doesn’t force a monster builder, and the salon features make sense out of the box.

Would I use BeautySpot for a huge WooCommerce beauty marketplace? Nope. Would I use it for a hairdresser, spa, massage studio, nail salon, or local cosmetic clinic? Yeah, absolutely — after creating a child theme and cleaning the font/script mess.

It’s one of those themes where the client sees a pretty site, and I only lose half a day fighting templates. That counts as a win.

FAQ

Why does the mobile menu break after optimization?
Because delayed jQuery kills the theme toggle script. Exclude jquery-core, beautyspot-main, and lsvr-frontend from JS delay.

Can I rebuild service cards in the Customizer?
No. Basic style, yes. Markup order needs edits in archive-lsvr_service.php or template-parts/service.php.

Where are the theme settings stored?
Mostly in wp_options under theme_mods_beautyspot. Handy during migrations.

Is BeautySpot okay for multiple sites?
The GPL package I tested worked with unlimited website usage. Manual updates are just ZIP/FTP replacement, no activation drama.