Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼142.96ms] Passed 4 tests
A check of server-side resources used by Notify for WooCommerce
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.85 ▲0.02 | 32.46 ▼4.77 |
Dashboard /wp-admin | 3.08 ▲0.03 | 43.86 ▼4.33 |
Posts /wp-admin/edit.php | 3.17 ▲0.06 | 46.73 ▲7.09 |
Add New Post /wp-admin/post-new.php | 5.45 ▲0.01 | 94.44 ▼550.44 |
Media Library /wp-admin/upload.php | 3.02 ▲0.02 | 31.85 ▼12.31 |
Notify /wp-admin/admin.php?page=notify-for-woocommerce/admin/partials/notify-for-woocommerce-admin-display.php | 3.08 | 34.71 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 26 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for Notify for WooCommerce
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,816 ▲220 | 16.33 ▲0.38 | 14.45 ▲1.65 | 46.01 ▼1.44 |
Dashboard /wp-admin | 2,977 ▲43 | 6.13 ▲0.07 | 146.45 ▼3.87 | 119.99 ▲6.54 |
Posts /wp-admin/edit.php | 2,743 ▲4 | 2.72 ▼0.00 | 65.89 ▼0.69 | 84.53 ▼3.31 |
Add New Post /wp-admin/post-new.php | 1,876 ▲295 | 19.04 ▼1.90 | 382.23 ▼69.90 | 106.19 ▼6.29 |
Media Library /wp-admin/upload.php | 1,811 ▲4 | 5.03 ▲0.02 | 149.57 ▼7.71 | 116.18 ▼1.55 |
Notify /wp-admin/admin.php?page=notify-for-woocommerce/admin/partials/notify-for-woocommerce-admin-display.php | 1,342 | 2.33 | 53.68 | 70.53 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Uninstaller ran successfully
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Almost there! Just fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/notify-for-woocommerce/public/partials/notify-for-woocommerce-public-display.php
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/notify-for-woocommerce/admin/partials/notify-for-woocommerce-admin-display.php:22
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_fields() in wp-content/plugins/notify-for-woocommerce/admin/partials/notify-for-woocommerce-admin-display-templates.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_fields() in wp-content/plugins/notify-for-woocommerce/admin/partials/notify-for-woocommerce-admin-display-settings.php:15
- > 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 Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
8 plugin tags: woocommerce, sms order, order sms, notifications, sms...
notify-for-woocommerce/notify-for-woocommerce.php Passed 13 tests
The entry point to "Notify for WooCommerce" version 1.1 is a PHP file that has certain tags in its header comment area
96 characters long description:
Notify for WooCommerce adds the ability to send SMS notifications for every status of the order.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected497 lines of code in 20 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 14 | 171 | 610 | 443 |
CSS | 2 | 12 | 8 | 41 |
JSON | 1 | 0 | 0 | 6 |
JavaScript | 2 | 4 | 54 | 6 |
SVG | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.12 |
Average class complexity | 3.71 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 17.00 |
Average method complexity | 1.73 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 17.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 26 | |
▷ Static methods | 2 | 7.69% |
▷ Public methods | 21 | 80.77% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 19.23% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 27 | |
▷ Global constants | 27 | 100.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
PNG images were not found in this plugin