Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼7.20ms] Passed 4 tests
A check of server-side resources used by Paack Delivery
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 37.64 ▼1.87 |
Dashboard /wp-admin | 3.33 ▲0.02 | 43.77 ▼2.20 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 45.51 ▼2.07 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 83.54 ▼22.66 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 34.43 ▼0.69 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 12 new files
Database: no new tables, 10 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
text_popup |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
paack_message_zip_code_error |
paack_message_zip_code_success |
is_store_valid |
Browser metrics Passed 4 tests
An overview of browser requirements for Paack Delivery
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,841 ▲106 | 13.32 ▼1.32 | 4.85 ▲3.33 | 41.68 ▲0.39 |
Dashboard /wp-admin | 2,222 ▲36 | 4.83 ▼0.13 | 108.33 ▲2.16 | 37.89 ▼3.47 |
Posts /wp-admin/edit.php | 2,105 ▲16 | 2.01 ▲0.01 | 35.76 ▼5.95 | 36.07 ▼2.16 |
Add New Post /wp-admin/post-new.php | 1,546 ▲13 | 23.46 ▲0.32 | 636.00 ▲1.25 | 53.19 ▲1.81 |
Media Library /wp-admin/upload.php | 1,404 ▲16 | 4.22 ▲0.00 | 105.58 ▲10.05 | 44.80 ▲2.96 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- This plugin does not fully uninstall, leaving 10 options in the database
- db_upgraded
- paack_message_zip_code_success
- is_store_valid
- widget_recent-posts
- theysaidso_admin_options
- paack_message_zip_code_error
- text_popup
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests 50% 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)
Good news, no errors were detected
SRP 0% 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
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/paack-delivery/paack_delivery.php
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/paack-delivery/checkout/checkout.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/paack-delivery/admin/paack_delivery_menu.php:4
- > 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 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
3 plugin tags: ecommerce, delivery, paack
paack-delivery/paack_delivery.php 92% from 13 tests
"Paack Delivery" version 1.0.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("paack-delivery.php" instead of "paack_delivery.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
There were no executable files found in this plugin2,238 lines of code in 11 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 3 | 425 | 168 | 1,515 |
CSS | 2 | 42 | 6 | 380 |
PHP | 5 | 56 | 10 | 308 |
Markdown | 1 | 18 | 0 | 35 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.20 |
Average class complexity | 3.67 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 6.00 |
Average method complexity | 1.62 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 13 | |
▷ Static methods | 5 | 38.46% |
▷ Public methods | 10 | 76.92% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 3 | 23.08% |
Functions | 8 | |
▷ Named functions | 8 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 3 | 100.00% |
▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
1 PNG file occupies 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/icon.png | 6.04KB | 3.14KB | ▼ 47.96% |