Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.12MB] [CPU: ▼140.68ms] Passed 4 tests
An overview of server-side resources used by OneDigiFlow - Lead Capture
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.93 ▲0.09 | 47.84 ▲20.74 |
| Dashboard /wp-admin | 3.20 ▲0.14 | 48.40 ▼0.24 |
| Posts /wp-admin/edit.php | 3.31 ▲0.20 | 48.33 ▲2.49 |
| Add New Post /wp-admin/post-new.php | 5.56 ▲0.12 | 90.62 ▼565.92 |
| Media Library /wp-admin/upload.php | 3.14 ▲0.14 | 35.29 ▲0.94 |
| Add Lead /wp-admin/post-new.php?post_type=odflc-leads | 3.24 | 50.59 |
| All Leads /wp-admin/edit.php?post_type=odflc-leads | 3.18 | 42.30 |
| Settings /wp-admin/edit.php?post_type=odflc-leads&page=odflc-settings | 3.13 | 32.00 |
Server storage [IO: ▲0.32MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 20 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
OneDigiFlow - Lead Capture: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,747 ▲151 | 15.86 ▼0.16 | 10.19 ▲0.64 | 50.41 ▼1.32 |
| Dashboard /wp-admin | 3,007 ▲76 | 5.91 ▼0.01 | 146.70 ▼5.55 | 122.07 ▲8.23 |
| Posts /wp-admin/edit.php | 2,779 ▲40 | 2.70 ▲0.01 | 72.77 ▲2.57 | 93.47 ▼4.97 |
| Add New Post /wp-admin/post-new.php | 1,709 ▲26 | 18.82 ▲0.02 | 378.61 ▼4.13 | 121.69 ▲2.70 |
| Media Library /wp-admin/upload.php | 1,847 ▲114 | 5.04 ▲0.03 | 163.92 ▲13.14 | 132.70 ▲9.60 |
| Add Lead /wp-admin/post-new.php?post_type=odflc-leads | 3,038 | 8.99 | 225.35 | 172.52 |
| All Leads /wp-admin/edit.php?post_type=odflc-leads | 1,472 | 2.63 | 61.71 | 75.66 |
| Settings /wp-admin/edit.php?post_type=odflc-leads&page=odflc-settings | 1,208 | 2.11 | 61.80 | 85.64 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Uninstaller ran successfully
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP Passed 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Everything seems fine, however this is by no means an exhaustive test
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
4 plugin tags: lead, onedigiflow, form, lead capture
onedigiflow-lead-capture/onedigiflow-lead-capture.php 69% from 13 tests
The entry point to "OneDigiFlow - Lead Capture" version 0.0.1 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Domain Path: Prefix the domain path with a forward slash character ("/languages")
- Domain Path: Use only dashes and lowercase characters for the domain path ("languages")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 148 characters long)
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
There were no executable files found in this plugin940 lines of code in 16 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 12 | 213 | 247 | 832 |
| JavaScript | 3 | 37 | 32 | 107 |
| CSS | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.31 |
| Average class complexity | 11.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 27.00 |
| Average method complexity | 3.42 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.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 | 26 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 26 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.23MB with 0.15MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/flags@2x.png | 170.28KB | 68.04KB | ▼ 60.04% |
| images/flags.png | 69.20KB | 23.42KB | ▼ 66.16% |