Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.19MB] [CPU: ▼3.68ms] Passed 4 tests
Analyzing server-side resources used by Wrapping ShortCode
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.65 ▲0.19 | 43.89 ▲2.84 |
Dashboard /wp-admin | 3.48 ▲0.18 | 50.48 ▼2.93 |
Posts /wp-admin/edit.php | 3.59 ▲0.24 | 47.10 ▼1.31 |
Add New Post /wp-admin/post-new.php | 6.08 ▲0.19 | 86.64 ▼8.28 |
Media Library /wp-admin/upload.php | 3.41 ▲0.18 | 36.80 ▼2.20 |
Server storage [IO: ▲1.02MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Wrapping ShortCode: an overview of browser usage
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,027 ▲281 | 21.65 ▲7.28 | 45.56 ▲43.72 | 42.16 ▼1.32 |
Dashboard /wp-admin | 2,288 ▲114 | 9.64 ▲4.76 | 137.70 ▲22.37 | 42.26 ▼8.58 |
Posts /wp-admin/edit.php | 2,164 ▲78 | 9.24 ▲7.22 | 68.46 ▲32.08 | 31.35 ▼2.42 |
Add New Post /wp-admin/post-new.php | 6,437 ▲4,903 | 20.61 ▼2.61 | 897.43 ▲204.55 | 37.50 ▼17.01 |
Media Library /wp-admin/upload.php | 1,482 ▲94 | 10.99 ▲6.81 | 126.86 ▲20.32 | 41.51 ▼9.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
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
Even though no errors were found, 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
- 4× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'Asm_Wrapping_ShortCode\\Base' not found in wp-content/plugins/wrapping-shortcode/classes/class-shortcode-metaloop.php:25
- > PHP Fatal error
Uncaught Error: Class 'Asm_Wrapping_ShortCode\\Base' not found in wp-content/plugins/wrapping-shortcode/classes/class-template.php:26
- > PHP Fatal error
Uncaught Error: Class 'Asm_Wrapping_ShortCode\\Base' not found in wp-content/plugins/wrapping-shortcode/classes/class-shortcode-commentout.php:23
- > PHP Fatal error
Uncaught Error: Class 'Asm_Wrapping_ShortCode\\Base' not found in wp-content/plugins/wrapping-shortcode/classes/class-enqueue.php:23
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 86% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
7 plugin tags: group, shortcode, asumaru, block, commentout...
wrapping-shortcode/asm-wrapping-shortcode-block.php 69% from 13 tests
Analyzing the main PHP file in "Wrapping ShortCode" version 0.1.0
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wrapping-shortcode.php" instead of "asm-wrapping-shortcode-block.php")
- Domain Path: You should use only dashes and lowercase characters for the domain path ("(default) // Changed from 'languages'")
- Domain Path: The domain path should be prefixed with a forward slash character ("/(default) // Changed from 'languages'")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
No dangerous file extensions were detected28,771 lines of code in 21 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 4 | 0 | 0 | 27,721 |
PHP | 8 | 69 | 557 | 827 |
JavaScript | 5 | 26 | 142 | 175 |
Sass | 2 | 5 | 0 | 46 |
CSS | 2 | 0 | 0 | 2 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 15.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 39.00 |
Average method complexity | 3.15 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 22.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 6 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 6 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 40 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 33 | 82.50% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 7 | 17.50% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.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