Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼5.81ms] Passed 4 tests
Server-side resources used by Mayuko Footer Tag Manager
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 40.50 ▲1.08 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 46.90 ▼14.33 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.81 ▼1.06 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 88.31 ▼8.91 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.11 ▲2.01 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-posts |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Mayuko Footer Tag Manager
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.37 ▼0.16 | 1.77 ▲0.22 | 46.22 ▲5.57 |
| Dashboard /wp-admin | 2,189 ▲9 | 5.54 ▼0.10 | 85.64 ▼5.09 | 37.44 ▼5.25 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.99 ▲0.00 | 37.59 ▲0.46 | 30.15 ▼6.02 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼3 | 23.03 ▼0.02 | 604.10 ▲8.41 | 47.75 ▼21.29 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.23 ▲0.03 | 100.24 ▼4.32 | 44.43 ▼9.79 |
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: 6 options
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 1× 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/mayuko-footer-tag-manager/navicast.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need to be fixed:
- Screenshots: Screenshot #1 (管理画面上の`設定`>`表示設定`から、表示させるHTMLタグを設定し、保存します。) image not found
mayuko-footer-tag-manager/navicast.php 92% from 13 tests
"Mayuko Footer Tag Manager" version 0.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("mayuko-footer-tag-manager.php" instead of "navicast.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
Everything looks great! No dangerous files found in this plugin1 line of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.17 |
| 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 | 3 | |
| ▷ Named functions | 3 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 33.13KB | 12.30KB | ▼ 62.88% |