Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▼0.91MB] [CPU: ▼33.38ms] Passed 4 tests
Analyzing server-side resources used by aoringo TAG upper
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.04 | 36.34 ▼1.93 |
Dashboard /wp-admin | 3.04 ▼0.27 | 22.79 ▼27.74 |
Posts /wp-admin/edit.php | 3.04 ▼0.32 | 25.88 ▼23.33 |
Add New Post /wp-admin/post-new.php | 3.04 ▼2.85 | 23.92 ▼70.66 |
Media Library /wp-admin/upload.php | 3.04 ▼0.20 | 22.96 ▼11.79 |
aoringo TAG upperの設定 /wp-admin/options-general.php?page=aoringo-tag-upper/aoringo_tag_upper.php | 3.04 | 24.09 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 10 new options
New WordPress options |
---|
widget_recent-posts |
tagtag_ng |
widget_theysaidso_widget |
db_upgraded |
tagtag_rendo |
can_compress_scripts |
tagtagjidou |
aoringotag_installed |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for aoringo TAG upper
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲58 | 13.31 ▼1.12 | 3.66 ▲2.11 | 38.16 ▼2.76 |
Dashboard /wp-admin | 2,210 ▲25 | 5.91 ▲0.10 | 98.01 ▼2.89 | 45.28 ▲6.02 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.01 ▼0.00 | 34.45 ▼3.85 | 35.60 ▼0.59 |
Add New Post /wp-admin/post-new.php | 1,536 ▲17 | 23.34 ▼0.05 | 656.55 ▼21.40 | 63.99 ▼1.61 |
Media Library /wp-admin/upload.php | 1,389 ▼2 | 4.21 ▼0.01 | 92.51 ▼5.13 | 44.76 ▲0.78 |
aoringo TAG upperの設定 /wp-admin/options-general.php?page=aoringo-tag-upper/aoringo_tag_upper.php | 936 | 2.17 | 22.80 | 106.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- The plugin did not uninstall gracefully
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Almost there, just fix the following server-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=aoringo-tag-upper/aoringo_tag_upper.php
- > User deprecated in wp-includes/functions.php+5737
Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
- 3 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=aoringo-tag-upper/aoringo_tag_upper.php
- > Notice in wp-content/plugins/aoringo-tag-upper/aoringo_tag_upper.php+139
Undefined index: posted
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/aoringo-tag-upper/aoringo_tag_upper.php:96
- > PHP Fatal error
Uncaught Error: Call to undefined function delete_option() in wp-content/plugins/aoringo-tag-upper/uninstall.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
2 plugin tags: tags, tag
aoringo-tag-upper/aoringo_tag_upper.php 92% from 13 tests
The main file in "aoringo TAG upper" v. 0.1.6 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:
- Main file name: Name the main plugin file the same as the plugin slug ("aoringo-tag-upper.php" instead of "aoringo_tag_upper.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected259 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 12 | 26 | 259 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
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 | 4 | |
▷ Named functions | 4 | 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
There were not PNG files found in your plugin