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
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼3.08ms] Passed 4 tests
Analyzing server-side resources used by Plain Logger
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 38.53 ▼3.25 |
Dashboard /wp-admin | 3.35 ▲0.05 | 43.76 ▼0.55 |
Posts /wp-admin/edit.php | 3.46 ▲0.11 | 45.77 ▼3.96 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 90.28 ▼4.56 |
Media Library /wp-admin/upload.php | 3.27 ▲0.05 | 33.70 ▲1.32 |
Plain Logger /wp-admin/tools.php?page=plain_logger | 3.24 | 31.08 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 14 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Plain Logger
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,833 ▲76 | 13.20 ▼1.19 | 1.83 ▼0.23 | 37.62 ▼8.64 |
Dashboard /wp-admin | 2,208 ▲20 | 5.87 ▲1.01 | 104.71 ▼6.18 | 40.48 ▼6.76 |
Posts /wp-admin/edit.php | 2,097 ▲8 | 2.03 ▼0.01 | 40.98 ▲0.20 | 34.18 ▼1.74 |
Add New Post /wp-admin/post-new.php | 1,521 ▼7 | 23.51 ▲5.31 | 567.92 ▼46.33 | 55.30 ▼3.60 |
Media Library /wp-admin/upload.php | 1,393 ▲11 | 4.27 ▲0.09 | 99.43 ▲1.25 | 40.60 ▼3.19 |
Plain Logger /wp-admin/tools.php?page=plain_logger | 817 | 2.05 | 25.50 | 30.21 |
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 were found after uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
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
The following issues need your attention
- 4× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Interface 'Logger' not found in wp-content/plugins/plain-logger/inc/class-log-to-db.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/plain-logger/admin/setting-page.php:2
- > PHP Fatal error
Uncaught Error: Interface 'Logger' not found in wp-content/plugins/plain-logger/inc/class-log-to-file.php:5
- > PHP Fatal error
Uncaught Error: Class 'Log_to_File' not found in wp-content/plugins/plain-logger/class-plain-logger.php:11
- > 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 97% 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:
- Tags: Too many tags (43 tag instead of maximum 10); only the first 5 tags are used in your directory listing
plain-logger/plain-logger.php Passed 13 tests
The primary PHP file in "Plain Logger" version 1.1.2 is used by WordPress to initiate all plugin functionality
102 characters long description:
Easily log any event on your WordPress site to text file. When simple echo and var_dump just won't do.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected266 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 75 | 35 | 212 |
JavaScript | 1 | 5 | 2 | 42 |
CSS | 1 | 2 | 0 | 12 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.15 |
Average class complexity | 2.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 5.00 |
Average method complexity | 1.29 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 1 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 24 | |
▷ Static methods | 1 | 4.17% |
▷ Public methods | 17 | 70.83% |
▷ Protected methods | 1 | 4.17% |
▷ Private methods | 6 | 25.00% |
Functions | 9 | |
▷ Named functions | 9 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 3 | 100.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
There are no PNG files in this plugin