Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.25MB] [CPU: ▼0.27ms] Passed 4 tests
Analyzing server-side resources used by 内链tag标签
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.70 ▲0.23 | 35.82 ▼6.99 |
| Dashboard /wp-admin | 3.56 ▲0.26 | 48.77 ▲1.56 |
| Posts /wp-admin/edit.php | 3.68 ▲0.32 | 52.01 ▲2.13 |
| Add New Post /wp-admin/post-new.php | 6.15 ▲0.25 | 97.70 ▲2.21 |
| Media Library /wp-admin/upload.php | 3.49 ▲0.25 | 36.85 ▲3.13 |
Server storage [IO: ▲0.75MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 21 new files
Database: 2 new tables, 7 new options
| New tables |
|---|
| wp_baiduseo_neilian |
| wp_baiduseo_long |
| New WordPress options |
|---|
| widget_recent-comments |
| tagmanage_tongji |
| can_compress_scripts |
| db_upgraded |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for 内链tag标签
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲44 | 14.34 ▲0.00 | 1.75 ▼0.13 | 38.69 ▼5.86 |
| Dashboard /wp-admin | 2,214 ▲33 | 5.62 ▼0.07 | 91.23 ▼15.49 | 44.63 ▲3.73 |
| Posts /wp-admin/edit.php | 2,116 ▲16 | 1.95 ▲0.00 | 38.76 ▲2.36 | 40.52 ▲3.94 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲13 | 23.38 ▲0.22 | 622.09 ▼80.95 | 58.98 ▲8.83 |
| Media Library /wp-admin/upload.php | 1,419 ▲19 | 4.21 ▼0.03 | 99.59 ▼0.28 | 46.33 ▲1.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- The plugin did not uninstall successfully, leaving 2 tables in the database
- wp_baiduseo_neilian
- wp_baiduseo_long
- Zombie WordPress options detected upon uninstall: 7 options
- can_compress_scripts
- tagmanage_tongji
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- 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
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
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 plugin_dir_path() in wp-content/plugins/nleilian-guanjc/tagmanage.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/nleilian-guanjc/tagmanage_html.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
1 plugin tags: tag
nleilian-guanjc/tagmanage.php 92% from 13 tests
The main PHP script in "内链tag标签" version 0.2.3 is automatically included on every request by WordPress
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("nleilian-guanjc.php" instead of "tagmanage.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected8,330 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 1 | 0 | 47 | 4,770 |
| PHP | 3 | 218 | 81 | 2,372 |
| CSS | 1 | 54 | 44 | 1,188 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.66 |
| 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 | 27 | |
| ▷ Named functions | 27 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 2 | 100.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
13 PNG files occupy 0.27MB with 0.16MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| image/bangzhushuoming.png | 4.19KB | 1.64KB | ▼ 60.98% |
| image/wzbbx.png | 81.06KB | 28.41KB | ▼ 64.95% |
| image/baiduchajian.png | 78.89KB | 38.25KB | ▼ 51.51% |
| image/guanbi.png | 4.12KB | 1.46KB | ▼ 64.64% |
| image/weixingzh.png | 13.00KB | 5.76KB | ▼ 55.68% |