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.05MB] [CPU: ▼7.40ms] Passed 4 tests
An overview of server-side resources used by Lottery Number Supplier
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 41.06 ▼2.18 |
Dashboard /wp-admin | 3.35 ▲0.05 | 45.20 ▼2.68 |
Posts /wp-admin/edit.php | 3.40 ▲0.05 | 41.26 ▼6.75 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.05 | 85.84 ▼17.99 |
Media Library /wp-admin/upload.php | 3.27 ▲0.05 | 35.53 ▼0.86 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 17 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Lottery Number Supplier
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,909 ▲174 | 13.72 ▼0.66 | 5.42 ▲3.35 | 47.06 ▼1.29 |
Dashboard /wp-admin | 2,206 ▲24 | 5.86 ▲0.76 | 94.85 ▼12.69 | 38.13 ▼4.49 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.98 ▼0.01 | 33.56 ▼9.33 | 30.51 ▼5.72 |
Add New Post /wp-admin/post-new.php | 1,533 ▼12 | 23.07 ▲4.82 | 658.36 ▲40.88 | 66.92 ▲15.21 |
Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.20 ▲0.00 | 96.43 ▼8.70 | 42.87 ▼5.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- 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 everything seems fine, this is not an exhaustive test
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
- 5× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/lottery-number-supplier/lib/lns_buildPlayLine.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/lottery-number-supplier/lib/lns_manageLineSupply.php:23
- > PHP Notice
Undefined variable: separator in wp-content/plugins/lottery-number-supplier/lib/lns_pickajax.php on line 12
- > PHP Notice
Undefined variable: freshround in wp-content/plugins/lottery-number-supplier/lib/lns_pickajax.php on line 14
- > PHP Notice
Undefined variable: lineprefix in wp-content/plugins/lottery-number-supplier/lib/lns_pickajax.php on line 13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Tags: You are using too many tags: 11 tag instead of maximum 10
lottery-number-supplier/lottery-number-supplier.php 92% from 13 tests
This is the main PHP file of "Lottery Number Supplier" version 1.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
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 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin671 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 9 | 41 | 138 | 554 |
PO File | 2 | 20 | 20 | 74 |
CSS | 1 | 3 | 7 | 43 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.26 |
Average class complexity | 13.40 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 31.00 |
Average method complexity | 3.70 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 5 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 5 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 23 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 18 | 78.26% |
▷ Protected methods | 5 | 21.74% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 3 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected