Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Please fix the following installer errors
- The plugin did not install without errors
- > Warning in wp-content/plugins/wpec-targetpay-for-wp-e-commerce/wpec-targetpay.php+17
require_once(wp-content/plugins/wpec-targetpay-for-wp-e-commerce/../wp-e-commerce/wpsc-includes/merchant.class.php): failed to open stream: No such file or directory
Server metrics [RAM: ▲0.00MB] [CPU: ▼2.20ms] Passed 4 tests
Analyzing server-side resources used by WPEC Targetpay for WP E-Commerce
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 35.68 ▼1.81 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 43.65 ▼6.38 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 44.18 ▼0.69 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 106.43 ▲9.95 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.34 ▲0.07 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 7 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| theysaidso_admin_options |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WPEC Targetpay for WP E-Commerce
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.20 ▼1.36 | 1.64 ▼0.36 | 39.27 ▼3.64 |
| Dashboard /wp-admin | 2,206 ▲14 | 5.79 ▲0.83 | 101.03 ▼13.37 | 44.36 ▲4.89 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▼0.03 | 34.78 ▼4.52 | 35.59 ▼2.01 |
| Add New Post /wp-admin/post-new.php | 1,519 ▲5 | 23.19 ▲5.76 | 664.84 ▲0.99 | 52.34 ▲5.78 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.18 ▼0.00 | 93.86 ▼5.55 | 42.78 ▼5.23 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting 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 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'wpsc_merchant' not found in wp-content/plugins/wpec-targetpay-for-wp-e-commerce/classes/wpscTargetpay.class.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/wpec-targetpay-for-wp-e-commerce/wpec-targetpay.php:17
- > 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 96% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
4 plugin tags: wpsc, targetpay, ideal, wp-e-commerce
wpec-targetpay-for-wp-e-commerce/wpec-targetpay.php 92% from 13 tests
The main PHP script in "WPEC Targetpay for WP E-Commerce" version 1.000 is automatically included on every request by WordPress
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("wpec-targetpay-for-wp-e-commerce.php" instead of "wpec-targetpay.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Success! There were no dangerous files found in this plugin392 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 129 | 233 | 375 |
| CSS | 2 | 1 | 0 | 16 |
| JavaScript | 1 | 0 | 2 | 1 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.31 |
| Average class complexity | 21.50 |
| ▷ Minimum class complexity | 6.00 |
| ▷ Maximum class complexity | 37.00 |
| Average method complexity | 2.78 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.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 | 23 | |
| ▷ Static methods | 2 | 8.70% |
| ▷ Public methods | 11 | 47.83% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 12 | 52.17% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
PNG images were not found in this plugin