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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.13MB] [CPU: ▼4.26ms] Passed 4 tests
Server-side resources used by Append or Prepend Content
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.56 ▲0.10 | 43.10 ▲0.95 |
Dashboard /wp-admin | 3.43 ▲0.13 | 48.84 ▼1.30 |
Posts /wp-admin/edit.php | 3.54 ▲0.19 | 44.78 ▼2.99 |
Add New Post /wp-admin/post-new.php | 6.07 ▲0.18 | 85.79 ▼13.69 |
Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 36.99 ▲2.03 |
Append or Prepend Content /wp-admin/edit.php?post_type=append_or_prepend | 3.39 | 38.35 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 20 new files
Database: no new tables, 7 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
app_or_prep_version |
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Append or Prepend Content
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,829 ▲83 | 13.22 ▼1.53 | 2.28 ▲0.35 | 41.77 ▼0.63 |
Dashboard /wp-admin | 2,213 ▲24 | 5.85 ▼0.22 | 100.90 ▼23.92 | 41.98 ▼3.84 |
Posts /wp-admin/edit.php | 2,090 ▲1 | 2.01 ▼0.00 | 37.33 ▼0.95 | 37.56 ▲1.44 |
Add New Post /wp-admin/post-new.php | 1,536 ▲8 | 23.34 ▲5.06 | 682.81 ▲58.32 | 54.98 ▼4.93 |
Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.21 ▼0.08 | 98.68 ▼0.82 | 44.05 ▲0.71 |
Append or Prepend Content /wp-admin/edit.php?post_type=append_or_prepend | 1,057 | 1.95 | 32.92 | 31.04 |
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
- Zombie WordPress options were found after uninstall: 7 options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- app_or_prep_version
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function AppOrPrepend\\plugin_dir_path() in wp-content/plugins/append-or-prepend-content/app-prep-content.php:29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
3 plugin tags: content, posts, custom post type
append-or-prepend-content/app-prep-content.php 85% from 13 tests
The main file in "Append or Prepend Content" v. 2.1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("append-or-prepend-content.php" instead of "app-prep-content.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected632 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 8 | 79 | 124 | 362 |
JavaScript | 7 | 18 | 0 | 166 |
PO File | 1 | 35 | 38 | 104 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.23 |
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 | 6 | |
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 | 24 | |
▷ Named functions | 23 | 95.83% |
▷ Anonymous functions | 1 | 4.17% |
Constants | 7 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 7 | 100.00% |
▷ Public constants | 7 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There are no PNG files in this plugin