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
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼1.18ms] Passed 4 tests
This is a short check of server-side resources used by Quickpay - WordPress Payment Plugin
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.03 ▼4.24 |
Dashboard /wp-admin | 3.32 ▲0.01 | 46.37 ▲2.56 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.49 ▼1.41 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 97.27 ▲1.37 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 34.22 ▼0.42 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 20 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Quickpay - WordPress Payment Plugin
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,812 ▲77 | 13.19 ▼1.19 | 1.74 ▼0.33 | 39.08 ▼8.37 |
Dashboard /wp-admin | 2,218 ▲30 | 4.84 ▼1.04 | 109.61 ▲7.83 | 43.50 ▲0.25 |
Posts /wp-admin/edit.php | 2,101 ▲12 | 2.00 ▼0.01 | 40.15 ▼3.00 | 36.95 ▲0.14 |
Add New Post /wp-admin/post-new.php | 1,524 ▼18 | 17.74 ▼0.78 | 599.91 ▼20.45 | 55.60 ▼4.37 |
Media Library /wp-admin/upload.php | 1,394 ▲12 | 4.15 ▼0.07 | 94.03 ▼2.13 | 42.87 ▲1.21 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 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
The following issues need your attention
- 6× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/quickpay/includes/qp-settings.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/quickpay/trunk/includes/qp-settings.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/quickpay/trunk/includes/qp-form.php:114
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/quickpay/trunk/includes/qp-settings.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/quickpay/includes/qp-form.php:114
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/quickpay/includes/qp-settings.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Screenshots: These screenshots require images: #1 (Quickpay plugin settings on the WordPress admin panel.), #2 (The Quickpay form front-end view.)
quickpay/quickpay.php 92% from 13 tests
This is the main PHP file of "Quickpay - WordPress Payment Plugin" version 1.1, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
The following require your attention:
- Description: Keep the plugin description shorter than 140 characters (currently 168 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Success! There were no dangerous files found in this plugin240 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 59 | 16 | 240 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.10 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ 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 Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
No PNG images were found in this plugin