Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.11ms] Passed 4 tests
Server-side resources used by e2payments-wp Payment for Woocommerce
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 42.25 ▼1.24 |
Dashboard /wp-admin | 3.31 ▲0.00 | 44.78 ▼7.42 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.99 ▲1.63 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 82.16 ▼9.42 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 36.55 ▲3.61 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for e2payments-wp Payment for Woocommerce
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲90 | 14.73 ▲0.35 | 2.13 ▲0.23 | 43.74 ▼6.09 |
Dashboard /wp-admin | 2,206 ▲18 | 5.88 ▲1.01 | 110.04 ▼0.05 | 38.40 ▼10.85 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.06 ▲0.01 | 43.51 ▲8.13 | 34.57 ▼0.66 |
Add New Post /wp-admin/post-new.php | 1,514 ▼20 | 17.80 ▼5.30 | 684.66 ▼10.47 | 56.58 ▼0.76 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.29 ▲0.10 | 93.21 ▼2.63 | 41.48 ▼4.13 |
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
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not 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
Almost there! Just fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/e2payments-wp-payment-for-woocommerce/woocommerce.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 76% from 29 tests
readme.txt 69% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need your attention:
- Contributors: Plugin contributors not specified
- Donate link: Invalid URI ("")
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== e2payments-wp-payment-for-woocommerce ===
) - Screenshots: Add images for these screenshots: #1 (Screenshot from 2023-04-03 23-53-06.png), #2 (Screenshot from 2023-04-03 23-54-48.png)
- Contributors: There were no tags found
e2payments-wp-payment-for-woocommerce/woocommerce.php 85% from 13 tests
The primary PHP file in "e2payments-wp Payment for Woocommerce" version 1.0.0 is used by WordPress to initiate all plugin functionality
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("e2payments-wp-payment-for-woocommerce.php" instead of "woocommerce.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 361 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected271 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 49 | 69 | 185 |
JavaScript | 2 | 23 | 7 | 54 |
Markdown | 1 | 20 | 0 | 32 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.36 |
Average class complexity | 23.00 |
▷ Minimum class complexity | 23.00 |
▷ Maximum class complexity | 23.00 |
Average method complexity | 3.75 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.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 | 8 | |
▷ Static methods | 1 | 12.50% |
▷ Public methods | 8 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 2 | 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
No PNG files were detected