Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼139.80ms] Passed 4 tests
An overview of server-side resources used by WP-e-Commerce Putler Connector
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.84 ▲0.12 | 38.30 ▲12.17 |
| Dashboard /wp-admin | 3.07 ▲0.01 | 57.83 ▲6.18 |
| Posts /wp-admin/edit.php | 3.12 ▲0.01 | 49.42 ▲0.99 |
| Add New Post /wp-admin/post-new.php | 5.42 ▼0.01 | 91.19 ▼571.43 |
| Media Library /wp-admin/upload.php | 3.01 ▲0.01 | 39.60 ▲5.06 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 10 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP-e-Commerce Putler Connector
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,679 ▲83 | 16.37 ▲0.87 | 8.89 ▼5.14 | 52.97 ▲2.16 |
| Dashboard /wp-admin | 2,967 ▲36 | 6.00 ▼0.21 | 160.43 ▲11.89 | 107.49 ▼1.07 |
| Posts /wp-admin/edit.php | 2,739 ▼0 | 2.71 ▼0.01 | 79.10 ▲4.51 | 97.59 ▲6.68 |
| Add New Post /wp-admin/post-new.php | 1,498 ▼83 | 18.99 ▼1.24 | 409.19 ▼24.15 | 113.65 ▲1.35 |
| Media Library /wp-admin/upload.php | 1,807 ▼0 | 5.01 ▼0.02 | 168.29 ▲2.31 | 115.63 ▼4.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The plugin uninstalled successfully, without leaving any zombie files or tables
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-e-commerce-putler-connector/wpec-putler-connector.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 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
Attributes that need to be fixed:
- Screenshots: These screenshots do not have images: #1 (WP-e-Commerce Putler Connector Settings Page), #2 (Putler Sales Dashboard), #3 (Adding a new account in Putler - Notice API token that needs to be copied to Putler Connector settings)
- Tags: There are too many tags (14 tag instead of maximum 10)
wp-e-commerce-putler-connector/wpec-putler-connector.php 92% from 13 tests
The principal PHP file in "WP-e-Commerce Putler Connector" v. 2.1 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("wp-e-commerce-putler-connector.php" instead of "wpec-putler-connector.php")
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
Success! There were no dangerous files found in this plugin559 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 138 | 43 | 427 |
| JavaScript | 1 | 53 | 2 | 117 |
| CSS | 1 | 1 | 0 | 15 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.34 |
| Average class complexity | 32.00 |
| ▷ Minimum class complexity | 29.00 |
| ▷ Maximum class complexity | 35.00 |
| Average method complexity | 5.77 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 28.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 13 | |
| ▷ Static methods | 1 | 7.69% |
| ▷ Public methods | 11 | 84.62% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 15.38% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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 Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
4 compressed PNG files occupy 0.06MB
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-3.png | 4.86KB | 5.36KB | 0.00% |
| assets/images/green-tick.png | 1.79KB | 1.85KB | 0.00% |
| screenshot-2.png | 51.85KB | 55.70KB | 0.00% |
| screenshot-1.png | 4.36KB | 4.71KB | 0.00% |