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
This plugin's installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▼7.56ms] Passed 4 tests
A check of server-side resources used by Woo In-Stock Notifier
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 37.51 ▲1.74 |
Dashboard /wp-admin | 3.31 ▼0.04 | 44.46 ▼13.02 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 44.95 ▼2.19 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 80.17 ▼14.83 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 31.33 ▼0.18 |
Server storage [IO: ▲0.16MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 23 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Woo In-Stock Notifier
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.27 ▼1.11 | 1.77 ▲0.10 | 43.38 ▼1.06 |
Dashboard /wp-admin | 2,203 ▲15 | 4.84 ▼1.06 | 109.15 ▲9.71 | 42.18 ▼2.62 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.02 | 34.13 ▼5.41 | 33.82 ▲1.96 |
Add New Post /wp-admin/post-new.php | 1,533 ▲9 | 23.27 ▲0.15 | 638.28 ▼5.18 | 53.55 ▼12.42 |
Media Library /wp-admin/upload.php | 1,382 ▼9 | 4.20 ▼0.12 | 96.20 ▼1.18 | 40.61 ▼0.15 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 4× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/woo-in-stock-notifier/instock-init.php on line 35
- > PHP Warning
require_once(ABSPATHwp-admin/includes/plugin.php): failed to open stream: No such file or directory in wp-content/plugins/woo-in-stock-notifier/instock-init.php on line 35
- > PHP Fatal error
Uncaught Error: Call to undefined function do_action() in wp-content/plugins/woo-in-stock-notifier/templates/email/wsn-email-template.php:10
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/plugin.php' (include_path='.:/usr/share/php') in wp-content/plugins/woo-in-stock-notifier/instock-init.php on line 35
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 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
Attributes that require attention:
- Screenshots: Please add descriptions for these screenshots #1, #2, #3 in woo-in-stock-notifier/assets to your readme.txt
woo-in-stock-notifier/instock-init.php 69% from 13 tests
The main file in "Woo In-Stock Notifier" v. 1.0.5 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Requires at least: Required version must match the one declared in readme.txt ("5.2" instead of "2.5.0")
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("woo-in-stock-notifier.php" instead of "instock-init.php")
- 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
- Description: The description should be shorter than 140 characters (currently 151 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Success! There were no dangerous files found in this plugin1,233 lines of code in 15 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 381 | 763 | 1,229 |
CSS | 2 | 4 | 2 | 2 |
JavaScript | 2 | 0 | 2 | 2 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.32 |
Average class complexity | 20.33 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 51.00 |
Average method complexity | 3.97 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 1 | 16.67% |
Methods | 39 | |
▷ Static methods | 3 | 7.69% |
▷ Public methods | 39 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 17 | |
▷ Named functions | 17 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 7 | |
▷ Global constants | 7 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin