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.07MB] [CPU: ▼8.40ms] Passed 4 tests
An overview of server-side resources used by azurecurve Display After Post Content
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 37.78 ▼1.39 |
| Dashboard /wp-admin | 3.37 ▲0.07 | 46.42 ▼0.01 |
| Posts /wp-admin/edit.php | 3.42 ▲0.06 | 41.93 ▼4.46 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 78.99 ▼27.74 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 37.23 ▲6.42 |
| Display After Post Content /wp-admin/admin.php?page=azc-dapc | 3.23 | 29.31 |
| Plugins /wp-admin/admin.php?page=azc-plugin-menus | 3.26 | 32.10 |
Server storage [IO: ▲0.03MB] [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: 8 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
| azc_dapc_options |
| db_upgraded |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for azurecurve Display After Post Content
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,855 ▲109 | 13.32 ▼1.26 | 1.93 ▲0.25 | 40.56 ▼5.84 |
| Dashboard /wp-admin | 2,237 ▲46 | 5.88 ▼0.02 | 97.61 ▼5.30 | 82.67 ▲40.81 |
| Posts /wp-admin/edit.php | 2,117 ▲46 | 2.01 ▲0.00 | 34.94 ▼4.91 | 31.08 ▼6.17 |
| Add New Post /wp-admin/post-new.php | 1,690 ▲176 | 20.27 ▲2.67 | 707.66 ▲85.26 | 45.33 ▼7.87 |
| Media Library /wp-admin/upload.php | 1,416 ▲28 | 4.18 ▲0.01 | 106.94 ▲10.69 | 46.93 ▲4.94 |
| Display After Post Content /wp-admin/admin.php?page=azc-dapc | 836 | 2.02 | 24.48 | 28.29 |
| Plugins /wp-admin/admin.php?page=azc-plugin-menus | 850 | 2.03 | 26.46 | 29.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These errors were triggered by the plugin
- > GET request to /wp-admin/admin.php?page=azc-dapc
- > Notice in wp-content/plugins/azurecurve-display-after-post-content/azurecurve-display-after-post-content.php+159
Undefined index: display_after_post_content
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
The following issues need your attention
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/azurecurve-display-after-post-content/includes/menu.php:29
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/azurecurve-display-after-post-content/includes/menu.php:29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
4 plugin tags: index, classicpress, post, wordpress
azurecurve-display-after-post-content/azurecurve-display-after-post-content.php 85% from 13 tests
The main file in "azurecurve Display After Post Content" v. 2.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 174 characters long)
- 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 | An overview of files in this plugin; executable files are not allowed
Everything looks great! No dangerous files found in this plugin421 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 68 | 61 | 402 |
| CSS | 2 | 0 | 4 | 19 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.59 |
| 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 | 15 | |
| ▷ Named functions | 15 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 compressed PNG file occupies 0.00MB
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/Favicon-16x16.png | 0.40KB | 0.34KB | ▼ 14.81% |