Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.13MB] [CPU: ▼6.87ms] Passed 4 tests
A check of server-side resources used by WP Frontend Submit
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.61 ▲0.14 | 40.07 ▲2.06 |
Dashboard /wp-admin | 3.44 ▲0.09 | 46.99 ▼16.98 |
Posts /wp-admin/edit.php | 3.55 ▲0.20 | 48.27 ▲1.33 |
Add New Post /wp-admin/post-new.php | 6.04 ▲0.15 | 90.21 ▼13.87 |
Media Library /wp-admin/upload.php | 3.36 ▲0.13 | 35.06 ▲2.89 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 26 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
WP Frontend Submit: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,890 ▲144 | 13.91 ▼0.38 | 9.00 ▲7.23 | 38.44 ▼4.47 |
Dashboard /wp-admin | 2,213 ▲25 | 4.88 ▼0.03 | 97.84 ▼18.43 | 39.07 ▼9.43 |
Posts /wp-admin/edit.php | 2,093 ▲5 | 2.01 ▲0.05 | 39.67 ▼1.21 | 36.84 ▲2.46 |
Add New Post /wp-admin/post-new.php | 1,527 ▼3 | 18.61 ▲0.46 | 591.61 ▼41.35 | 50.55 ▼3.43 |
Media Library /wp-admin/upload.php | 1,392 ▲1 | 4.18 ▲0.02 | 91.92 ▼5.97 | 40.88 ▼1.69 |
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
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 50% 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 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/wp-frontend-submit/admin/partials/wp-frontend-submit-admin-display.php
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/wp-frontend-submit/public/partials/wp-frontend-submit-public-display.php:20
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that need to be fixed:
- Plugin Name: You should set the name of your plugin on the first line (
=== wp-frontend-submit ===
) - Screenshots: These screenshots have no corresponding images in /assets: #1 (Frontend submit form), #2 (Plugin settings in Customize)
wp-frontend-submit/wp-frontend-submit.php Passed 13 tests
The main file in "WP Frontend Submit" v. 1.0.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
114 characters long description:
Easy to use plugin that enables your visitors and members to submit posts with images from the WordPress frontend.
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,535 lines of code in 17 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 2 | 107 | 12 | 657 |
PHP | 12 | 218 | 591 | 545 |
JavaScript | 2 | 51 | 22 | 225 |
PO File | 1 | 41 | 52 | 108 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.26 |
Average class complexity | 7.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 41.00 |
Average method complexity | 2.35 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 19.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 31 | |
▷ Static methods | 2 | 6.45% |
▷ Public methods | 23 | 74.19% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 8 | 25.81% |
Functions | 5 | |
▷ Named functions | 5 | 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
2 PNG files occupy 0.08MB with 0.05MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 41.80KB | 15.07KB | ▼ 63.95% |
screenshot-2.png | 42.54KB | 16.01KB | ▼ 62.37% |