Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼9.19ms] Passed 4 tests
A check of server-side resources used by JavaScript Notifier
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 33.21 ▼16.02 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 44.07 ▼5.05 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 39.81 ▼5.80 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 81.92 ▼9.90 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.83 ▲3.08 |
| JavaScript Notifier /wp-admin/options-general.php?page=javascript-notifier-settings | 3.21 | 26.31 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 11 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| javascript_notifier_settings |
Browser metrics Passed 4 tests
Checking browser requirements for JavaScript Notifier
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,860 ▲114 | 13.47 ▼0.91 | 1.72 ▼0.10 | 37.12 ▼9.46 |
| Dashboard /wp-admin | 2,229 ▲41 | 5.17 ▼0.71 | 119.58 ▲5.33 | 40.79 ▼6.80 |
| Posts /wp-admin/edit.php | 2,093 ▲4 | 2.32 ▲0.28 | 33.97 ▼1.65 | 32.11 ▼4.13 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲3 | 23.32 ▲0.11 | 609.06 ▼41.71 | 35.00 ▼23.03 |
| Media Library /wp-admin/upload.php | 1,415 ▲30 | 4.36 ▲0.16 | 119.99 ▲9.02 | 46.82 ▼3.48 |
| JavaScript Notifier /wp-admin/options-general.php?page=javascript-notifier-settings | 1,100 | 2.25 | 54.69 | 32.06 |
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 does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
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
Often overlooked, readme.txt is one of the most important files in your plugin
6 plugin tags: warning, disabled, javascript, alert, notification...
javascript-notifier/javascript-notifier.php Passed 13 tests
"JavaScript Notifier" version 1.2.7's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
100 characters long description:
Notify visitors of your website if 1st-party JavaScript is disabled. Block entire site, if required.
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
Everything looks great! No dangerous files found in this plugin165 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 13 | 15 | 132 |
| CSS | 1 | 0 | 0 | 23 |
| XML | 1 | 0 | 0 | 7 |
| JavaScript | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 8 | |
| ▷ Named functions | 1 | 12.50% |
| ▷ Anonymous functions | 7 | 87.50% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.05MB with 0.01MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-3.png | 20.58KB | 10.94KB | ▼ 46.84% |
| screenshot-2.png | 14.73KB | 9.45KB | ▼ 35.87% |
| screenshot-1.png | 13.64KB | 21.27KB | 0.00% |