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.05MB] [CPU: ▼6.54ms] Passed 4 tests
A check of server-side resources used by HandL UTM Grabber / Tracker
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.10 | 41.39 ▲1.35 |
| Dashboard /wp-admin | 3.36 ▲0.02 | 50.54 ▼8.05 |
| Posts /wp-admin/edit.php | 3.41 ▲0.05 | 46.32 ▼6.54 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 87.43 ▼12.93 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 37.98 ▲4.33 |
Server storage [IO: ▲1.08MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
HandL UTM Grabber / Tracker: an overview of browser usage
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,038 ▲292 | 13.47 ▼0.88 | 13.34 ▲11.73 | 29.85 ▼16.82 |
| Dashboard /wp-admin | 2,321 ▲147 | 5.55 ▼0.04 | 87.00 ▼2.02 | 47.96 ▲4.01 |
| Posts /wp-admin/edit.php | 2,179 ▲79 | 2.05 ▲0.08 | 38.44 ▲1.23 | 35.92 ▲1.81 |
| Add New Post /wp-admin/post-new.php | 1,575 ▲47 | 23.08 ▼0.22 | 698.22 ▲84.36 | 58.44 ▲9.90 |
| Media Library /wp-admin/upload.php | 1,482 ▲85 | 4.13 ▼0.01 | 112.52 ▲6.80 | 52.15 ▲10.89 |
| Apps /wp-admin/handl-utm-grabber.php?page=handl_apps | 26 | 0.42 | 0.09 | 15.12 |
| Knowledge Base /wp-admin/handl-utm-grabber.php?page=handl_kb | 26 | 0.42 | 0.08 | 5.45 |
| Premium /wp-admin/handl-utm-grabber.php?page=handl_go_premium | 26 | 0.42 | 0.08 | 6.10 |
| UTM /wp-admin/handl-utm-grabber.php | 26 | 0.42 | 0.09 | 6.09 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'NF_Abstracts_MergeTags' not found in wp-content/plugins/handl-utm-grabber/external/ninja.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/handl-utm-grabber/external/zapier.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/handl-utm-grabber/external/zapier.php:10
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please take a look at the following user-side issues
- > GET request to /wp-admin/handl-utm-grabber.php?page=handl_apps
- > Network (severe)
wp-admin/handl-utm-grabber.php?page=handl_apps - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/handl-utm-grabber.php?page=handl_kb
- > Network (severe)
wp-admin/handl-utm-grabber.php?page=handl_kb - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/handl-utm-grabber.php?page=handl_go_premium
- > Network (severe)
wp-admin/handl-utm-grabber.php?page=handl_go_premium - Failed to load resource: the server responded with a status of 404 (Not Found)
- > GET request to /wp-admin/handl-utm-grabber.php
- > Network (severe)
wp-admin/handl-utm-grabber.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% 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
These attributes need to be fixed:
- Tags: Please delete some tags, you are using 11 tag instead of maximum 10
- Screenshots: Please add an image for screenshot #1 (Zapier Integration)
handl-utm-grabber/handl-utm-grabber.php Passed 13 tests
This is the main PHP file of "HandL UTM Grabber / Tracker" version 2.7.26, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
54 characters long description:
The easiest way to capture UTMs on your (optin) forms.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected3,069 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 526 | 355 | 2,698 |
| CSS | 1 | 40 | 0 | 202 |
| JavaScript | 3 | 35 | 13 | 169 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.53 |
| Average class complexity | 43.67 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 246.00 |
| Average method complexity | 4.90 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 63.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 9 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 9 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 99 | |
| ▷ Static methods | 1 | 1.01% |
| ▷ Public methods | 84 | 84.85% |
| ▷ Protected methods | 15 | 15.15% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 57 | |
| ▷ Named functions | 50 | 87.72% |
| ▷ Anonymous functions | 7 | 12.28% |
| Constants | 24 | |
| ▷ Global constants | 24 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
12 PNG files occupy 0.94MB with 0.65MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/gclid_reporter.png | 65.82KB | 20.40KB | ▼ 69.01% |
| screenshot-11.png | 171.39KB | 47.03KB | ▼ 72.56% |
| screenshot-8.png | 197.04KB | 55.57KB | ▼ 71.80% |
| screenshot-5.png | 142.24KB | 47.10KB | ▼ 66.89% |
| screenshot-9.png | 147.89KB | 49.79KB | ▼ 66.34% |