Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼3.19ms] Passed 4 tests
Analyzing server-side resources used by Pushover Notifications for Jetpack
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 38.18 ▼4.25 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 43.38 ▼4.62 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 45.87 ▼3.01 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 93.08 ▼0.88 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 34.95 ▲3.37 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Pushover Notifications for Jetpack: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲60 | 13.60 ▼0.69 | 1.69 ▼0.18 | 43.30 ▼1.02 |
| Dashboard /wp-admin | 2,212 ▲41 | 5.76 ▼0.14 | 103.89 ▲1.34 | 40.98 ▼2.77 |
| Posts /wp-admin/edit.php | 2,097 ▲5 | 2.01 ▲0.04 | 35.21 ▼6.42 | 35.30 ▼2.20 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲5 | 18.43 ▼4.49 | 627.81 ▲45.95 | 58.62 ▲11.48 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.28 ▲0.07 | 96.44 ▼4.70 | 43.23 ▼0.96 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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 | 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 plugin_dir_path() in wp-content/plugins/pushover-notifications-for-jetpack/pushover-notifications-jp-ext.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 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
5 plugin tags: visits, push notifications, stats, jetpack, pushover
pushover-notifications-for-jetpack/pushover-notifications-jp-ext.php 85% from 13 tests
"Pushover Notifications for Jetpack" version 1.0.2.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
- Main file name: The principal plugin file should be the same as the plugin slug ("pushover-notifications-for-jetpack.php" instead of "pushover-notifications-jp-ext.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Success! There were no dangerous files found in this plugin130 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 33 | 61 | 90 |
| PO File | 1 | 7 | 7 | 40 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 11.00 |
| ▷ Maximum class complexity | 11.00 |
| Average method complexity | 1.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 12 | |
| ▷ Static methods | 1 | 8.33% |
| ▷ Public methods | 7 | 58.33% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 41.67% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
PNG images were not found in this plugin