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: ▼5.97ms] Passed 4 tests
An overview of server-side resources used by Pixeline's Email Protector
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 54.28 ▲18.96 |
| Dashboard /wp-admin | 3.34 ▼0.01 | 55.80 ▼4.50 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 45.08 ▼1.96 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 84.78 ▼15.86 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 34.41 ▼1.56 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 8 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| can_compress_scripts |
| p_email_protector_options |
Browser metrics Passed 4 tests
Checking browser requirements for Pixeline's Email Protector
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,795 ▲49 | 14.38 ▲0.03 | 2.56 ▲0.70 | 57.71 ▲13.79 |
| Dashboard /wp-admin | 2,193 ▲13 | 5.55 ▼0.08 | 89.27 ▲3.70 | 38.00 ▼4.47 |
| Posts /wp-admin/edit.php | 2,104 ▲4 | 2.03 ▲0.03 | 34.18 ▼3.04 | 33.54 ▼2.93 |
| Add New Post /wp-admin/post-new.php | 1,534 ▼3 | 23.22 ▲5.02 | 653.16 ▲2.98 | 57.98 ▼17.99 |
| Media Library /wp-admin/upload.php | 1,398 ▼2 | 4.21 ▼0.14 | 97.17 ▼17.65 | 42.08 ▼5.51 |
| Email protector /wp-admin/pixeline-email-protector.php | 26 | 0.42 | 0.07 | 13.75 |
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
Please fix the following items
- The uninstall procedure has failed, leaving 7 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- p_email_protector_options
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
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
Please take a closer look at the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_locale() in wp-content/plugins/pixelines-email-protector/pixeline-email-protector.php:43
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/pixelines-email-protector/admin.ui.php:3
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Please fix the following user-side errors
- > GET request to /wp-admin/pixeline-email-protector.php
- > Network (severe)
wp-admin/pixeline-email-protector.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Tags: Please delete some tags, you are using 15 tag instead of maximum 10
pixelines-email-protector/pixeline-email-protector.php 92% from 13 tests
The main file in "Pixeline's Email Protector" v. 1.3.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("pixelines-email-protector.php" instead of "pixeline-email-protector.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin301 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 37 | 54 | 169 |
| PO File | 1 | 35 | 59 | 130 |
| JavaScript | 1 | 0 | 0 | 2 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.12 |
| Average class complexity | 10.00 |
| ▷ Minimum class complexity | 10.00 |
| ▷ Maximum class complexity | 10.00 |
| Average method complexity | 1.90 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.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 | 10 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 10 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.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
PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin