Diza 1.3.18 – Pharmacy Store Elementor WooCommerce Theme

I tested Diza Theme on a boring local WooCommerce stack: PHP 8.2, WordPress 6.x, Elementor, Elementor Pro, WooCommerce, WP Rocket, and a pile of sample products. Diza installed fine, no drama there. The demo import worked through the theme’s importer, but I still made a database snapshot first because I’ve been burned by “one-click demo” buttons more times than I care to admit.

The pharmacy demo looks decent out of the box. Clean cards, usable product grids, nice category blocks, and the header actually makes sense for a store with search-heavy traffic. But then I opened DevTools and saw the usual theme-shop crime scene: too many CSS files, multiple font weights, and Elementor widgets dragging half the circus onto pages that only need a product loop.

What I Could Change Without Swearing

Most visual stuff in Diza is thankfully editable from Appearance -> Customize and the theme panel. Header layout, logo, colors, some typography, product archive behavior — all manageable without touching code. Elementor handles the homepage sections, banners, icon boxes, and category promos.

The useful bits are in the builder: homepage hero, pharmacy category blocks, “featured products”, and promotional strips. I swapped the demo blue/green palette from the Customizer and adjusted product card spacing in Elementor. No need to fight CSS for basic layout tweaks, which is honestly a lifesaver when the client is already asking why the “vitamin banner feels sad”.

WooCommerce settings are normal: product catalog in Appearance -> Customize -> WooCommerce, checkout fields via hooks or a plugin, and product image sizes through WooCommerce -> Settings -> Products. Nothing magical, but nothing broken either.

What Is Hardcoded Because Of Course It Is

The annoying parts start when you want to change structural markup. Some header and product template pieces are not “real Elementor freedom”; they’re theme templates dressed up as flexibility.

I had to look into files like:

• header.php
• footer.php
• woocommerce/content-product.php
• woocommerce/single-product/product-image.php
• inc/classes/class-theme-setup.php
• inc/vendors/woocommerce/functions.php

On my setup, changing the product badge logic properly meant overriding WooCommerce templates in a child theme, not hacking the parent like an animal. I hooked into woocommerce_before_shop_loop_item_title and removed the theme’s badge output, then added my own stock/discount label. Cleaner, less future pain.

Also, some strings were not where I expected. A few labels were buried in theme functions instead of template files. I used grep -R "Quick View" wp-content/themes/diza/ because clicking around the admin like a confused raccoon was getting me nowhere.

Performance: Not Awful, Not Innocent

Diza is not the heaviest WooCommerce theme I’ve touched, but it still has that Elementor + shop theme bloat. In Chrome DevTools, the Network tab showed several font weights loading even after I picked only two in the typography panel. I killed the extras by disabling Google Fonts in Elementor and serving local fonts from the child theme.

In functions.php, I dequeued a couple of unused styles on non-shop pages:

add_action('wp_enqueue_scripts', function () {
    if (!is_woocommerce() && !is_cart() && !is_checkout()) {
        wp_dequeue_style('diza-woocommerce');
        wp_dequeue_script('diza-quick-view');
    }
}, 99);

Do not blindly copy that without checking handles on your install. I confirmed mine from Query Monitor and the page source. Theme handles can change between builds, because apparently stability is a luxury.

The JS Bug That Made Me Mutter Into My Coffee

Here’s the predictable WooCommerce headache: if you enable aggressive JS delay in WP Rocket or LiteSpeed Cache, product variations can break. On one test product, the dropdown changed but price and stock text didn’t update.

Console was clean, which made it more annoying. The fix was excluding these from delay/minify:

• jquery-core
• jquery-migrate
• wc-add-to-cart-variation.js
• wc-single-product
• diza-woocommerce

In WP Rocket, I added them under File Optimization -> Delay JavaScript execution -> Excluded JavaScript Files. After that, variations behaved again. I absolutely hate that this is still a thing in 2026, but here we are.

GPL, Activation, Demo Import, Updates

I tested a GPL-licensed copy of Diza on multiple local/staging installs. The theme itself worked without domain limits, so yes, practical Unlimited Website Usage for the WordPress theme code. No weird lock screen, no “enter key or die” nonsense for basic usage.

That said, don’t confuse GPL usage with vendor services. Marketplace auto-updates, support, and some bundled plugin updates may still require a valid purchase/license. That’s normal.

Demo import worked from the included importer. If it fails, I’d skip the drama and manually import XML from Tools -> Import -> WordPress, then assign menus in Appearance -> Menus and set the homepage in Settings -> Reading. Manual updates are the usual: upload the new theme ZIP or replace the parent theme over SFTP, while keeping all edits in a child theme. Never patch parent files unless you enjoy losing weekends.

Database Mess I Noticed

Like most Elementor-heavy themes, Diza leaves plenty of layout data in wp_postmeta, especially _elementor_data, _elementor_css, and _elementor_page_settings. After importing demos, I cleaned unused pages, trashed demo products, then ran a search for orphaned Elementor templates.

If the site feels sluggish in admin after import, check wp_options for bloated transients and autoloaded junk. I used WP-CLI:

wp option list --autoload=on --format=table
wp transient delete --all

Not glamorous, but it beats blaming hosting for everything.

FAQ

Why does the mobile menu sometimes freeze after optimization?

Because delayed jQuery breaks the theme menu script. Exclude jquery-core and the main Diza navigation JS from delay.

Can I rebuild the header fully in Elementor?

Partly. Basic layout yes, deep markup no. For serious header surgery, use a child theme and edit/override header.php.

Does Diza work for non-pharmacy stores?

Yes. The pharmacy skin is just styling and demo content. WooCommerce logic is generic enough for cosmetics, supplements, or medical equipment.

Why is the shop page DOM so heavy?

Elementor widgets plus theme wrappers plus WooCommerce loops. Reduce product card extras, disable quick view if unused, and avoid stacking three carousel widgets above the fold.