Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.12ms] Passed 4 tests
An overview of server-side resources used by Tabber Widget
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 54.16 ▲15.19 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 47.40 ▼3.91 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 46.57 ▼3.35 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 82.21 ▼13.50 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 31.74 ▼3.70 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| can_compress_scripts |
| widget_simple_tabber_element |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by Tabber Widget
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,872 ▲111 | 13.42 ▼0.94 | 9.95 ▲7.98 | 43.54 ▲0.89 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.58 ▼0.05 | 95.25 ▲4.10 | 41.17 ▼4.94 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.98 ▲0.02 | 40.16 ▲5.69 | 36.20 ▼1.40 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.05 ▼0.33 | 685.56 ▲35.02 | 55.02 ▼1.71 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.21 ▲0.07 | 95.71 ▼11.81 | 43.20 ▼1.55 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- The uninstall procedure has failed, leaving 7 options in the database
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- widget_simple_tabber_element
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
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
Good news, no errors were detected
SRP 50% 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
Almost there! Just fix the following items
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/simple-tabber-widget/plugin-functions.php:16
- > 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
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Simple Tabber Widget on your site.), #2 (Simple Tabber Widget on wordpress widget page.)
simple-tabber-widget/plugin-functions.php 92% from 13 tests
The entry point to "Tabber Widget" version 2.0 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("simple-tabber-widget.php" instead of "plugin-functions.php")
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
No dangerous file extensions were detected146 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 20 | 31 | 79 |
| CSS | 1 | 1 | 0 | 53 |
| JavaScript | 1 | 0 | 1 | 14 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.12 |
| Average class complexity | 2.00 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 2.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 | 3 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 3 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| Screenshot-1.png | 11.95KB | 6.49KB | ▼ 45.67% |
| Screenshot-2.png | 9.25KB | 5.45KB | ▼ 41.15% |