Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.28MB] [CPU: ▼5.29ms] Passed 4 tests
Analyzing server-side resources used by WooRule
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.71 ▲0.25 | 24.50 ▼13.95 |
Dashboard /wp-admin | 3.64 ▲0.33 | 45.13 ▼3.06 |
Posts /wp-admin/edit.php | 3.69 ▲0.33 | 46.08 ▲2.52 |
Add New Post /wp-admin/post-new.php | 6.16 ▲0.27 | 84.67 ▼4.49 |
Media Library /wp-admin/upload.php | 3.50 ▲0.27 | 34.40 ▲0.35 |
Server storage [IO: ▲0.13MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 46 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for WooRule
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,503 ▼258 | 14.14 ▲0.00 | 0.45 ▼1.64 | 16.39 ▼22.24 |
Dashboard /wp-admin | 2,244 ▲64 | 5.69 ▲0.08 | 80.87 ▼5.36 | 74.83 ▲32.85 |
Posts /wp-admin/edit.php | 2,155 ▲55 | 2.00 ▲0.04 | 34.97 ▼2.25 | 33.56 ▼3.72 |
Add New Post /wp-admin/post-new.php | 1,575 ▲49 | 22.95 ▼0.14 | 751.04 ▲92.66 | 79.75 ▲26.15 |
Media Library /wp-admin/upload.php | 1,452 ▲52 | 4.13 ▼0.07 | 92.56 ▼13.79 | 84.63 ▲37.87 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking 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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 8× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
require_once(): Failed opening required 'WOORULE_PATHinc/trait-woorule-logging.php' (include_path='.:/usr/share/php') in wp-content/plugins/woorule/inc/class-woorule.php on line 8
- > PHP Warning
Use of undefined constant WOORULE_PATH - assumed 'WOORULE_PATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/woorule/inc/class-woorule.php on line 8
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/woorule/inc/class-woorule-alert.php:25
- > PHP Fatal error
Trait 'Woorule_Logging' not found in wp-content/plugins/woorule/inc/class-rulemailer-api.php on line 21
- > PHP Fatal error
Trait 'Woorule_Logging' not found in wp-content/plugins/woorule/inc/class-productalert-api.php on line 22
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/woorule/woorule.php:24
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/woorule/inc/class-woorule-alert-shortcode.php:20
- > PHP Warning
require_once(WOORULE_PATHinc/trait-woorule-logging.php): failed to open stream: No such file or directory in wp-content/plugins/woorule/inc/class-woorule.php on line 8
- > 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
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need your attention:
- Requires php: Version format is invalid
woorule/woorule.php 92% from 13 tests
The primary PHP file in "WooRule" version 3.0.4 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("5.0.0" instead of "3.0.0")
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 plugin2,298 lines of code in 37 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 21 | 344 | 902 | 2,002 |
JavaScript | 4 | 25 | 4 | 107 |
Sass | 3 | 11 | 0 | 58 |
CSS | 6 | 14 | 3 | 45 |
SVG | 1 | 0 | 0 | 43 |
XML | 1 | 0 | 0 | 27 |
Markdown | 1 | 8 | 0 | 16 |
PHP code Passed 2 tests
A brief analysis 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.33 |
Average class complexity | 12.43 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 25.00 |
Average method complexity | 2.84 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 1 | |
Classes | 13 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 13 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 87 | |
▷ Static methods | 24 | 27.59% |
▷ Public methods | 54 | 62.07% |
▷ Protected methods | 23 | 26.44% |
▷ Private methods | 10 | 11.49% |
Functions | 1 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 1 | 100.00% |
Constants | 7 | |
▷ Global constants | 3 | 42.86% |
▷ Class constants | 4 | 57.14% |
▷ Public constants | 4 | 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
1 PNG file occupies 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/logo.png | 13.21KB | 6.03KB | ▼ 54.32% |