WordPress Theme Speed Database

1. Why Base Theme Weight Dictates LCP

A theme’s base CSS and JS files execute on every page view. As documented in Google Web Vitals Guidance, lightweight themes like GeneratePress or Kadence give sites a head start toward sub-1.2s LCP.

2. Vanilla JS vs. Legacy jQuery Dependencies

Modern themes use lightweight vanilla JavaScript instead of legacy jQuery. Calculate plugin execution weights in our Plugin Bloat Score Calculator.

3. Compounding Theme & Plugin Bloat

Compare caching plugin speed gains in our WordPress Caching Plugin Comparison Tool.

4. 95+ Scores for Any Theme via Nimbica Static Edge

Nimbica pre-renders WordPress theme HTML into static assets served from 300+ global edge locations, accelerating even heavy multipurpose themes like Divi or Avada to 95+ PageSpeed scores.

5. How to Use This Benchmark Database

The table above is a static comparison dataset covering seven of the most widely deployed WordPress themes, spanning three architectural categories: lightweight (GeneratePress, Kadence, Astra, Blocksy), page-builder-native (Hello Elementor), and multipurpose all-in-one (Divi, Avada). Click any row to highlight it for side-by-side reading. Each row reports four independent measurements taken from a clean starter-content install:

1. Base Weight: total transferred bytes (CSS + JS + fonts + starter images) for the homepage before any content is added.
2. HTTP Requests: the count of separate network round-trips the browser must make to fully paint the page — each one carries DNS, TLS, and queuing overhead.
3. Avg LCP: Largest Contentful Paint measured under Lighthouse's simulated mobile throttling profile (slow 4G, 4x CPU slowdown).
4. PageSpeed Score: the composite 0–100 Lighthouse performance score factoring in LCP, TBT, CLS, and speed index.

Use the category column to compare like with like — a lightweight theme will almost always outscore a multipurpose theme on a stock install, but the gap narrows once both are optimized. The purpose of this database is to set realistic speed expectations before you commit to a theme, not to replace testing your actual finished site with the Core Web Vitals Checker.

6. Worked Example: GeneratePress vs. Divi

Consider two agencies building the same 12-page marketing site. Agency A picks GeneratePress: 32 KB base weight, 7 requests, 0.8s LCP, 99/100 score. Agency B picks Divi: 620 KB base weight, 38 requests, 2.9s LCP, 68/100 score — nearly 20x heavier before a single blog post is written.

That gap comes almost entirely from architecture, not content. GeneratePress ships a single small stylesheet and defers non-critical JS. Divi's visual builder generates a large core stylesheet covering every possible module (sliders, pricing tables, testimonials, counters) whether or not the page uses them, plus a JavaScript bundle for the builder's front-end interactivity. Interpretation: if Agency B's client insists on Divi for its drag-and-drop editing workflow, the fix isn't necessarily switching themes — it's pairing Divi with aggressive unused-CSS removal and static pre-rendering so visitors never pay the builder's runtime cost.

7. Practical Use Cases

• Pre-purchase due diligence: Before buying a premium theme license, compare its category and expected weight class against the benchmarks here to set realistic performance expectations.
• Agency proposal justification: Use the LCP and score columns as evidence when recommending a lightweight theme rebuild to a client currently running a bloated multipurpose theme.
• Migration planning: If you're moving off Avada or Divi, this table helps set a target speed budget for the replacement theme before development starts.
• Client education: Show non-technical stakeholders why "the theme looks the same either way" isn't true from a performance standpoint — the score column makes the trade-off concrete.

8. Common Mistakes & Limitations

• Assuming benchmarks transfer 1:1 to a live site: Adding 40 plugins, custom Google Fonts, and a hero video to GeneratePress can easily push it past a stock Divi install. Theme weight is a starting point, not a guarantee.
• Switching themes without a child theme or staging environment: Migrating between page builder ecosystems (e.g. Divi to Elementor) requires manually rebuilding layouts — content is not portable between builder-specific shortcodes and blocks.
• Ignoring WooCommerce overhead: Adding an online store to any theme introduces WooCommerce's own CSS/JS bundles regardless of base theme weight — check the WordPress Caching Plugin Comparison Tool for store-specific caching strategies.
• Confusing "lightweight" with "feature-poor": GeneratePress, Kadence, and Astra all support full site editing, custom layouts, and hooks — lightness comes from disciplined asset loading, not fewer capabilities.