Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼4.26ms] Passed 4 tests
An overview of server-side resources used by Historian
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 38.43 ▼3.96 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 43.96 ▼6.70 |
| Posts /wp-admin/edit.php | 3.37 ▲0.02 | 51.74 ▲6.20 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 87.70 ▼8.51 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 36.90 ▲2.15 |
Server storage [IO: ▲1.25MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 19 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| theysaidso_admin_options |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| widget_historian_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Historian
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,836 ▲79 | 13.26 ▼1.11 | 4.32 ▲2.18 | 40.63 ▼4.69 |
| Dashboard /wp-admin | 2,239 ▲51 | 4.85 ▼0.06 | 109.70 ▼9.84 | 39.30 ▼6.20 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.02 ▲0.01 | 41.09 ▲5.94 | 34.07 ▲0.31 |
| Add New Post /wp-admin/post-new.php | 6,587 ▲5,073 | 29.17 ▲11.50 | 900.23 ▲264.17 | 64.18 ▲12.06 |
| Media Library /wp-admin/upload.php | 1,385 ▼6 | 4.19 ▼0.02 | 96.96 ▲1.03 | 42.55 ▲0.04 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- Zombie WordPress options were found after uninstall: 7 options
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- widget_historian_widget
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/retroposts/classes/HistorianWidget-class.php:5
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/retroposts/classes/HistorianWidget-class.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
3 plugin tags: post history, block, dashboard widget
retroposts/historian.php 85% from 13 tests
This is the main PHP file of "Historian" version 2.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("retroposts.php" instead of "historian.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
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 plugin31,699 lines of code in 17 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 4 | 0 | 0 | 31,496 |
| PHP | 4 | 34 | 27 | 107 |
| JavaScript | 5 | 18 | 46 | 75 |
| Sass | 2 | 2 | 0 | 19 |
| CSS | 2 | 0 | 0 | 2 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| Average class complexity | 4.00 |
| ▷ Minimum class complexity | 4.00 |
| ▷ Maximum class complexity | 4.00 |
| Average method complexity | 1.71 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 8 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 6 | 75.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 25.00% |
| Functions | 6 | |
| ▷ Named functions | 4 | 66.67% |
| ▷ Anonymous functions | 2 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.06MB with 0.04MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 57.18KB | 19.25KB | ▼ 66.34% |