Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.16MB] [CPU: ▲1.49ms] Passed 4 tests
This is a short check of server-side resources used by Lead to Clio
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.59 ▲0.13 | 45.67 ▲0.52 |
| Dashboard /wp-admin | 3.47 ▲0.16 | 53.56 ▲1.21 |
| Posts /wp-admin/edit.php | 3.58 ▲0.22 | 55.24 ▲4.41 |
| Add New Post /wp-admin/post-new.php | 6.07 ▲0.19 | 101.06 ▲1.36 |
| Media Library /wp-admin/upload.php | 3.39 ▲0.16 | 36.49 ▲2.86 |
| Lead-to-Clio Settings /wp-admin/options-general.php?page=lead-to-clio-admin | 3.39 | 40.97 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 21 new files
Database: no new tables, 8 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| add_to_pages |
| lead_to_clio_version |
| can_compress_scripts |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
Lead to Clio: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,831 ▲70 | 14.38 ▲0.02 | 2.67 ▲0.96 | 44.51 ▼0.89 |
| Dashboard /wp-admin | 2,206 ▲29 | 5.61 ▼0.04 | 89.12 ▼3.87 | 38.04 ▼4.18 |
| Posts /wp-admin/edit.php | 2,108 ▲8 | 1.97 ▼0.01 | 38.25 ▼0.20 | 36.16 ▼2.74 |
| Add New Post /wp-admin/post-new.php | 6,229 ▲4,701 | 19.13 ▼3.94 | 907.10 ▲224.50 | 62.41 ▲13.12 |
| Media Library /wp-admin/upload.php | 1,405 ▲5 | 4.30 ▲0.10 | 97.31 ▼3.22 | 40.90 ▲0.34 |
| Lead-to-Clio Settings /wp-admin/options-general.php?page=lead-to-clio-admin | 1,099 | 3.13 | 49.52 | 27.40 |
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
These items require your attention
- Zombie WordPress options were found after uninstall: 8 options
- can_compress_scripts
- widget_recent-comments
- add_to_pages
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- lead_to_clio_version
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
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 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 93% 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
Please fix the following attributes:
- Plugin Name: You should set the name of your plugin on the first line (
=== lead-to-clio ===)
lead-to-clio/lead-to-clio.php 92% from 13 tests
The primary PHP file in "Lead to Clio" version 1.0 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Success! There were no dangerous files found in this plugin1,006 lines of code in 14 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 227 | 429 | 871 |
| CSS | 1 | 0 | 0 | 75 |
| JavaScript | 5 | 16 | 6 | 60 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 25.33 |
| ▷ Minimum class complexity | 5.00 |
| ▷ Maximum class complexity | 76.00 |
| Average method complexity | 3.98 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 46.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 6 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 6 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 49 | |
| ▷ Static methods | 3 | 6.12% |
| ▷ Public methods | 43 | 87.76% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 12.24% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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
No PNG images were found in this plugin