Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼7.32ms] Passed 4 tests
Server-side resources used by Stepped Content - Showcase Stepped Content
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.06 | 43.18 ▼7.57 |
Dashboard /wp-admin | 3.35 ▲0.00 | 51.01 ▼15.03 |
Posts /wp-admin/edit.php | 3.40 ▲0.04 | 51.43 ▲1.85 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.05 | 93.39 ▼8.54 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 41.45 ▲7.07 |
Server storage [IO: ▲0.48MB] [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: 24 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Stepped Content - Showcase Stepped Content
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,850 ▲89 | 13.57 ▼0.86 | 11.00 ▲9.40 | 39.94 ▲1.55 |
Dashboard /wp-admin | 2,195 ▲18 | 5.66 ▼0.06 | 92.06 ▼6.24 | 43.70 ▼0.26 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 2.04 ▼0.09 | 39.85 ▲0.85 | 35.48 ▲0.22 |
Add New Post /wp-admin/post-new.php | 6,373 ▲4,838 | 27.93 ▲4.61 | 905.54 ▲236.19 | 42.88 ▼12.72 |
Media Library /wp-admin/upload.php | 1,397 ▼6 | 4.20 ▲0.01 | 113.66 ▲15.06 | 47.51 ▲5.10 |
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
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- 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
Even though everything seems fine, this is not 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
Please fix the following
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Warning
Use of undefined constant STP_PLUGIN_VERSION - assumed 'STP_PLUGIN_VERSION' (this will throw an Error in a future version of PHP) in wp-content/plugins/stepped-content/dist/editor.asset.php on line 3
- > PHP Warning
Use of undefined constant STP_PLUGIN_VERSION - assumed 'STP_PLUGIN_VERSION' (this will throw an Error in a future version of PHP) in wp-content/plugins/stepped-content/dist/script.asset.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/stepped-content/child/child.php:4
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Requires at least: Invalid version format
stepped-content/index.php 92% from 13 tests
The entry point to "Stepped Content - Showcase Stepped Content" version 1.0.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("stepped-content.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected319 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 4 | 0 | 0 | 144 |
PO File | 1 | 37 | 80 | 96 |
PHP | 4 | 21 | 16 | 75 |
CSS | 3 | 0 | 6 | 3 |
JavaScript | 2 | 0 | 3 | 1 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.05 |
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 | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 7 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 7 | 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 | 2 | |
▷ Global constants | 2 | 100.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
There were not PNG files found in your plugin