Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.14MB] [CPU: ▼12.96ms] Passed 4 tests
This is a short check of server-side resources used by MagniPOS - POS Software for WooCommerce
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.00 ▲0.53 | 40.95 ▼5.17 |
Dashboard /wp-admin | 3.83 ▲0.53 | 51.84 ▲3.03 |
Posts /wp-admin/edit.php | 3.88 ▲0.53 | 50.69 ▲5.42 |
Add New Post /wp-admin/post-new.php | 3.73 ▼2.16 | 38.52 ▼55.13 |
Media Library /wp-admin/upload.php | 3.75 ▲0.53 | 40.35 ▲7.26 |
Server storage [IO: ▲0.31MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 50 new files
Database: 1 new table, 7 new options
New tables |
---|
wp_mp_customer_balance |
New WordPress options |
---|
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
recovery_mode_email_last_sent |
theysaidso_admin_options |
widget_recent-comments |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by MagniPOS - POS Software for WooCommerce
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,898 ▲152 | 13.23 ▼1.36 | 1.68 ▼0.20 | 36.33 ▼10.48 |
Dashboard /wp-admin | 2,286 ▲98 | 5.84 ▲0.03 | 98.29 ▼31.50 | 41.95 ▼28.85 |
Posts /wp-admin/edit.php | 2,174 ▲106 | 2.02 ▲0.04 | 39.19 ▲3.14 | 40.57 ▲7.25 |
Add New Post /wp-admin/post-new.php | 53 ▼1,480 | 0.44 ▼22.73 | 0.11 ▼653.43 | 14.85 ▼53.55 |
Media Library /wp-admin/upload.php | 1,469 ▲78 | 4.18 ▼0.03 | 94.26 ▼3.35 | 65.91 ▲24.81 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie tables were found after uninstall: 1 table
- wp_mp_customer_balance
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- recovery_mode_email_last_sent
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× 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/magnipos/admin/templates/magni-pos-admin-dashboard.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need your attention:
- Screenshots: No descriptions were found for these screenshots #1, #10, #11, #12, #13, #14, #2, #3, #4, #5, #6, #7, #8, #9 in magnipos/assets to your readme.txt
magnipos/magni-pos.php 85% from 13 tests
The entry point to "MagniPOS - POS Software for WooCommerce" version 1.0.1 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("magnipos.php" instead of "magni-pos.php")
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
Good job! No executable or dangerous file extensions detected5,600 lines of code in 45 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 41 | 1,164 | 2,612 | 5,054 |
CSS | 1 | 39 | 12 | 283 |
Markdown | 1 | 32 | 0 | 168 |
JSON | 2 | 0 | 0 | 95 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 19.55 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 59.00 |
Average method complexity | 3.60 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 53.00 |
Code structure | ||
---|---|---|
Namespaces | 4 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 31 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 31 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 216 | |
▷ Static methods | 54 | 25.00% |
▷ Public methods | 184 | 85.19% |
▷ Protected methods | 10 | 4.63% |
▷ Private methods | 22 | 10.19% |
Functions | 7 | |
▷ Named functions | 4 | 57.14% |
▷ Anonymous functions | 3 | 42.86% |
Constants | 7 | |
▷ Global constants | 4 | 57.14% |
▷ Class constants | 3 | 42.86% |
▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
PNG images were not found in this plugin