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.52MB] [CPU: ▼13.14ms] Passed 4 tests
This is a short check of server-side resources used by Restore Classic Widgets and Classic Post Editor
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.09 | 39.80 ▼0.44 |
Dashboard /wp-admin | 3.39 ▲0.09 | 49.19 ▼4.98 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 48.95 ▼3.25 |
Add New Post /wp-admin/post-new.php | 3.54 ▼2.35 | 60.38 ▼43.90 |
Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 39.18 ▲1.68 |
Classic Editor And Widget Settings /wp-admin/options-general.php?page=classic-widgets-and-post-editor-options | 3.28 | 33.94 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 22 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
classic_widgets_and_post_editor_options |
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Restore Classic Widgets and Classic Post Editor
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲32 | 14.29 ▼0.08 | 1.78 ▼0.06 | 43.13 ▼3.36 |
Dashboard /wp-admin | 2,193 ▲16 | 5.55 ▲0.02 | 86.66 ▼6.41 | 40.79 ▼2.18 |
Posts /wp-admin/edit.php | 2,104 ▲1 | 1.94 ▼0.04 | 39.40 ▲0.75 | 32.23 ▼10.33 |
Add New Post /wp-admin/post-new.php | 3,104 ▲1,578 | 7.83 ▼16.03 | 181.24 ▼499.22 | 69.47 ▲11.49 |
Media Library /wp-admin/upload.php | 1,398 ▼5 | 4.20 ▼0.02 | 96.09 ▼1.84 | 43.67 ▼4.39 |
Classic Editor And Widget Settings /wp-admin/options-general.php?page=classic-widgets-and-post-editor-options | 834 | 2.03 | 27.71 | 27.65 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
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 90% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Please fix the following attributes:
- Screenshots: A description for screenshot #1 is required in restore-classic-widgets-and-classic-post-editor/assets to your readme.txt
restore-classic-widgets-and-classic-post-editor/restore_classic_widgets_and_classic_post_editor.php 85% from 13 tests
"Restore Classic Widgets and Classic Post Editor" version 0.1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("restore-classic-widgets-and-classic-post-editor.php" instead of "restore_classic_widgets_and_classic_post_editor.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 157 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Success! There were no dangerous files found in this plugin785 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 233 | 175 | 686 |
PO File | 2 | 20 | 20 | 81 |
JSON | 2 | 0 | 0 | 18 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.48 |
Average class complexity | 15.83 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 47.00 |
Average method complexity | 2.98 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 46 | |
▷ Static methods | 20 | 43.48% |
▷ Public methods | 44 | 95.65% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 4.35% |
Functions | 3 | |
▷ Named functions | 2 | 66.67% |
▷ Anonymous functions | 1 | 33.33% |
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
PNG files should be compressed to save space and minimize bandwidth usage
There are no PNG files in this plugin