Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.03MB] [CPU: ▼3.53ms] Passed 4 tests
Analyzing server-side resources used by WP Secure Content
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.63 ▲0.16 | 34.76 ▼8.89 |
| Dashboard /wp-admin | 3.34 ▲0.03 | 52.92 ▲1.12 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 48.16 ▲1.81 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 82.32 ▼8.17 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 37.63 ▲3.54 |
| WP SC /wp-admin/options-general.php?page=wp_sc | 3.25 | 33.76 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 12 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for WP Secure Content
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,946 ▲189 | 13.61 ▼1.03 | 5.68 ▲3.69 | 36.93 ▼16.13 |
| Dashboard /wp-admin | 2,214 ▲26 | 4.86 ▼0.01 | 98.78 ▼10.96 | 37.69 ▼6.65 |
| Posts /wp-admin/edit.php | 2,097 ▲8 | 2.02 ▼0.00 | 39.47 ▲4.11 | 35.72 ▲2.85 |
| Add New Post /wp-admin/post-new.php | 1,521 ▲2 | 17.86 ▼5.67 | 643.50 ▼52.87 | 59.71 ▼10.55 |
| Media Library /wp-admin/upload.php | 1,393 ▲2 | 4.36 ▲0.05 | 101.18 ▼2.25 | 44.21 ▼1.30 |
| WP SC /wp-admin/options-general.php?page=wp_sc | 813 | 2.07 | 26.53 | 36.56 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
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
Congratulations! This plugin passed the SRP test
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)
There were no browser issues found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Attributes that need to be fixed:
- Screenshots: Please add images for these screenshots: #2 (Create a new directory named `wp-secure-content` in the `wp-content/plugins` directory of your WordPress installation. Use an FTP or SFTP client to upload the contents of your plugin archive to the new directory that you just created on your web host.), #3 (Log in to the WordPress Dashboard and activate the WP Secure Content plugin.), #4 (Once the plugin is activated, a new **WP Secure Content** sub-menu will appear in your Wordpress admin -> settings menu.)
wp-secure-content/index.php 77% from 13 tests
The main file in "WP Secure Content" v. 1.1.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wp-secure-content.php" instead of "index.php")
- Description: Please don't use more than 140 characters for the plugin description (currently 158 characters long)
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
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 detected311 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 90 | 19 | 175 |
| PO File | 3 | 27 | 27 | 102 |
| JavaScript | 1 | 4 | 1 | 31 |
| CSS | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| 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 | 9 | |
| ▷ Named functions | 9 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin