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.01MB] [CPU: ▼3.66ms] Passed 4 tests
This is a short check of server-side resources used by Vivet Widget
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 34.48 ▼1.78 |
| Dashboard /wp-admin | 3.32 ▼0.02 | 45.28 ▼15.24 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 44.36 ▲1.27 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 84.00 ▲1.11 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.10 ▲2.08 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 8 new files
Database: 1 new table, 6 new options
| New tables |
|---|
| wp_vivet_app_widget |
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Vivet Widget
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,837 ▲91 | 14.26 ▼0.09 | 2.24 ▲0.73 | 38.63 ▼2.29 |
| Dashboard /wp-admin | 2,212 ▲31 | 5.53 ▼0.10 | 85.18 ▼17.91 | 74.48 ▲31.83 |
| Posts /wp-admin/edit.php | 2,129 ▲29 | 1.96 ▼0.01 | 36.28 ▲1.40 | 38.73 ▲3.38 |
| Add New Post /wp-admin/post-new.php | 1,399 ▼132 | 21.57 ▼1.53 | 582.85 ▼42.85 | 174.97 ▲115.88 |
| Media Library /wp-admin/upload.php | 1,429 ▲26 | 4.25 ▲0.12 | 97.95 ▼5.56 | 45.27 ▲2.09 |
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
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% 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
Almost there! Just fix the following items
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to a member function get_results() on null in wp-content/plugins/vivet-widget/admin/admin_landing.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/vivet-widget/vivet_app_widget.php:18
- > PHP Notice
Trying to get property 'prefix' of non-object in wp-content/plugins/vivet-widget/admin/admin_landing.php on line 3
- > 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 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
4 plugin tags: widget, vivetapp, vivet, landing
vivet-widget/vivet_app_widget.php 92% from 13 tests
"Vivet Widget" version 1.0.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("vivet-widget.php" instead of "vivet_app_widget.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Success! There were no dangerous files found in this plugin109 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 20 | 9 | 106 |
| CSS | 1 | 0 | 0 | 3 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.07 |
| Average class complexity | 1.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 1.00 |
| Average method complexity | 1.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 1.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 6 | |
| ▷ Static methods | 6 | 100.00% |
| ▷ Public methods | 6 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.05MB with 0.02MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| public/img/logo_plugin_wp.png | 46.43KB | 11.69KB | ▼ 74.83% |
| public/img/icon.png | 0.47KB | 0.46KB | ▼ 1.25% |