Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▼8.29ms] Passed 4 tests
Analyzing server-side resources used by Notify Engage Pixel Handling
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 35.03 ▼2.45 |
| Dashboard /wp-admin | 3.33 ▲0.02 | 43.56 ▼2.42 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 43.02 ▼5.77 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 80.69 ▼22.50 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 34.06 ▼1.51 |
| Notify Engage /wp-admin/options-general.php?page=notify-engage | 3.22 | 29.93 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Notify Engage Pixel Handling
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲58 | 14.48 ▲0.31 | 1.69 ▼0.03 | 44.75 ▲4.69 |
| Dashboard /wp-admin | 2,213 ▲25 | 5.85 ▲0.95 | 102.64 ▼10.80 | 40.77 ▲2.32 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.05 ▲0.05 | 36.99 ▼5.39 | 38.18 ▲2.80 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲31 | 18.39 ▲0.91 | 629.28 ▲23.37 | 52.94 ▼1.93 |
| Media Library /wp-admin/upload.php | 1,386 ▼2 | 4.16 ▼0.05 | 94.41 ▼7.96 | 42.20 ▼2.75 |
| Notify Engage /wp-admin/options-general.php?page=notify-engage | 810 | 2.06 | 23.61 | 28.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% 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 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/notify-engage/views/settings.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/notify-engage/notify-engage.php:26
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need to be fixed:
- Screenshots: Please a description for screenshot #1 in notify-engage/assets to your readme.txt
notify-engage/notify-engage.php 77% from 13 tests
The entry point to "Notify Engage Pixel Handling" version 0.1 is a PHP file that has certain tags in its header comment area
Please take the time to fix the following:
- Description: Please don't use more than 140 characters for the plugin description (currently 194 characters long)
- Domain Path: The domain path should be prefixed with a forward slash character ("/languages")
- Domain Path: Use only dashes and lowercase characters for the domain path ("languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected110 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 22 | 54 | 110 |
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.33 |
| Average class complexity | 12.00 |
| ▷ Minimum class complexity | 12.00 |
| ▷ Maximum class complexity | 12.00 |
| Average method complexity | 2.57 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.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 | 7 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected