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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.45MB] [CPU: ▼2.19ms] Passed 4 tests
An overview of server-side resources used by Podamibe 2Checkout
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.92 ▲0.46 | 38.16 ▲1.85 |
| Dashboard /wp-admin | 3.76 ▲0.41 | 45.70 ▼11.20 |
| Posts /wp-admin/edit.php | 3.87 ▲0.51 | 46.37 ▲0.30 |
| Add New Post /wp-admin/post-new.php | 6.36 ▲0.47 | 89.58 ▲0.44 |
| Media Library /wp-admin/upload.php | 3.68 ▲0.45 | 38.03 ▲1.71 |
Server storage [IO: ▲0.18MB] [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, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Podamibe 2Checkout
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,898 ▲148 | 13.44 ▼0.91 | 11.66 ▲9.95 | 38.94 ▼7.84 |
| Dashboard /wp-admin | 2,217 ▲42 | 5.58 ▼0.14 | 80.32 ▼18.49 | 82.34 ▲38.40 |
| Posts /wp-admin/edit.php | 2,119 ▲19 | 2.05 ▲0.02 | 39.84 ▲4.03 | 38.06 ▲1.84 |
| Add New Post /wp-admin/post-new.php | 1,705 ▲179 | 24.39 ▲1.31 | 737.65 ▲47.39 | 49.96 ▲0.50 |
| Media Library /wp-admin/upload.php | 1,416 ▲13 | 4.25 ▲0.05 | 103.09 ▼7.05 | 72.55 ▲27.03 |
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
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-comments
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/podamibe-2checkout/2checkout.php
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/podamibe-2checkout/inc/functions.php:102
- > PHP Fatal error
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)
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need your attention:
- Tags: Too many tags (11 tag instead of maximum 10); only the first 5 tags are used in your directory listing
podamibe-2checkout/2checkout.php 85% from 13 tests
The entry point to "Podamibe 2Checkout" version 1.0.3 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("podamibe-2checkout.php" instead of "2checkout.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 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin1,769 lines of code in 15 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 10 | 146 | 174 | 1,472 |
| CSS | 2 | 13 | 4 | 161 |
| JavaScript | 3 | 26 | 30 | 136 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.49 |
| Average class complexity | 20.75 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 87.00 |
| Average method complexity | 5.39 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 40.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 36 | |
| ▷ Static methods | 4 | 11.11% |
| ▷ Public methods | 30 | 83.33% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 6 | 16.67% |
| Functions | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 11 | |
| ▷ Global constants | 11 | 100.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
2 PNG files occupy 0.03MB with 0.03MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/2checkout.png | 16.13KB | 1.19KB | ▼ 92.62% |
| images/2checkout22.png | 15.93KB | 1.20KB | ▼ 92.50% |