Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼7.98ms] Passed 4 tests
Analyzing server-side resources used by Clio Grow
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 36.93 ▼1.67 |
Dashboard /wp-admin | 3.35 ▲0.01 | 48.62 ▼9.10 |
Posts /wp-admin/edit.php | 3.40 ▲0.05 | 48.76 ▼1.92 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 85.31 ▼19.24 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 35.60 ▲0.97 |
Clio Grow Settings /wp-admin/options-general.php?page=Grow_Form_settings | 3.28 | 38.39 |
Server storage [IO: ▲0.37MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 25 new files
Database: no new tables, 7 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-comments |
widget_recent-posts |
Grow_Form_version |
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Clio Grow
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,907 ▲146 | 13.37 ▼0.98 | 8.39 ▲6.90 | 37.99 ▼0.68 |
Dashboard /wp-admin | 2,203 ▲23 | 5.64 ▼0.01 | 84.40 ▼5.97 | 36.22 ▼9.65 |
Posts /wp-admin/edit.php | 2,087 ▼13 | 2.01 ▲0.03 | 33.88 ▼1.91 | 32.12 ▼6.60 |
Add New Post /wp-admin/post-new.php | 1,533 ▲7 | 22.97 ▼0.56 | 609.88 ▼20.56 | 64.36 ▼4.43 |
Media Library /wp-admin/upload.php | 1,402 ▲2 | 4.15 ▼0.07 | 102.35 ▼1.97 | 42.59 ▲0.09 |
Clio Grow Settings /wp-admin/options-general.php?page=Grow_Form_settings | 1,158 | 3.12 | 48.92 | 54.08 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- The uninstall procedure has failed, leaving 7 options in the database
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- Grow_Form_version
- widget_theysaidso_widget
Smoke tests 75% from 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 50% 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
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/clio-grow-form/includes/templates/form.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
9 plugin tags: contact, lawyer, wordpress, plugin, lead tracking...
clio-grow-form/grow-form.php 77% from 13 tests
The main PHP script in "Clio Grow" version 1.0.2 is automatically included on every request by WordPress
Please make the necessary changes and fix the following:
- Requires at least: Required version must be the same as the one declared in readme.txt ("3.9" instead of "4.0")
- Main file name: Name the main plugin file the same as the plugin slug ("clio-grow-form.php" instead of "grow-form.php")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin1,190 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 9 | 281 | 620 | 1,134 |
JavaScript | 5 | 16 | 6 | 56 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
Average class complexity | 30.60 |
▷ Minimum class complexity | 5.00 |
▷ Maximum class complexity | 61.00 |
Average method complexity | 3.79 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 43.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 5 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 5 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 53 | |
▷ Static methods | 4 | 7.55% |
▷ Public methods | 45 | 84.91% |
▷ Protected methods | 3 | 5.66% |
▷ Private methods | 5 | 9.43% |
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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.02MB with 0.02MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
includes/templates/images/clio-grow-logo-dark-small-200x100.png | 12.74KB | 3.33KB | ▼ 73.87% |
includes/templates/images/clio-grow-logo-dark-small-169x75.png | 10.76KB | 3.09KB | ▼ 71.26% |