Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▼2.62ms] Passed 4 tests
A check of server-side resources used by Traffic Jammer
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.58 ▲0.11 | 43.42 ▲5.55 |
Dashboard /wp-admin | 3.42 ▲0.08 | 54.42 ▼6.46 |
Posts /wp-admin/edit.php | 3.54 ▲0.18 | 50.84 ▲2.97 |
Add New Post /wp-admin/post-new.php | 6.00 ▲0.12 | 88.08 ▼12.53 |
Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 39.54 ▲6.42 |
Dashboard /wp-admin/admin.php?page=wp_traffic_jammer | 3.33 | 34.93 |
Reports /wp-admin/admin.php?page=trafficjammer_traffic_logs | 3.33 | 35.41 |
Server storage [IO: ▲0.04MB] [DB: ▲0.01MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 8 new files
Database: 1 new table, 8 new options
New tables |
---|
wp_trafficjammer_traffic |
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
trafficjammer_db_version |
wp_traffic_jammer_options |
widget_recent-posts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Traffic Jammer
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,819 ▲57 | 14.14 ▼0.18 | 1.78 ▲0.01 | 43.09 ▲2.66 |
Dashboard /wp-admin | 2,221 ▲47 | 5.64 ▲0.12 | 94.47 ▲3.80 | 44.30 ▲3.07 |
Posts /wp-admin/edit.php | 2,129 ▲29 | 2.05 ▲0.10 | 37.22 ▼1.45 | 33.53 ▼0.12 |
Add New Post /wp-admin/post-new.php | 1,550 ▲24 | 23.53 ▲0.35 | 633.77 ▼36.89 | 53.46 ▼10.90 |
Media Library /wp-admin/upload.php | 1,426 ▲23 | 4.18 ▼0.01 | 101.11 ▲0.12 | 42.49 ▲0.97 |
Dashboard /wp-admin/admin.php?page=wp_traffic_jammer | 925 | 1.85 | 24.50 | 30.19 |
Reports /wp-admin/admin.php?page=trafficjammer_traffic_logs | 860 | 1.70 | 29.65 | 26.48 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_trafficjammer_traffic
- Zombie WordPress options were found after uninstall: 8 options
- theysaidso_admin_options
- trafficjammer_db_version
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- wp_traffic_jammer_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These server-side errors were triggered
- > GET request to /wp-admin/admin.php?page=trafficjammer_traffic_logs
- > User notice in wp-includes/functions.php+5905
Function wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.)
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
The following issues need your attention
- 4× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/traffic-jammer/partials/traffic-logs.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/traffic-jammer/includes/class-wp-traffic-jammer-cli.php:95
- > PHP Fatal error
Uncaught Error: Call to undefined function sanitize_text_field() in wp-content/plugins/traffic-jammer/traffic-jammer.php:677
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/traffic-jammer/partials/options-page.php:17
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
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
8 plugin tags: block, malicious ip, security, ip, block bots...
traffic-jammer/traffic-jammer.php Passed 13 tests
The primary PHP file in "Traffic Jammer" version 1.2.4 is used by WordPress to initiate all plugin functionality
68 characters long description:
WordPress plugin to block IP and bots that causes malicious traffic.
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
Good job! No executable or dangerous file extensions detected912 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 107 | 293 | 878 |
Markdown | 1 | 14 | 0 | 34 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 4.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 6.00 |
Average method complexity | 1.60 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.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 | 10 | |
▷ Static methods | 1 | 10.00% |
▷ Public methods | 10 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 28 | |
▷ Named functions | 28 | 100.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
No PNG images were found in this plugin