WordPress Theme Speed Comparison

How We Tested Theme Performance

We installed each theme on identical test environments: a fresh WordPress 6.7 installation on a shared hosting plan with PHP 8.3, MariaDB 10.11 and no caching plugins. Each test used the theme’s default demo content with a standard blog layout of 10 posts.

We measured performance using three tools: Google Lighthouse (desktop and mobile), WebPageTest (from a Virginia server on a 4G connection) and Chrome DevTools Network panel. Each theme received five consecutive test runs and we averaged the results to eliminate variance.

Metrics We Measured

Every theme received scores across these performance indicators:

• Largest Contentful Paint (LCP): Time until the largest visible element renders. Google targets under 2.5 seconds.
• Total Blocking Time (TBT): Total time JavaScript blocks the main thread. Target: under 200ms.
• Cumulative Layout Shift (CLS): Visual stability during load. Target: under 0.1.
• Total page weight: Combined size of HTML, CSS, JavaScript, fonts and images transferred.
• HTTP requests: Number of individual files the browser must download.
• Lighthouse Performance Score: Google’s composite score from 0-100.

For deeper context on WordPress performance metrics, read our advanced WordPress performance guide.

Lightweight Theme Tier: The Speed Leaders

GeneratePress

GeneratePress dominates speed benchmarks for good reason. The theme loads under 30KB of CSS and zero JavaScript on a clean install. It ships with no jQuery dependency and uses vanilla CSS for all styling.

Test results: LCP at 0.4s, TBT at 0ms, CLS at 0, total page weight at 28KB, 7 HTTP requests, Lighthouse score of 100. These numbers represent the performance ceiling for WordPress themes. Every other theme competes against this baseline.

The premium version adds a modular Site Library with pre-built templates. Each module loads conditionally, so unused features add zero overhead. GeneratePress achieves this by generating only the CSS rules your site actually uses.

Kadence

Kadence delivers near-identical speed to GeneratePress with a more feature-rich default experience. The free version includes a header/footer builder, starter templates and global color/typography controls that many themes restrict to premium tiers.

Test results: LCP at 0.5s, TBT at 12ms, CLS at 0, total page weight at 45KB, 9 HTTP requests, Lighthouse score of 99. Kadence loads slightly more CSS than GeneratePress because of its built-in header builder, but the difference is negligible in real-world usage.

Blocksy

Blocksy targets users who want visual flexibility without sacrificing speed. It integrates deeply with the WordPress block editor and includes a companion plugin for advanced customization.

Test results: LCP at 0.6s, TBT at 18ms, CLS at 0.01, total page weight at 62KB, 11 HTTP requests, Lighthouse score of 97. Blocksy sits at the top end of the lightweight tier. Its CSS footprint grows faster than GeneratePress or Kadence as you enable features, but remains well within acceptable limits for most sites.

Mid-Weight Theme Tier: Feature vs. Speed Tradeoffs

Astra

Astra markets itself as lightweight, and it once was. The theme has grown significantly since its early days, adding a header builder, mega menus and deeper page builder integrations. Current versions load more assets than the lightweight tier.

Test results: LCP at 0.8s, TBT at 45ms, CLS at 0.02, total page weight at 110KB, 14 HTTP requests, Lighthouse score of 92. Astra still performs well, but the gap between Astra and GeneratePress has widened with each release. The free version loads extra inline CSS for its default styling engine.

OceanWP

OceanWP offers extensive customization through free extensions. This modular approach works in theory but creates performance overhead in practice. Each active extension adds its own stylesheet and sometimes JavaScript.

Test results: LCP at 1.1s, TBT at 80ms, CLS at 0.03, total page weight at 185KB, 19 HTTP requests, Lighthouse score of 85. OceanWP falls firmly into mid-weight territory. With 3-4 extensions active (a common setup), page weight crosses 250KB.

Flavor Comparison: Starter Templates

Starter templates change the equation. A theme’s demo might score 95 on Lighthouse, but the starter template you actually import could score 70 because of additional section blocks, animations and image-heavy layouts. Always test performance after importing your chosen starter template, not before.

Review our WordPress performance optimization guide for techniques to reduce bloat after importing a starter template.

Page Builder Themes: The Heavy Hitters

Divi (Elegant Themes)

Divi bundles its own page builder directly into the theme. This tight integration simplifies the workflow but creates a monolithic CSS and JavaScript payload that loads on every page regardless of which modules you use.

Test results: LCP at 1.8s, TBT at 320ms, CLS at 0.08, total page weight at 680KB, 32 HTTP requests, Lighthouse score of 62. Divi’s performance suffers from its architecture. The theme loads its entire framework upfront rather than splitting code per page. Enabling “Dynamic CSS” and “Critical CSS” in Divi settings improves scores by 10-15 points but does not close the gap with lightweight themes.

Avada

Avada remains the best-selling theme on ThemeForest with over 950,000 sales. Its feature list is enormous: 90+ design elements, a full page builder, mega menus, custom widgets. Every feature has a performance cost.

Test results: LCP at 2.3s, TBT at 450ms, CLS at 0.12, total page weight at 1.1MB, 45 HTTP requests, Lighthouse score of 48. Avada fails Core Web Vitals thresholds on mobile. The theme loads 400KB+ of JavaScript regardless of which features you use. Disabling unused elements through Avada’s Performance Wizard helps but cannot fix the underlying architecture.

Elementor Hello Theme

Hello is Elementor’s companion theme, designed as a blank canvas for the Elementor builder. The theme itself is almost empty, but Elementor Pro adds significant overhead.

Test results (Hello + Elementor Pro): LCP at 1.4s, TBT at 180ms, CLS at 0.04, total page weight at 350KB, 24 HTTP requests, Lighthouse score of 74. Hello theme alone scores 98 on Lighthouse. The gap comes entirely from Elementor’s frontend scripts and stylesheets. Each widget type you use adds incremental CSS.

Bricks Builder

Bricks takes a different approach than traditional page builders. It generates clean semantic HTML and loads only the CSS for components present on each page. No jQuery dependency. No framework-level JavaScript on the frontend.

Test results: LCP at 0.7s, TBT at 25ms, CLS at 0.01, total page weight at 85KB, 12 HTTP requests, Lighthouse score of 96. Bricks proves that page builder functionality and performance are not mutually exclusive. It competes directly with lightweight themes while offering visual editing capabilities.

Speed Comparison Summary Table

This table ranks all tested themes by Lighthouse performance score:

What Causes Theme Bloat

Unused CSS and JavaScript

Multipurpose themes bundle styles for every possible feature. If the theme offers 80 design elements but your page uses 5, the browser still downloads CSS for all 80. This “ship everything” approach is the primary cause of theme bloat.

Lightweight themes solve this with conditional loading. GeneratePress only generates CSS rules for active features. Bricks loads component styles per page. This architectural decision accounts for the 20-40x difference in page weight.

jQuery and Legacy Dependencies

Many themes still depend on jQuery, a 90KB library that WordPress core has been moving away from. jQuery blocks rendering while it loads and executes. Themes that replaced jQuery with vanilla JavaScript gained 100-200ms in load time.

Font Loading Strategy

Google Fonts add 50-200KB per font family depending on the number of weights loaded. Themes that default to system fonts (like GeneratePress) avoid this cost entirely. If you use Google Fonts, limit yourself to two weights (regular and bold) and use font-display: swap to prevent invisible text during load.

Visit our web development services page to learn how we build performance-first WordPress sites.

Choosing the Right Theme for Your Project

Performance-Critical Sites

If Core Web Vitals and page speed rank as top priorities (e-commerce, media sites, high-traffic blogs), choose GeneratePress or Kadence. These themes give you the smallest possible footprint while still offering professional design flexibility through their premium add-ons.

Design-Heavy Sites That Need Speed

If you need visual page building without the typical performance penalty, Bricks is the strongest option. It delivers Elementor-level design control with performance numbers that compete against lightweight themes. Blocksy offers a similar balance through its block editor integration.

Sites Where Speed Is Secondary

Some projects prioritize rapid prototyping or non-technical user editing over raw speed. In these cases, Elementor or Divi might justify their performance cost. Pair them with a CDN, caching plugin and critical CSS generation to mitigate the worst of the bloat.

Even on these sites, avoid Avada. Its performance deficit is too large to recover through optimization alone.

Frequently Asked Questions

Final Recommendation

Theme choice sets your performance ceiling. No amount of caching or CDN configuration overcomes a theme that ships 1MB of unused code. Start with a theme from the lightweight tier and build upward. Your Core Web Vitals, your search rankings and your users will benefit.

Want a professional assessment of your current WordPress theme’s performance? Request a free audit and we will benchmark your site against these standards.