Benchmarks
Plugin footprint 65% 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.01MB] [CPU: ▼5.43ms] Passed 4 tests
This is a short check of server-side resources used by Universal WP Lead Tracking
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 39.20 ▼2.69 |
Dashboard /wp-admin | 3.32 ▼0.02 | 49.58 ▼13.22 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 49.40 ▲2.86 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 90.32 ▼3.71 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 36.03 ▼2.10 |
Universal WP Lead Tracking /wp-admin/options-general.php?page=uwplt | 3.22 | 250.13 |
Server storage [IO: ▲54.01MB] [DB: ▲0.00MB] 67% from 3 tests
Input-output and database impact of this plugin
Please fix the following
- The filesystem usage should be lower than 25MB (currently using 54.01MB)
Filesystem: 11 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_track_sessions |
New WordPress options |
---|
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Universal WP Lead Tracking
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲58 | 14.48 ▲0.10 | 1.98 ▲0.25 | 44.20 ▲3.47 |
Dashboard /wp-admin | 2,210 ▲22 | 5.78 ▼0.12 | 101.32 ▼7.77 | 41.77 ▼2.65 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 1.99 ▲0.02 | 39.08 ▲0.25 | 36.25 ▲1.13 |
Add New Post /wp-admin/post-new.php | 1,517 ▲3 | 17.51 ▲0.09 | 693.85 ▲51.65 | 58.66 ▲2.24 |
Media Library /wp-admin/upload.php | 1,395 ▲4 | 4.21 ▼0.04 | 98.25 ▼5.80 | 41.00 ▼6.23 |
Universal WP Lead Tracking /wp-admin/options-general.php?page=uwplt | 1,108 | 2.16 | 25.85 | 50.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie tables detected upon uninstall: 1 table
- wp_track_sessions
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
No output text or server-side errors detected on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
5 plugin tags: form, email, lead, tracking, contact
universal-wp-lead-tracking/universal-wp-lead-tracking.php 92% from 13 tests
The primary PHP file in "Universal WP Lead Tracking" version 1.0.3.1 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 278 characters long)
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
Good job! No executable or dangerous file extensions detected690 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 254 | 65 | 690 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 31.00 |
▷ Minimum class complexity | 31.00 |
▷ Maximum class complexity | 31.00 |
Average method complexity | 3.50 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 19.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 | 14 | |
▷ Static methods | 9 | 64.29% |
▷ Public methods | 10 | 71.43% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 4 | 28.57% |
Functions | 16 | |
▷ Named functions | 12 | 75.00% |
▷ Anonymous functions | 4 | 25.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
1 PNG file occupies 0.03MB with 0.02MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/icon-256x256.png | 30.73KB | 10.07KB | ▼ 67.22% |