Benchmarks
Plugin footprint 65% 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: ▼1.12MB] [CPU: ▼45.62ms] Passed 4 tests
This is a short check of server-side resources used by Debug Log Parser
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.85 ▼0.61 | 15.28 ▼26.49 |
Dashboard /wp-admin | 2.91 ▼0.44 | 24.70 ▼37.77 |
Posts /wp-admin/edit.php | 2.91 ▼0.45 | 20.36 ▼30.49 |
Add New Post /wp-admin/post-new.php | 2.91 ▼2.98 | 19.20 ▼87.72 |
Media Library /wp-admin/upload.php | 2.91 ▼0.32 | 19.23 ▼16.18 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] 67% from 3 tests
A short overview of filesystem and database impact
These are issues you should consider
- The plugin illegally modified 1 file (4.44KB) outside of "wp-content/plugins/debug-log-parser/" and "wp-content/uploads/"
- (modified) wp-config.php
Filesystem: 10 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
Debug Log Parser: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,842 ▲81 | 14.27 ▼0.08 | 1.72 ▲0.03 | 40.84 ▲1.64 |
Dashboard /wp-admin | 2,248 ▲67 | 5.60 ▼0.11 | 95.22 ▼5.86 | 40.79 ▲2.23 |
Posts /wp-admin/edit.php | 2,116 ▲16 | 2.03 ▲0.07 | 33.07 ▼6.04 | 34.12 ▼3.28 |
Add New Post /wp-admin/post-new.php | 1,544 ▲16 | 23.32 ▲0.17 | 662.57 ▼44.07 | 67.27 ▲11.42 |
Media Library /wp-admin/upload.php | 1,419 ▲22 | 4.18 ▼0.05 | 99.07 ▼7.82 | 45.91 ▼1.48 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- This plugin cannot be uninstalled
- > Notice in wp-config.php+132
Constant WP_DEBUG already defined
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/debug-log-parser/debug-log-parser.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% 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
These attributes need your attention:
- Donate link: Invalid URI ("")
debug-log-parser/debug-log-parser.php 92% from 13 tests
The main file in "Debug Log Parser" v. 1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin463 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 99 | 144 | 404 |
PO File | 1 | 20 | 42 | 59 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 6.67 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 15.00 |
Average method complexity | 2.36 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 25 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 25 | 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 | 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