---
title: "Divi Performance Inspector"
url: "https://divitorque.com/features/performance-inspector.md"
canonical: "https://divitorque.com/features/performance-inspector/"
published: "2026-09-12"
modified: "2026-09-12"
author: "Fahim Reza"
---

# Divi Performance Inspector

## Why use the Divi Performance Inspector?

Measures the real asset weight of each page and flags unused modules, oversized bundles and stale feed caches. Nothing here is estimated.

Per-page asset weight is read from what actually loaded on a real visit to your site, not a synthetic test and not a guess based on file sizes alone.

At a glance

4 real checks

Default state

Off until you switch it on

How it measures

Real page loads, not synthetic tests

### Measured, never estimated

Reads what actually loaded

WordPress's own record of scripts and styles actually printed on a real page load, measured on disk.

Off until you want it

Ships disabled. Turn it on in Settings > Quality when you're ready to look.

No live requests

It doesn't fetch pages itself and doesn't add any tracking beyond that.

Gets better with traffic

A low-traffic site's first report may show fewer findings — expected, not a bug.

## Everything the Divi Performance Inspector does

Four checks, each a real measurement from your own site.

**Global stylesheet on non-Torque pages**Divi Torque's Divi 5 stylesheet and script load as one bundle whenever any module is active anywhere on the site — including pages that use no Torque module at all. This check names those pages directly.

**Pages over the internal asset budget**Real, measured Torque JS/CSS weight against a starting internal budget of 150 KB per page — a first line, not a promise, and it will move as we learn more.

**Enabled but unused modules**A module switched on in Module Manager but never placed on any page — its assets stay registered for every page load for no benefit.

**Instagram Feed cache health**Confirms each connected account's media cache is present, so page views serve from cache instead of making a live API call.

What it doesn't promise

No specific performance outcome is ever guaranteed for your site. The Inspector names what it measures on your server — it isn't a synthetic Lighthouse-style score and doesn't claim to be one.

## See the Divi Performance Inspector in action

Three real findings, the kind the report actually surfaces.

BUDGET

/landing-page/ is 214 KB of Torque assets, 64 KB over budget.

UNUSED

Testimonial Slider is enabled but not placed on any page.

SITEWIDE

Torque assets load on 3 pages with no Torque module.

### Turn it on in three steps

STEP 1

Open Settings > Quality in wp-admin.

STEP 2

Switch on the Performance Inspector — it's off by default.

STEP 3

Browse normally for a few days, then open the report.

## Divi Performance Inspector FAQ

**What exactly does it check?**Four things: Torque assets loading on pages with no Torque module, pages over a 150 KB asset budget, modules enabled but never placed, and Instagram Feed cache health.

**Is this a Lighthouse-style score?**No. It measures real Torque asset weight on your own site, not a synthetic overall page score. No performance outcome is guaranteed.

**Does it make outbound requests or slow my site down?**No. It reads WordPress's own record of what already loaded, and measures those files on disk. It doesn't fetch pages itself.

**Why does my first report look thin?**A low-traffic site hasn't seen enough real visits yet to measure every page. That's expected, not a bug.

**Where do I turn it on?**Settings > Quality in wp-admin. It ships off by default.

**Is it free?**No. It's part of Divi Torque Pro, along with every Pro module and extension.