Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.03MB] [CPU: ▼7.72ms] Passed 4 tests
Server-side resources used by WoPo Minesweeper
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.02 | 35.82 ▼6.65 |
Dashboard /wp-admin | 3.34 ▲0.03 | 46.46 ▼8.94 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 44.83 ▼4.49 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 85.82 ▼10.80 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 35.73 ▲2.07 |
Server storage [IO: ▲0.78MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 30 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WoPo Minesweeper
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,806 ▲44 | 14.67 ▲0.27 | 1.62 ▼0.04 | 45.30 ▲1.48 |
Dashboard /wp-admin | 2,208 ▲30 | 5.62 ▼0.08 | 92.01 ▼22.48 | 41.17 ▼5.64 |
Posts /wp-admin/edit.php | 2,116 ▲19 | 2.03 ▲0.06 | 38.95 ▲0.18 | 35.65 ▲3.21 |
Add New Post /wp-admin/post-new.php | 1,541 ▲15 | 23.37 ▼0.21 | 618.71 ▼11.56 | 45.67 ▼2.20 |
Media Library /wp-admin/upload.php | 1,413 ▲16 | 4.15 ▼0.11 | 96.74 ▼1.83 | 40.84 ▼1.32 |
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
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests 75% 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 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
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wopo-minesweeper/wopo-minesweeper.php:21
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
8 plugin tags: javascript, game, html5, minesweeper, app...
wopo-minesweeper/wopo-minesweeper.php 77% from 13 tests
This is the main PHP file of "WoPo Minesweeper" version 1.2.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Domain Path: The domain path is invalid: folder "/languages" does not exist
- Requires PHP: The required version number did not match the one declared in readme.txt ("5.2.4" instead of "7.1")
- Requires at least: The required version number did not match the one declared in readme.txt ("4.6" instead of "5.2")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected4,399 lines of code in 23 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 15 | 338 | 595 | 3,269 |
CSS | 5 | 52 | 72 | 959 |
PHP | 1 | 23 | 67 | 120 |
HTML | 1 | 0 | 1 | 42 |
Markdown | 1 | 10 | 0 | 9 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.18 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 8 | |
▷ Named functions | 8 | 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
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
html/app/img/sprite.png | 2.33KB | 1.25KB | ▼ 46.53% |