Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.14MB] [CPU: ▼9.37ms] Passed 4 tests
This is a short check of server-side resources used by WP Privacy
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.73 ▼0.73 | 16.02 ▼36.83 |
Dashboard /wp-admin | 3.36 ▲0.06 | 45.50 ▼2.49 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 48.09 ▲0.73 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.08 | 94.17 ▲1.93 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 32.96 ▲1.11 |
密码保护 /wp-admin/options-general.php?page=wp_privacy-setting-admin | 3.25 | 38.16 |
Server storage [IO: ▲0.59MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 55 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_hidemysiteSecure |
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Privacy
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,835 ▲100 | 13.63 ▼0.93 | 1.80 ▼0.55 | 44.07 ▼14.29 |
Dashboard /wp-admin | 2,238 ▲53 | 5.03 ▼0.85 | 103.20 ▲0.91 | 49.84 ▲4.20 |
Posts /wp-admin/edit.php | 2,104 ▲12 | 2.33 ▲0.36 | 42.45 ▲7.20 | 45.47 ▲15.36 |
Add New Post /wp-admin/post-new.php | 1,552 ▲18 | 23.58 ▲0.44 | 582.91 ▼105.50 | 33.16 ▼19.85 |
Media Library /wp-admin/upload.php | 1,426 ▲41 | 4.44 ▲0.16 | 97.60 ▼2.80 | 51.40 ▲5.15 |
密码保护 /wp-admin/options-general.php?page=wp_privacy-setting-admin | 1,486 | 3.79 | 56.11 | 175.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- Zombie tables detected upon uninstall: 1 table
- wp_hidemysiteSecure
- The uninstall procedure has failed, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- db_upgraded
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=wp_privacy-setting-admin
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=wp_privacy-setting-admin
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
- 4 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wp_privacy-setting-admin
- > Notice in wp-content/plugins/wp-privacy/index.php+893
Undefined index: class
- > GET request to /wp-admin/options-general.php?page=wp_privacy-setting-admin
- > Notice in wp-content/plugins/wp-privacy/index.php+963
Undefined index: desc
SRP 0% from 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 following issues need your attention
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/wp-privacy/templates/hmsdiscreet.php
- 11× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wp-privacy/templates/hmsiris.php:11
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wp-privacy/templates/hmsclassic.php:11
- > PHP Notice
Undefined variable: messagehtml in wp-content/plugins/wp-privacy/templates/hmsdefault.php on line 106
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/wp-privacy/index.php:25
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wp-privacy/templates/hmscobalt.php:10
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wp-privacy/templates/hmsbinder.php:11
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wp-privacy/templates/hmsdefault.php:111
- > PHP Notice
Undefined variable: messagehtml in wp-content/plugins/wp-privacy/templates/hmsdiscreet.php on line 71
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wp-privacy/templates/hmsice.php:11
- > PHP Notice
Undefined variable: hinthtml in wp-content/plugins/wp-privacy/templates/hmsdiscreet.php on line 75
- > 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 on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: hide-my-site, wp-privacy, privacy, password protection, password
wp-privacy/index.php 85% from 13 tests
This is the main PHP file of "WP Privacy" version 1.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
The following require your attention:
- Description: Please don't use more than 140 characters for the plugin description (currently 289 characters long)
- Main file name: The principal plugin file should be the same as the plugin slug ("wp-privacy.php" instead of "index.php")
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
There were no executable files found in this plugin1,440 lines of code in 12 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 10 | 148 | 188 | 1,414 |
JavaScript | 2 | 14 | 5 | 26 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 45.00 |
▷ Minimum class complexity | 13.00 |
▷ Maximum class complexity | 77.00 |
Average method complexity | 3.32 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 23.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 38 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 38 | 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
29 PNG files occupy 0.21MB with 0.04MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/bg_dot.png | 0.12KB | 0.10KB | ▼ 16.67% |
images/premium_back.png | 10.54KB | 8.60KB | ▼ 18.33% |
images/default.png | 1.38KB | 1.24KB | ▼ 9.92% |
images/login_button_cobalt.png | 2.84KB | 2.00KB | ▼ 29.46% |
images/input_back_lockandkey.png | 0.76KB | 0.58KB | ▼ 24.55% |