How Classic Editor Affects Your WordPress Speed
How is this scored?
Our Benchmark Methodology
Every speed score on MakeWPFast is based on real performance measurements, not estimates. We install each plugin on a clean WordPress 6.9 setup (PHP 8.3, MariaDB, GeneratePress theme) and measure the difference in three metrics:
TTFB (Time To First Byte) — how many milliseconds the plugin adds to server response time. This is the most important factor (50% of the score) because it directly affects every page load.
Memory usage — how much additional PHP memory the plugin consumes per request (30% of score). High memory usage can cause crashes on shared hosting.
Database queries — how many extra SQL queries the plugin runs per page load (20% of score). More queries mean more database work on every request.
| Grade | What it means |
|---|---|
| A / A- | Negligible impact. Safe to install on any hosting. |
| B+ / B / B- | Light impact. Adds some overhead but manageable on most setups. |
| C+ / C / C- | Moderate impact. May noticeably slow down budget hosting. |
| D+ / D | Heavy impact. Will affect page load times. Consider alternatives. |
| F | Severe impact. Significant resource usage that hurts performance. |
Plugins marked "Not Yet Tested" have not been benchmarked yet. We do not estimate or guess scores — if there is no measured data, there is no grade.
Note: Benchmarks measure a plugin in isolation on a clean install. Real-world impact varies based on your hosting, other plugins, and how the plugin is configured.
Share This Badge
Add this performance badge to your site or README:
Performance Analysis
Classic Editor (classic-editor) is a lightweight plugin that restores the old Classic Editor UI with TinyMCE, meta boxes, and the Edit Post screen. It keeps all plugins that depend on that screen working, so if you use any legacy editor‑based plugins you’ll retain their functionality.
It isn’t for developers who only use Gutenberg and want a clean, modern workflow. The performance impact is minimal — about a two‑query overhead and a few milliseconds of TTFB increase — but you’ll still notice it if you’re monitoring tight page load budgets.
Maintenance Status
Last updated: 2025-12-08. Requires PHP 5.2.4+. Trusted by 9.0M+ active installations.
Benchmark data measured in an isolated Docker environment (WordPress 6.8, PHP 8.3, GeneratePress). See our full methodology.
Find slow plugins on your own site
WP Multitool scans your WordPress site for slow queries, memory hogs, and performance bottlenecks - in one click.
Alternatives to Classic Editor
| Plugin | Speed Score | Active Installs |
|---|---|---|
| Elementor Website Builder – More Than Just a Page Builder | C- | 10M+ |
| Yoast Duplicate Post | A | 4M+ |
| Duplicate Page | A | 3M+ |
Frequently Asked Questions
Does Classic Editor slow down WordPress?
Is Classic Editor still maintained?
What are the best alternatives to Classic Editor?
Plugin reviews, speed optimization guides, and error debugging — straight to your inbox.
No spam. Unsubscribe anytime. We respect your privacy.