Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.33MB] [CPU: ▼0.51ms] Passed 4 tests
Server-side resources used by magayo Lottery Results
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.79 ▲0.33 | 44.85 ▲5.69 |
| Dashboard /wp-admin | 3.63 ▲0.32 | 48.08 ▲1.15 |
| Posts /wp-admin/edit.php | 3.74 ▲0.38 | 52.34 ▲6.31 |
| Add New Post /wp-admin/post-new.php | 6.22 ▲0.34 | 83.14 ▼9.36 |
| Media Library /wp-admin/upload.php | 3.55 ▲0.32 | 37.44 ▲0.49 |
| magayo Lottery Results /wp-admin/options-general.php?page=magayo-lottery-results | 3.62 | 41.81 |
Server storage [IO: ▲4.02MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
These are issues you should consider
- You have illegally modified 2 files (0.00KB) outside of "wp-content/plugins/magayo-lottery-results/" and "wp-content/uploads/"
- (new file) "wp-content/plugins/magayo-lottery-results/assets/icon-256\303\227256.png"
- (new file) "wp-content/plugins/magayo-lottery-results/assets/banner-1544\303\227500.jpg"
Filesystem: 863 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| magayo-lottery-results |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| widget_magayo_lottery_results_widget |
| db_upgraded |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by magayo Lottery Results
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,891 ▲145 | 13.57 ▼0.80 | 5.89 ▲3.79 | 41.93 ▼4.36 |
| Dashboard /wp-admin | 2,211 ▲23 | 5.88 ▲0.07 | 105.77 ▼4.18 | 37.73 ▼4.91 |
| Posts /wp-admin/edit.php | 2,100 ▲11 | 2.04 ▲0.01 | 40.02 ▲4.19 | 34.86 ▲0.67 |
| Add New Post /wp-admin/post-new.php | 1,521 ▲2 | 17.39 ▼5.93 | 682.84 ▼54.80 | 62.22 ▲2.97 |
| Media Library /wp-admin/upload.php | 1,396 ▲5 | 4.18 ▼0.03 | 96.63 ▼3.16 | 42.10 ▼3.78 |
| magayo Lottery Results /wp-admin/options-general.php?page=magayo-lottery-results | 1,545 | 1.74 | 26.94 | 26.97 |
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
Please fix the following items
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_magayo_lottery_results_widget
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/magayo-lottery-results/public/partials/magayo-lottery-results-public-display.php
- 6× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/magayo-lottery-results/admin/partials/magayo-lottery-results-display-settings.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/magayo-lottery-results/admin/partials/magayo-lottery-results-getting-started.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/magayo-lottery-results/includes/magayo-lottery-results-widget-admin-display.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/magayo-lottery-results/admin/partials/magayo-lottery-results-admin-display.php:18
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/magayo-lottery-results/includes/class-magayo-lottery-results-widget.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/magayo-lottery-results/admin/partials/magayo-lottery-results-games-settings.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== magayo-lottery-results ===)
magayo-lottery-results/magayo-lottery-results.php Passed 13 tests
The primary PHP file in "magayo Lottery Results" version 2.0.9 is used by WordPress to initiate all plugin functionality
72 characters long description:
Display lottery results and jackpots for lottery games across the world.
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin2,626 lines of code in 22 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 17 | 578 | 724 | 2,442 |
| JavaScript | 3 | 42 | 50 | 163 |
| CSS | 2 | 5 | 10 | 21 |
PHP code 50% from 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Please fix the following
- Cyclomatic complexity of methods has to be reduced to less than 100 (currently 110)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.40 |
| Average class complexity | 51.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 398.00 |
| Average method complexity | 8.09 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 110.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 57 | |
| ▷ Static methods | 2 | 3.51% |
| ▷ Public methods | 37 | 64.91% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 20 | 35.09% |
| 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 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
818 PNG files occupy 3.67MB with 1.41MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/images/red/ball_red85.png | 4.36KB | 2.81KB | ▼ 35.44% |
| assets/images/purple/ball_purple59.png | 4.97KB | 2.86KB | ▼ 42.44% |
| assets/images/orange/ball_orange21.png | 4.59KB | 2.75KB | ▼ 40.17% |
| assets/images/purple/ball_purple68.png | 4.97KB | 2.98KB | ▼ 40.03% |
| assets/images/red/ball_red43.png | 4.25KB | 2.83KB | ▼ 33.56% |