Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Please fix the following installer errors
- Install procedure validation failed for this plugin
- > Warning in wp-content/plugins/wp-grass/WpGrass_Plugin.php+36
count(): Parameter must be an array or an object that implements Countable
Server metrics [RAM: ▼2.53MB] [CPU: ▼341.17ms] Passed 4 tests
An overview of server-side resources used by wp grass
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 1.84 ▼1.68 | 4.68 ▼50.07 |
| Dashboard /wp-admin | 1.86 ▼1.55 | 4.04 ▼30.65 |
| Posts /wp-admin/edit.php | 1.86 ▼1.78 | 4.36 ▼38.88 |
| Add New Post /wp-admin/post-new.php | 1.86 ▼5.11 | 5.97 ▼1,245.06 |
| Media Library /wp-admin/upload.php | 1.86 ▼1.44 | 4.22 ▼27.06 |
| WP-Grass /wp-admin/plugins.php?page=WpGrass_PluginSettings | 1.86 | 4.58 |
Server storage [IO: ▲0.58MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 11 new files
Database: no new tables, 3 new options
| New WordPress options |
|---|
| WpGrass_Plugin__installed |
| WpGrass_Plugin_days |
| WpGrass_Plugin__version |
Browser metrics Passed 4 tests
Checking browser requirements for wp grass
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,797 ▲42 | 16.23 ▲0.61 | 7.19 ▲0.33 | 2.73 ▲0.31 |
| Dashboard /wp-admin | 2,899 ▲38 | 6.16 ▲0.00 | 116.01 ▼16.64 | 154.88 ▼2.72 |
| Posts /wp-admin/edit.php | 2,695 ▲1 | 3.36 ▲0.13 | 67.82 ▲3.98 | 155.01 ▲19.54 |
| Add New Post /wp-admin/post-new.php | 1,765 ▲75 | 22.26 ▲1.66 | 423.94 ▲16.09 | 160.90 ▲9.98 |
| Media Library /wp-admin/upload.php | 1,699 ▼2 | 5.54 ▲0.03 | 135.83 ▼1.48 | 195.56 ▲3.53 |
| WP-Grass /wp-admin/plugins.php?page=WpGrass_PluginSettings | 1,036 | 2.37 | 53.37 | 125.21 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin cannot be uninstalled
- > User notice in wp-includes/functions.php+5768
wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the grass-style handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- Zombie WordPress options detected upon uninstall: 3 options
- WpGrass_Plugin__installed
- WpGrass_Plugin__version
- WpGrass_Plugin_days
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Almost there, just fix the following server-side errors
- > GET request to /wp-admin/plugins.php?page=WpGrass_PluginSettings
- > User notice in wp-includes/functions.php+5768
wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the grass-style handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
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 server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/wp-grass/wp-grass.php:48
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
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:
- Donate link: Please fix this invalid url: ""
- Tags: Please add at least on tag
wp-grass/wp-grass.php Passed 13 tests
The main file in "wp grass" v. 0.2.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
57 characters long description:
The grass grows higher while your blog is being inactive.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected474 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 160 | 407 | 458 |
| CSS | 1 | 3 | 0 | 16 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.31 |
| Average class complexity | 13.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 40.00 |
| Average method complexity | 1.73 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 66 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 39 | 59.09% |
| ▷ Protected methods | 27 | 40.91% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 4 | |
| ▷ Named functions | 4 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 4 | 100.00% |
| ▷ Public constants | 4 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.54MB with 0.17MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/wp-grass.png | 553.85KB | 379.96KB | ▼ 31.40% |