Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼1.73MB] [CPU: ▼51.51ms] Passed 4 tests
An overview of server-side resources used by aaLogWP
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.26 ▼1.21 | 5.28 ▼33.88 |
| Dashboard /wp-admin | 2.28 ▼1.03 | 6.95 ▼41.54 |
| Posts /wp-admin/edit.php | 2.28 ▼1.08 | 7.48 ▼39.36 |
| Add New Post /wp-admin/post-new.php | 2.28 ▼3.61 | 6.30 ▼91.27 |
| Media Library /wp-admin/upload.php | 2.28 ▼0.95 | 6.19 ▼30.75 |
| aaLog Options /wp-admin/options-general.php?page=aalogwp_settings | 2.28 | 6.64 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| aalog_cookie |
| widget_recent-posts |
| aalog_filename |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for aaLogWP
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲33 | 13.20 ▼1.11 | 1.72 ▼0.11 | 43.53 ▲3.65 |
| Dashboard /wp-admin | 2,210 ▲19 | 4.84 ▼0.06 | 117.56 ▲17.77 | 40.95 ▼1.01 |
| Posts /wp-admin/edit.php | 2,090 ▲1 | 2.00 ▼0.00 | 33.00 ▼8.67 | 34.07 ▼0.80 |
| Add New Post /wp-admin/post-new.php | 1,522 ▼20 | 23.18 ▲4.78 | 676.30 ▲55.64 | 53.27 ▲4.57 |
| Media Library /wp-admin/upload.php | 1,389 ▲7 | 4.28 ▲0.08 | 99.63 ▲0.27 | 42.70 ▼0.27 |
| aaLog Options /wp-admin/options-general.php?page=aalogwp_settings | 850 | 2.07 | 24.34 | 40.41 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- This plugin did not uninstall without warnings or errors
- > Deprecated in wp-content/plugins/aalogwp/aalog.php+6
Methods with the same name as their class will not be constructors in a future version of PHP; aaLog has a deprecated constructor
- The uninstall procedure has failed, leaving 8 options in the database
- widget_recent-posts
- aalog_cookie
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- aalog_filename
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=aalogwp_settings
- > Deprecated in wp-content/plugins/aalogwp/aalog.php+6
Methods with the same name as their class will not be constructors in a future version of PHP; aaLog has a deprecated constructor
- > GET request to /wp-admin/options-general.php?page=aalogwp_settings
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=aalogwp_settings
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/aalogwp/aalogwp_options_page.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/aalogwp/aalogwp.php:38
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
2 plugin tags: logging, benchmarking
aalogwp/aalogwp.php Passed 13 tests
"aaLogWP" version 1.0.2's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
33 characters long description:
Allows logging data to a logfile.
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
Good job! No executable or dangerous file extensions detected339 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 94 | 35 | 334 |
| Markdown | 1 | 4 | 0 | 5 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.39 |
| Average class complexity | 28.00 |
| ▷ Minimum class complexity | 17.00 |
| ▷ Maximum class complexity | 39.00 |
| Average method complexity | 2.93 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 28 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 28 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 1 | 100.00% |
| ▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin