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.00MB] [CPU: ▼10.37ms] Passed 4 tests
A check of server-side resources used by FoodParser
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 36.83 ▼4.78 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 41.39 ▼18.91 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.66 ▲1.73 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 78.07 ▼15.39 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.04 ▼2.40 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for FoodParser
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,802 ▲56 | 13.28 ▼1.10 | 5.31 ▲3.49 | 42.59 ▼2.49 |
| Dashboard /wp-admin | 2,203 ▲15 | 4.88 ▼0.00 | 110.89 ▼0.00 | 43.07 ▼2.26 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▲0.04 | 40.46 ▲2.02 | 34.72 ▲1.02 |
| Add New Post /wp-admin/post-new.php | 1,521 ▲2 | 23.08 ▼0.27 | 665.41 ▲3.92 | 62.39 ▼0.77 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.20 ▼0.05 | 93.34 ▼19.25 | 40.40 ▼7.10 |
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
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
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
Please fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/foodparser/foodparser-add-button.php:14
- > 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 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== foodparser ===)
foodparser/foodparser-add-button.php 92% from 13 tests
The main PHP file in "FoodParser" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("foodparser.php" instead of "foodparser-add-button.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin310 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 7 | 5 | 248 |
| CSS | 1 | 2 | 0 | 34 |
| PHP | 1 | 13 | 24 | 28 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.07 |
| 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 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 compressed PNG file occupies 0.01MB
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| foodparser-pear.png | 6.44KB | 6.76KB | 0.00% |