Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼4.26ms] Passed 4 tests
An overview of server-side resources used by WP Steps
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.01 | 37.72 ▼4.04 |
| Dashboard /wp-admin | 3.35 ▼0.03 | 46.62 ▼13.20 |
| Posts /wp-admin/edit.php | 3.40 ▲0.01 | 51.35 ▲7.64 |
| Add New Post /wp-admin/post-new.php | 5.93 ▲0.01 | 91.68 ▼1.66 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.01 | 36.26 ▲1.88 |
Server storage [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: no files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP Steps
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,803 ▲57 | 13.35 ▼0.90 | 1.54 ▼0.10 | 43.09 ▲2.10 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.80 ▼1.11 | 117.16 ▲15.76 | 54.51 ▲14.33 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▼0.01 | 43.81 ▲6.71 | 37.89 ▲3.53 |
| Add New Post /wp-admin/post-new.php | 1,531 ▲12 | 18.07 ▼5.21 | 614.99 ▼17.80 | 65.53 ▲18.57 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.20 ▲0.08 | 92.71 ▼10.49 | 41.86 ▼3.48 |
Uninstaller [IO: ✅] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
Please fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/wp-steps/wp-steps.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
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
These attributes need your attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (In Editor Codeview you see a button named `wpsteps`. If you press this button it will insert the shortcode.), #2 (This is how a setup may look.)
- Tags: Too many tags (15 tag instead of maximum 10); only the first 5 tags are used in your directory listing
wp-steps/wp-steps.php Passed 13 tests
"WP Steps" version 1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
83 characters long description:
WP Steps shows your content step by step. There is no limit how many steps you use.
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
Good job! No executable or dangerous file extensions detected73 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 4 | 12 | 58 |
| JavaScript | 1 | 0 | 0 | 15 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.47 |
| 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 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG files were detected