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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.12MB] [CPU: ▼5.79ms] Passed 4 tests
A check of server-side resources used by HUEM: Huge Upload Enabler, mostly
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.59 ▲0.13 | 43.32 ▼1.98 |
| Dashboard /wp-admin | 3.42 ▲0.12 | 48.03 ▼7.13 |
| Posts /wp-admin/edit.php | 3.53 ▲0.18 | 49.98 ▲0.39 |
| Add New Post /wp-admin/post-new.php | 6.00 ▲0.12 | 88.03 ▼13.86 |
| Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 38.18 ▼0.17 |
| HUEM /wp-admin/options-general.php?page=wp-awesome-options | 3.32 | 34.37 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for HUEM: Huge Upload Enabler, mostly
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,906 ▲145 | 13.65 ▼0.70 | 7.98 ▲6.18 | 38.16 ▼6.48 |
| Dashboard /wp-admin | 2,199 ▲22 | 5.51 ▼0.08 | 93.28 ▲0.03 | 41.49 ▼1.24 |
| Posts /wp-admin/edit.php | 2,104 ▲4 | 2.02 ▲0.07 | 34.52 ▼3.55 | 36.62 ▲0.41 |
| Add New Post /wp-admin/post-new.php | 1,540 ▲14 | 18.21 ▼4.80 | 650.08 ▼47.58 | 67.72 ▲3.66 |
| Media Library /wp-admin/upload.php | 1,401 ▲1 | 4.22 ▲0.14 | 99.86 ▼15.19 | 45.36 ▼4.07 |
| HUEM /wp-admin/options-general.php?page=wp-awesome-options | 873 | 2.17 | 26.18 | 28.79 |
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
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
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)
Everything seems fine, however this is by no means an exhaustive test
SRP 0% 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
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/wp-awesome/wp-awesome.php
- 3× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Interface 'WPA\\Module\\Fluent\\Backends\\BackendInterface' not found in wp-content/plugins/wp-awesome/modules/Fluent/Backends/WP_Query.php:4
- > PHP Fatal error
Uncaught Error: Interface 'WPA\\Module\\Fluent\\Backend\\IteratorAggregate' not found in wp-content/plugins/wp-awesome/modules/Fluent/Backends/BackendInterface.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/wp-awesome/pages/options.php:2
- > 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 errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
10 plugin tags: context menu, upload limit, upload size, user experience, user interface...
wp-awesome/wp-awesome.php 77% from 13 tests
The main PHP script in "HUEM: Huge Upload Enabler, mostly" version 1.0.1 is automatically included on every request by WordPress
You should first fix the following items:
- Domain Path: The domain path should be prefixed with a forward slash character ("/Languages")
- Domain Path: Note that the domain path follows the same naming rules as the domain name, using only dashes and lowercase characters ("Languages")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected1,022 lines of code in 18 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 14 | 170 | 147 | 805 |
| JavaScript | 2 | 27 | 6 | 141 |
| CSS | 1 | 0 | 0 | 40 |
| PO File | 1 | 9 | 9 | 36 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.62 |
| Average class complexity | 15.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 78.00 |
| Average method complexity | 4.87 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 72.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 7 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 11 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 11 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 46 | |
| ▷ Static methods | 29 | 63.04% |
| ▷ Public methods | 45 | 97.83% |
| ▷ Protected methods | 1 | 2.17% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 1 | 100.00% |
| Constants | 4 | |
| ▷ Global constants | 2 | 50.00% |
| ▷ Class constants | 2 | 50.00% |
| ▷ Public constants | 2 | 100.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
No PNG files were detected