Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.46MB] [CPU: ▼5.77ms] Passed 4 tests
Analyzing server-side resources used by Spider Analyser - WordPress搜索引擎蜘蛛分析插件
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.94 ▲0.47 | 42.71 ▼1.13 |
Dashboard /wp-admin | 3.79 ▲0.44 | 53.53 ▼10.16 |
Posts /wp-admin/edit.php | 3.90 ▲0.54 | 47.99 ▼2.46 |
Add New Post /wp-admin/post-new.php | 6.37 ▲0.48 | 82.73 ▼9.34 |
Media Library /wp-admin/upload.php | 3.71 ▲0.48 | 38.43 ▲8.22 |
Server storage [IO: ▲2.04MB] [DB: ▲0.01MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 40 new files
Database: 7 new tables, 8 new options
New tables |
---|
wp_wb_spider_post |
wp_wb_spider_visit |
wp_wb_spider_log |
wp_wb_spider_post_link |
wp_wb_spider |
wp_wb_spider_ip |
wp_wb_spider_sum |
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
wb_spider_analyser_db_ver |
widget_theysaidso_widget |
sync_wb_spider |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Spider Analyser - WordPress搜索引擎蜘蛛分析插件
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,843 ▲97 | 14.26 ▼0.17 | 1.72 ▲0.01 | 43.12 ▼2.90 |
Dashboard /wp-admin | 2,249 ▲75 | 5.52 ▼0.05 | 85.75 ▼1.81 | 89.93 ▲48.80 |
Posts /wp-admin/edit.php | 2,154 ▲54 | 2.00 ▲0.05 | 35.12 ▼2.47 | 41.59 ▲4.56 |
Add New Post /wp-admin/post-new.php | 1,567 ▲39 | 23.48 ▲0.45 | 742.89 ▲82.18 | 53.92 ▲0.22 |
Media Library /wp-admin/upload.php | 1,448 ▲48 | 4.19 ▲0.02 | 95.65 ▼8.75 | 83.42 ▲36.90 |
文章爬取 /wp-admin/admin.php?page=wp_spider_analyser#/post | 1,758 | 6.59 | 90.44 | 159.64 |
插件设置 /wp-admin/admin.php?page=wp_spider_analyser#/setting | 1,641 | 6.27 | 77.89 | 128.36 |
访问路径 /wp-admin/admin.php?page=wp_spider_analyser#/path | 1,329 | 8.46 | 169.36 | 102.97 |
蜘蛛日志 /wp-admin/admin.php?page=wp_spider_analyser#/log | 1,723 | 7.01 | 77.11 | 109.14 |
蜘蛛列表 /wp-admin/admin.php?page=wp_spider_analyser#/list | 1,678 | 6.66 | 83.03 | 118.66 |
蜘蛛概况 /wp-admin/admin.php?page=wp_spider_analyser#/home | 1,369 | 10.81 | 180.24 | 97.24 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Zombie tables were found after uninstall: 7 tables
- wp_wb_spider_post
- wp_wb_spider_sum
- wp_wb_spider_ip
- wp_wb_spider_visit
- wp_wb_spider_log
- wp_wb_spider
- wp_wb_spider_post_link
- This plugin did not uninstall successfully, leaving 8 options in the database
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- wb_spider_analyser_db_ver
- sync_wb_spider
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP Passed 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
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% 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
9 plugin tags: mj12bot, bytespider, googlebot, semrushbot, spider analyser...
spider-analyser/index.php 85% from 13 tests
"Spider Analyser - WordPress搜索引擎蜘蛛分析插件" version 1.3.11's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("spider-analyser.php" instead of "index.php")
- Description: Keep the plugin description shorter than 140 characters (currently 198 characters long)
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected3,196 lines of code in 35 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 13 | 600 | 198 | 3,094 |
SQL | 1 | 17 | 6 | 73 |
JavaScript | 18 | 2 | 53 | 26 |
CSS | 2 | 0 | 3 | 2 |
SVG | 1 | 0 | 0 | 1 |
PHP code 50% from 2 tests
This plugin's cyclomatic complexity and code structure detailed below
These items need your attention
- Method cyclomatic complexity should be reduced to less than 100 (currently 295)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.49 |
Average class complexity | 364.50 |
▷ Minimum class complexity | 69.00 |
▷ Maximum class complexity | 660.00 |
Average method complexity | 13.22 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 295.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 60 | |
▷ Static methods | 60 | 100.00% |
▷ Public methods | 59 | 98.33% |
▷ Protected methods | 1 | 1.67% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 3 | 100.00% |
Constants | 4 | |
▷ Global constants | 4 | 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
1 compressed PNG file occupies 0.03MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
tpl/assets/img/icons.abf3bf80.png | 28.97KB | 28.95KB | 0.06% |