Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼3.38ms] Passed 4 tests
Analyzing server-side resources used by Insert Blocks Before or After Posts Content
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.06 | 36.37 ▼7.57 |
Dashboard /wp-admin | 3.37 ▲0.07 | 43.01 ▼6.14 |
Posts /wp-admin/edit.php | 3.43 ▲0.07 | 47.43 ▲0.38 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 93.34 ▼0.20 |
Media Library /wp-admin/upload.php | 3.30 ▲0.06 | 33.39 ▲1.34 |
Before/after content /wp-admin/themes.php?page=insert-blocks-before-or-after-posts-content | 3.27 | 32.61 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Insert Blocks Before or After Posts Content
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲58 | 13.23 ▼1.17 | 1.55 ▼0.23 | 35.72 ▼9.51 |
Dashboard /wp-admin | 2,204 ▲33 | 5.84 ▼0.21 | 98.76 ▼23.35 | 40.88 ▼4.00 |
Posts /wp-admin/edit.php | 2,096 ▲7 | 2.04 ▲0.05 | 40.38 ▲2.84 | 35.27 ▲1.27 |
Add New Post /wp-admin/post-new.php | 1,536 ▼6 | 23.49 ▲5.10 | 597.10 ▼25.39 | 50.43 ▲0.80 |
Media Library /wp-admin/upload.php | 1,389 ▲7 | 4.30 ▲0.09 | 95.70 ▼9.25 | 43.60 ▼0.26 |
Before/after content /wp-admin/themes.php?page=insert-blocks-before-or-after-posts-content | 1,002 | 2.18 | 22.77 | 28.36 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
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
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 is_admin() in wp-content/plugins/insert-blocks-before-or-after-posts-content/insert-block-before-after-content.php:21
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
9 plugin tags: insert, content, prepend, page, block...
insert-blocks-before-or-after-posts-content/insert-block-before-after-content.php 92% from 13 tests
"Insert Blocks Before or After Posts Content" version 0.3's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("insert-blocks-before-or-after-posts-content.php" instead of "insert-block-before-after-content.php")
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 detected380 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 43 | 39 | 380 |
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.53 |
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 | 10 | |
▷ Named functions | 8 | 80.00% |
▷ Anonymous functions | 2 | 20.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
PNG images were not found in this plugin