Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼1.95ms] Passed 4 tests
An overview of server-side resources used by Is Varnish Working?
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 40.33 ▼1.72 |
| Dashboard /wp-admin | 3.34 ▲0.03 | 49.85 ▼3.62 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 51.59 ▲2.05 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 95.30 ▼4.51 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 41.11 ▲4.54 |
| Is Varnish Working? /wp-admin/options-general.php?page=is-varnish-working | 3.23 | 35.89 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
Is Varnish Working?: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,821 ▲35 | 13.24 ▼1.16 | 1.94 ▼0.41 | 43.70 ▼7.18 |
| Dashboard /wp-admin | 2,224 ▲24 | 4.85 ▼0.97 | 113.91 ▼7.07 | 42.75 ▼1.48 |
| Posts /wp-admin/edit.php | 2,109 ▲12 | 1.99 ▼0.01 | 41.31 ▲2.11 | 37.88 ▼1.86 |
| Add New Post /wp-admin/post-new.php | 1,547 ▲2 | 22.89 ▼0.26 | 651.14 ▼50.23 | 79.65 ▲20.52 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.21 ▼0.16 | 113.04 ▲2.60 | 48.29 ▼0.53 |
| Is Varnish Working? /wp-admin/options-general.php?page=is-varnish-working | 939 | 1.83 | 29.12 | 44.42 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Contributors: The plugin tags were not defined
- Contributors: Plugin contributors not specified
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== is-varnish-working ===)
is-varnish-working/is-varnish-working.php 92% from 13 tests
The principal PHP file in "Is Varnish Working?" v. 1.0.2 is loaded by WordPress automatically on each request
The following require your attention:
- Domain Path: The domain path points to a folder that does not exist ("/languages")
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 detected205 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 30 | 20 | 205 |
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.17 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.29 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.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 | 7 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 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 | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin