Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼142.25ms] Passed 4 tests
Server-side resources used by HSTS Ready
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.85 ▲0.01 | 30.52 ▼5.41 |
Dashboard /wp-admin | 3.08 ▲0.02 | 46.05 ▼0.51 |
Posts /wp-admin/edit.php | 3.13 ▲0.02 | 47.06 ▲0.07 |
Add New Post /wp-admin/post-new.php | 5.43 ▼0.00 | 93.39 ▼559.37 |
Media Library /wp-admin/upload.php | 3.02 ▲0.01 | 30.63 ▼3.72 |
HSTS Ready /wp-admin/options-general.php?page=hsts_ready_settings | 2.99 | 27.67 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 2 new options
New WordPress options |
---|
hsts_ready_subdomains |
hsts_ready_expire |
Browser metrics Passed 4 tests
Checking browser requirements for HSTS Ready
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,684 ▲88 | 16.25 ▲0.62 | 9.99 ▲1.21 | 49.70 ▼4.42 |
Dashboard /wp-admin | 2,975 ▲44 | 5.95 ▼0.07 | 138.66 ▼8.12 | 103.16 ▼9.11 |
Posts /wp-admin/edit.php | 2,741 ▲2 | 2.72 ▲0.01 | 67.21 ▲4.50 | 88.35 ▼3.07 |
Add New Post /wp-admin/post-new.php | 1,675 ▲5 | 18.87 ▼0.23 | 382.83 ▲10.43 | 111.89 ▲5.40 |
Media Library /wp-admin/upload.php | 1,815 ▲8 | 5.02 ▼0.02 | 146.70 ▼13.87 | 124.06 ▼4.96 |
HSTS Ready /wp-admin/options-general.php?page=hsts_ready_settings | 1,059 | 2.09 | 51.12 | 65.31 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The plugin uninstalled successfully, without leaving any zombie files or tables
Smoke tests 75% 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 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/hsts-ready/hsts_ready.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
5 plugin tags: security, strict transport security, https, hsts, seo
hsts-ready/hsts_ready.php 77% from 13 tests
The primary PHP file in "HSTS Ready" version 1.03 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("hsts-ready.php" instead of "hsts_ready.php")
- Domain Path: The domain path should use only dashes and lowercase characters ("")
- Domain Path: Please prefix the domain path with a forward slash character ("/")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected47 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 13 | 13 | 47 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
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 | 5 | |
▷ Named functions | 5 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
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/fb.png | 1.59KB | 1.00KB | ▼ 37.42% |