Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼3.69ms] Passed 4 tests
Analyzing server-side resources used by Pusher - Pushing mobile notification with FCM
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 42.33 ▲1.56 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 55.86 ▲0.55 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 45.68 ▼14.47 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 92.79 ▼2.41 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 38.69 ▲1.92 |
Server storage [IO: ▲0.15MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 20 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Pusher - Pushing mobile notification with FCM: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,810 ▲49 | 14.37 ▼0.02 | 1.93 ▼0.17 | 43.67 ▼1.83 |
| Dashboard /wp-admin | 2,204 ▲36 | 5.56 ▼0.07 | 89.98 ▲3.86 | 64.59 ▲19.35 |
| Posts /wp-admin/edit.php | 2,118 ▲18 | 2.04 ▲0.04 | 36.65 ▲0.54 | 36.34 ▼0.34 |
| Add New Post /wp-admin/post-new.php | 1,698 ▲142 | 22.47 ▲4.14 | 719.19 ▲75.48 | 54.09 ▲0.02 |
| Media Library /wp-admin/upload.php | 1,421 ▲24 | 4.20 ▼0.15 | 100.80 ▼0.31 | 73.27 ▲24.94 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
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
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
The following issues need your attention
- 7× PHP files trigger server errors when accessed directly:
- > PHP Warning
include(): Failed opening 'PUSHERFCM_ROOTincludes/Helpers/menus/dashboard.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/pusher-pushing-mobile-notifications-with-fcm/includes/Helpers/content.php on line 3
- > PHP Warning
include(PUSHERFCM_ROOTincludes/Helpers/menus/side.php): failed to open stream: No such file or directory in wp-content/plugins/pusher-pushing-mobile-notifications-with-fcm/includes/Helpers/content.php on line 4
- > PHP Warning
include(): Failed opening 'PUSHERFCM_ROOTincludes/Helpers/menus/side.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/pusher-pushing-mobile-notifications-with-fcm/includes/Helpers/content.php on line 4
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pusher-pushing-mobile-notifications-with-fcm/includes/Helpers/actions.php:3
- > PHP Warning
include(PUSHERFCM_ROOTincludes/Helpers/menus/dashboard.php): failed to open stream: No such file or directory in wp-content/plugins/pusher-pushing-mobile-notifications-with-fcm/includes/Helpers/content.php on line 3
- > PHP Warning
Use of undefined constant PUSHERFCM_ROOT - assumed 'PUSHERFCM_ROOT' (this will throw an Error in a future version of PHP) in wp-content/plugins/pusher-pushing-mobile-notifications-with-fcm/includes/Helpers/content.php on line 3
- > PHP Warning
Use of undefined constant PUSHERFCM_ROOT - assumed 'PUSHERFCM_ROOT' (this will throw an Error in a future version of PHP) in wp-content/plugins/pusher-pushing-mobile-notifications-with-fcm/includes/Helpers/content.php on line 4
- > PHP Warning
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)
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
5 plugin tags: ios, notification, mobile, android, firebase
pusher-pushing-mobile-notifications-with-fcm/pusher.php 85% from 13 tests
The main PHP file in "Pusher - Pushing mobile notification with FCM" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and 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 ("pusher-pushing-mobile-notifications-with-fcm.php" instead of "pusher.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected411 lines of code in 12 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 11 | 41 | 27 | 350 |
| CSS | 1 | 12 | 0 | 61 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 6.50 |
| ▷ Minimum class complexity | 5.00 |
| ▷ Maximum class complexity | 8.00 |
| Average method complexity | 2.22 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 6.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 9 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 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
5 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| includes/assets/smi.png | 1.87KB | 0.70KB | ▼ 62.74% |
| includes/assets/error.png | 1.92KB | 1.10KB | ▼ 43.07% |
| includes/assets/postoff.png | 13.73KB | 10.28KB | ▼ 25.16% |
| includes/assets/check.png | 1.94KB | 0.73KB | ▼ 62.38% |
| includes/assets/post.png | 11.54KB | 5.10KB | ▼ 55.83% |