Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼11.24ms] Passed 4 tests
An overview of server-side resources used by Japanese font for WordPress(Previously: Japanese Font for TinyMCE)
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 48.62 ▲12.01 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 48.26 ▼10.38 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 45.25 ▼17.16 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 86.00 ▼21.40 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.73 ▲3.97 |
Server storage [IO: ▲0.77MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 31 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| widget_recent-comments |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Japanese font for WordPress(Previously: Japanese Font for TinyMCE)
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,845 ▲99 | 14.35 ▲0.09 | 1.89 ▲0.09 | 42.03 ▲0.76 |
| Dashboard /wp-admin | 2,246 ▲69 | 5.52 ▼0.00 | 84.41 ▼1.19 | 100.84 ▲60.81 |
| Posts /wp-admin/edit.php | 2,148 ▲51 | 2.10 ▲0.15 | 34.47 ▼2.44 | 60.47 ▲23.23 |
| Add New Post /wp-admin/post-new.php | 1,734 ▲208 | 22.48 ▼1.20 | 739.17 ▲73.44 | 62.09 ▼15.40 |
| Media Library /wp-admin/upload.php | 1,439 ▲39 | 4.21 ▼0.05 | 95.65 ▼14.47 | 101.41 ▲52.83 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
Smoke tests 50% 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 0% 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
Please fix the following items
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/japanese-font-for-tinymce/default-font-css.php
- 4× 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/japanese-font-for-tinymce/settings.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/japanese-font-for-tinymce/japanese-tinymce.php:57
- > PHP Notice
Undefined index: fn in wp-content/plugins/japanese-font-for-tinymce/default-font-css.php on line 7
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/japanese-font-for-tinymce/notice.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
6 plugin tags: gutenberg, japanesefont, fonts, tinymce, font...
japanese-font-for-tinymce/japanese-tinymce.php 92% from 13 tests
The entry point to "Japanese font for WordPress(Previously: Japanese Font for TinyMCE)" version 4.28 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("japanese-font-for-tinymce.php" instead of "japanese-tinymce.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected16,593 lines of code in 23 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 2 | 0 | 0 | 15,760 |
| PHP | 6 | 61 | 130 | 447 |
| CSS | 6 | 6 | 6 | 161 |
| JavaScript | 4 | 21 | 36 | 137 |
| Sass | 3 | 9 | 0 | 57 |
| Markdown | 2 | 10 | 0 | 31 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| 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 | 26 | |
| ▷ Named functions | 24 | 92.31% |
| ▷ Anonymous functions | 2 | 7.69% |
| 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 compressed PNG file occupies 0.00MB
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| icon.png | 1.19KB | 1.02KB | ▼ 14.75% |