> ## Documentation Index
> Fetch the complete documentation index at: https://vr-it-services-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> Plugins known to work, plugins that need care, and how to test one safely.

# Plugin compatibility

# Plugin compatibility

What to expect from plugins alongside Vara SaaS, and how to test one safely before you commit.

**The theme is deliberately conservative**

It renders a standard HTML document structure, hooks into WordPress the conventional way, and
adds nothing to the admin. Most plugins that follow WordPress coding standards work without any
special handling.

## Tested and expected to work

| Plugin | Purpose | Notes |
| - | - | - |
| **Elementor** | Page builder | Deep integration — see [Elementor](/integrations/elementor.md) |
| **Contact Form 7** | Forms | Manages the demo contact form |
| **WPForms / Ninja Forms / Formidable** | Forms | Styled consistently by the theme |
| **Yoast SEO / Rank Math / All in One SEO** | SEO | No duplication — see [SEO](/performance/seo.md) |
| **WP Super Cache / LiteSpeed Cache / W3 Total Cache** | Caching | Recommended; the theme caches nothing itself |
| **ShortPixel / Imagify / Smush** | Image optimisation | Recommended; the theme does not compress images |
| **Wordfence / Sucuri / Solid Security** | Security | No overlap |
| **WP Mail SMTP** | Email delivery | Fixes Contact Form 7 delivery on most hosts |
| **Beaver Builder / Divi / Bricks** | Page builders | Recognised — see [Other page builders](/integrations/other-builders.md) |

## Plugins worth adding for specific needs

> **WP Rocket or LiteSpeed Cache**
>
> Caching. On a shared host this is usually the largest speed win available.

> **A megamenu plugin**
>
> The theme's menu handles nested dropdowns but has no megamenu builder. WunderMenu, Smart Megamenu, or Max Mega Menu.

> **SearchWP or Relevanssi**
>
> Better search relevance than WordPress core. The theme's search page is ready for either.

> **WPML or Polylang**
>
> Multilingual sites. The theme ships an Arabic translation and uses the `vara-saas` text domain throughout.

## Plugins that need care

> **Other themes' companion plugins**
>
> Plugins tied to a different theme — Astra Pro, Kadence Blocks, Neve Pro — are designed to extend their own theme's architecture. Installed here, they may register settings for header builders or layouts that do not exist in this theme.

> **Page builder plugins other than Elementor**
>
> More than one builder active at once is asking for trouble. Detection is handled, but CSS conflicts are not guaranteed to resolve cleanly.

> **Aggressive CSS optimisers**
>
> Plugins that minify, inline, and defer CSS can break the theme's conditional asset loading. The main stylesheet already uses a print-media swap; a second optimiser may double-process it.

> **Plugins that replace the login or admin screens**
>
> Login customisation plugins inject markup that can affect the body classes the theme relies on. Check the mobile menu and dark mode toggle after installing one.

## Testing a plugin

Use this procedure before committing any new plugin to a live site.

**1. Back up first**

Files and database. This is the only step that makes the rest safe.

**2. Install and activate the plugin**

Nothing else yet.

**3. Check the homepage visually**

Header, footer, hero. Anything structurally broken shows up immediately.

**4. Check a builder page**

If you use Elementor, open one in the editor and confirm it loads.

**5. Check the blog and a single post**

Cards, byline, table of contents, comments.

**6. Check mobile**

Menu toggle, dropdowns, and dark mode on a real device.

**7. Test in a private window**

Bypasses page cache and shows what a first-time visitor sees.

**8. Measure page weight**

A single plugin should not add hundreds of kilobytes. Re-run PageSpeed Insights.

**Watch page weight, not just appearance**

A plugin that adds 400 KB of JavaScript for a feature you use once a month is a bad trade no
matter how good it looks.

## Debugging a conflict

If something breaks, bisect rather than guess.

**1. Deactivate everything except the theme**

A single step that resolves most conflicts immediately.

**2. Confirm the problem is gone**

If not, the issue is your content or your hosting, not a plugin.

**3. Reactivate plugins in halves**

Turn on half, check, then the other half. Repeat to isolate.

**4. Confirm the culprit**

Deactivate just that one and verify the problem returns when it is active.

See [Plugin conflicts](/troubleshooting/plugin-conflicts.md) for the full procedure.

## Plugin bloat, honestly

A typical Vara SaaS install with the essentials is roughly:

| Component | Approximate weight |
| - | - |
| Theme CSS and JS | \~150 KB uncompressed |
| Elementor CSS | 100–300 KB depending on your pages |
| Contact Form 7 | \~50 KB |
| Cache plugin | Negligible |
| SEO plugin | \~100 KB |
| Image optimisation | \~20 KB |

The theme itself is lean. **Almost everything above the first row is a plugin you chose**, and the fastest performance win available to most sites is removing the ones they do not need.

**Audit quarterly**

Use a plugin like Plugin Check or Query Monitor to list plugins you have not used in months. Most
sites have three or four that can be removed with no consequence.

## Related

> **[Recommended plugins](/introduction/recommended-plugins.md)**
>
> What the theme expects.

> **[Plugin conflicts](/troubleshooting/plugin-conflicts.md)**
>
> The full conflict-resolution procedure.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.