Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.09MB] [CPU: ▼0.88ms] Passed 4 tests
Server-side resources used by Web Push Notifications by PushEngage: WordPress Push Notifications to Supercharge Your Engagement
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 38.24 ▼0.90 |
| Dashboard /wp-admin | 3.42 ▲0.11 | 45.18 ▼3.09 |
| Posts /wp-admin/edit.php | 3.46 ▲0.10 | 46.07 ▲0.34 |
| Add New Post /wp-admin/post-new.php | 5.99 ▲0.10 | 91.84 ▲0.14 |
| Media Library /wp-admin/upload.php | 3.33 ▲0.10 | 37.17 ▲4.46 |
Server storage [IO: ▲19.54MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 131 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| pushengage_settings |
| can_compress_scripts |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Web Push Notifications by PushEngage: WordPress Push Notifications to Supercharge Your Engagement
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,315 ▲554 | 21.78 ▲7.42 | 7.12 ▲5.47 | 29.47 ▼10.30 |
| Dashboard /wp-admin | 2,678 ▲501 | 13.08 ▲7.43 | 350.64 ▲259.57 | 52.12 ▲7.39 |
| Posts /wp-admin/edit.php | 2,288 ▲188 | 2.15 ▲0.14 | 36.11 ▲1.49 | 37.71 ▲2.63 |
| Add New Post /wp-admin/post-new.php | 1,645 ▲119 | 22.97 ▼0.56 | 602.79 ▼91.39 | 55.38 ▲1.29 |
| Media Library /wp-admin/upload.php | 1,588 ▲188 | 4.28 ▼0.04 | 103.90 ▼4.79 | 46.69 ▼0.10 |
| Drip /wp-admin/admin.php?page=pushengage#/automation/drip | 1,167 | 8.99 | 220.50 | 120.62 |
| Audience /wp-admin/admin.php?page=pushengage#/audience/subscribers | 1,442 | 9.60 | 263.32 | 104.83 |
| About Us /wp-admin/admin.php?page=pushengage#/about-us | 1,374 | 9.29 | 219.23 | 87.50 |
| Dashboard /wp-admin/admin.php?page=pushengage# | 1,392 | 8.75 | 194.40 | 110.20 |
| Analytics /wp-admin/admin.php?page=pushengage#/analytics | 1,497 | 9.77 | 258.59 | 89.47 |
| Design /wp-admin/admin.php?page=pushengage#/design | 1,731 | 11.47 | 261.16 | 91.64 |
| Settings /wp-admin/admin.php?page=pushengage#/settings/site-details | 1,263 | 9.36 | 245.05 | 99.03 |
| Campaigns /wp-admin/admin.php?page=pushengage#/campaigns/notifications | 1,219 | 9.43 | 232.22 | 81.87 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 0% 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
Please take a closer look at the following
- 4× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/pushengage/packages/service-worker.js.php
- > /wp-content/plugins/pushengage/views/dashboard-widget.php
- > /wp-content/plugins/pushengage/views/wp-admin-bar-menu.php
- > /wp-content/plugins/pushengage/views/admin.php
- 5× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/pushengage/views/site-not-connected.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/pushengage/languages/pushengage.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/pushengage/views/review-notice.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html__() in wp-content/plugins/pushengage/views/service-worker-error.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_nonce_field() in wp-content/plugins/pushengage/views/post-editor-metabox.php:7
- > 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 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Tags: You are using too many tags: 40 tag instead of maximum 10
pushengage/main.php 92% from 13 tests
The main PHP script in "Web Push Notifications by PushEngage: WordPress Push Notifications to Supercharge Your Engagement" version 4.0.6 is automatically included on every request by WordPress
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("pushengage.php" instead of "main.php")
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
Good job! No executable or dangerous file extensions detected6,607 lines of code in 82 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 46 | 1,950 | 3,683 | 4,678 |
| SVG | 21 | 1 | 0 | 1,575 |
| Markdown | 1 | 127 | 0 | 179 |
| CSS | 3 | 11 | 2 | 87 |
| JavaScript | 9 | 3 | 15 | 46 |
| JSON | 2 | 0 | 0 | 42 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.47 |
| Average class complexity | 19.66 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 147.00 |
| Average method complexity | 3.61 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 25.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 29 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 29 | 100.00% |
| ▷ Final classes | 1 | 3.45% |
| Methods | 201 | |
| ▷ Static methods | 71 | 35.32% |
| ▷ Public methods | 195 | 97.01% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 2.99% |
| Functions | 10 | |
| ▷ Named functions | 1 | 10.00% |
| ▷ Anonymous functions | 9 | 90.00% |
| Constants | 28 | |
| ▷ Global constants | 9 | 32.14% |
| ▷ Class constants | 19 | 67.86% |
| ▷ Public constants | 19 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
18 PNG files occupy 0.51MB with 0.30MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/plugin-om.png | 47.11KB | 13.82KB | ▼ 70.66% |
| assets/img/plugin-seedprod.png | 46.64KB | 15.15KB | ▼ 67.51% |
| assets/img/pe-chrome.png | 3.59KB | 2.17KB | ▼ 39.72% |
| assets/img/phone-preview.png | 12.67KB | 5.05KB | ▼ 60.11% |
| assets/img/plugin-all-in-one-seo.png | 7.42KB | 3.31KB | ▼ 55.43% |