Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▼0.53MB] [CPU: ▼12.51ms] Passed 4 tests
A check of server-side resources used by Remove Gutenberg
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 39.97 ▼5.04 |
| Dashboard /wp-admin | 3.39 ▲0.09 | 47.41 ▼8.02 |
| Posts /wp-admin/edit.php | 3.43 ▲0.07 | 52.25 ▲4.49 |
| Add New Post /wp-admin/post-new.php | 3.55 ▼2.33 | 55.12 ▼41.47 |
| Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 42.21 ▲5.44 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 2 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| reenable-gutenberg |
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Remove Gutenberg
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲3 | 14.35 ▼0.18 | 1.52 ▼1.00 | 41.81 ▼5.69 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.62 ▼0.08 | 92.63 ▲0.16 | 41.47 ▲1.44 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 2.02 ▲0.04 | 38.65 ▲4.54 | 36.36 ▲2.40 |
| Add New Post /wp-admin/post-new.php | 3,094 ▲1,566 | 7.69 ▼15.50 | 210.62 ▼498.45 | 73.33 ▲21.31 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.20 ▼0.07 | 109.72 ▲3.55 | 46.03 ▼1.18 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 7 options
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- reenable-gutenberg
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/restore-classic-editor/rm-gutenberg.php:33
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need your attention:
- Tags: There are too many tags (11 tag instead of maximum 10)
restore-classic-editor/rm-gutenberg.php 69% from 13 tests
"Remove Gutenberg" version 2.2.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Requires PHP: Required version does not match the one declared in readme.txt ("4.9" instead of "7.0")
- Domain Path: The domain path points to an invalid folder, "/languages" does not exist
- Main file name: It is recommended to name the main PHP file as the plugin slug ("restore-classic-editor.php" instead of "rm-gutenberg.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected71 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 13 | 21 | 71 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.23 |
| Average class complexity | 2.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 2.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 2.00 |
| ▷ Maximum method complexity | 2.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 1 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 1 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 8 | |
| ▷ Named functions | 8 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin