Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.09MB] [CPU: ▼4.06ms] Passed 4 tests
A check of server-side resources used by Step pay
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.09 | 42.69 ▲0.37 |
Dashboard /wp-admin | 3.40 ▲0.09 | 51.59 ▼0.04 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 50.59 ▲1.91 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.09 | 86.13 ▼18.48 |
Media Library /wp-admin/upload.php | 3.32 ▲0.09 | 40.89 ▲4.70 |
Server storage [IO: ▲0.84MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
can_compress_scripts |
widget_theysaidso_widget |
theysaidso_admin_options |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Step pay
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 14.74 ▲0.38 | 2.26 ▲0.12 | 42.74 ▼14.49 |
Dashboard /wp-admin | 2,206 ▲18 | 5.85 ▼0.06 | 95.49 ▼19.85 | 37.32 ▼6.74 |
Posts /wp-admin/edit.php | 2,086 ▼6 | 1.99 ▼0.00 | 35.10 ▼7.78 | 33.12 ▼0.23 |
Add New Post /wp-admin/post-new.php | 1,521 ▲7 | 23.24 ▲5.88 | 610.20 ▼84.08 | 46.60 ▼10.28 |
Media Library /wp-admin/upload.php | 1,385 ▲3 | 4.26 ▼0.01 | 95.60 ▼6.18 | 41.01 ▼3.28 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
You still need to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
Smoke tests Passed 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 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
Looking good! No server-side errors or output 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 on the user side
Optimizations
Plugin configuration 79% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== step-pay ===
) - Screenshots: These screenshots require images: #1 (Auth page: the customer must create an account or log in the app.), #2 (Cards page: the customer chooses one of his cards or add a new one.), #3 (Checkout page: the customer sees a summary of the order and pays by installments.)
step-pay/class-wc-gateway-splittypay-step.php 69% from 13 tests
"Step pay" version 1.6.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
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 ("step-pay.php" instead of "class-wc-gateway-splittypay-step.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Requires at least: Required version must match the one declared in readme.txt ("4.0.1" instead of "2.2")
- Domain Path: The domain path folder was not found ("/languages")
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
There were no executable files found in this plugin454 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 55 | 80 | 454 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 24.00 |
▷ Minimum class complexity | 24.00 |
▷ Maximum class complexity | 24.00 |
Average method complexity | 2.64 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.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 | 0 | 0.00% |
▷ Public methods | 11 | 78.57% |
▷ Protected methods | 3 | 21.43% |
▷ Private methods | 0 | 0.00% |
Functions | 10 | |
▷ Named functions | 10 | 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 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
4 PNG files occupy 0.81MB with 0.60MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshots/screenshot 1.png | 237.86KB | 48.52KB | ▼ 79.60% |
assets/screenshots/screenshot 3.png | 249.79KB | 51.85KB | ▼ 79.24% |
assets/screenshots/screenshot 2.png | 318.20KB | 67.40KB | ▼ 78.82% |
assets/images/splittypay.png | 20.05KB | 7.75KB | ▼ 61.36% |