Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.15MB] [CPU: ▼5.99ms] Passed 4 tests
Server-side resources used by Essert Privacy Compliance
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.11 | 39.82 ▼3.10 |
| Dashboard /wp-admin | 3.45 ▲0.14 | 46.37 ▼1.06 |
| Posts /wp-admin/edit.php | 3.54 ▲0.19 | 46.06 ▼1.56 |
| Add New Post /wp-admin/post-new.php | 6.12 ▲0.24 | 82.37 ▼13.94 |
| Media Library /wp-admin/upload.php | 3.39 ▲0.16 | 31.82 ▼5.35 |
Server storage [IO: ▲0.68MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 16 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| _essert_v2_settings |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| _essert_v2_dns_button_settings |
| widget_recent-comments |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Essert Privacy Compliance
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,811 ▲76 | 13.19 ▼1.16 | 1.71 ▼0.23 | 44.54 ▼7.15 |
| Dashboard /wp-admin | 2,217 ▲26 | 5.86 ▼0.05 | 112.01 ▲8.25 | 65.27 ▲19.51 |
| Posts /wp-admin/edit.php | 2,100 ▲14 | 2.02 ▼0.03 | 34.80 ▼3.80 | 37.34 ▲2.32 |
| Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.23 ▲5.54 | 746.96 ▲55.33 | 64.88 ▼3.09 |
| Media Library /wp-admin/upload.php | 1,402 ▲14 | 4.24 ▼0.01 | 114.60 ▲2.44 | 45.91 ▼2.75 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 79% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that require attention:
- Screenshots: Please add descriptions for these screenshots #0, #0, #0, #0, #0 in privacy-security-compliance/assets to your readme.txt
- Screenshots: These screenshots require images: #1 (Setup), #2 (Policies that are part of public disclosure), #3 (Privacy request forms (DSAR) to address privacy requests), #4 (FAQs)
- Tags: You are using too many tags: 21 tag instead of maximum 10
privacy-security-compliance/essert-privacy-compliance.php 77% from 13 tests
"Essert Privacy Compliance" version 1.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("privacy-security-compliance.php" instead of "essert-privacy-compliance.php")
- Description: Keep the plugin description shorter than 140 characters (currently 564 characters long)
- Text Domain: Please use dashes and lowercase characters for text domains
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
No dangerous file extensions were detected16,312 lines of code in 14 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 3 | 0 | 0 | 15,861 |
| PHP | 6 | 47 | 34 | 277 |
| Markdown | 1 | 43 | 0 | 90 |
| JavaScript | 4 | 5 | 1 | 84 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.60 |
| Average class complexity | 13.75 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 24.00 |
| Average method complexity | 4.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 24.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 2 | 50.00% |
| ▷ Concrete classes | 2 | 50.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 17 | |
| ▷ Static methods | 12 | 70.59% |
| ▷ Public methods | 16 | 94.12% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 5.88% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icon.png | 1.26KB | 0.98KB | ▼ 22.08% |