Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.05MB] [CPU: ▼7.88ms] Passed 4 tests
An overview of server-side resources used by Ojama Flying Sankocho
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.52 ▲0.06 | 37.66 ▼2.39 |
Dashboard /wp-admin | 3.36 ▲0.02 | 46.10 ▼12.21 |
Posts /wp-admin/edit.php | 3.48 ▲0.12 | 43.22 ▼3.39 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.06 | 81.74 ▼13.53 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 37.86 ▲3.04 |
Flying Sankocho plugin Option /wp-admin/options-general.php?page=flyjpf_plugin_options | 3.23 | 32.12 |
Server storage [IO: ▲0.22MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 11 new files
Database: no new tables, 7 new options
New WordPress options |
---|
flying_sankocho_option |
db_upgraded |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Ojama Flying Sankocho
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,906 ▲160 | 13.79 ▼0.56 | 9.63 ▲7.97 | 37.85 ▼4.38 |
Dashboard /wp-admin | 2,202 ▲32 | 5.57 ▼0.08 | 84.22 ▼19.06 | 37.30 ▼2.39 |
Posts /wp-admin/edit.php | 2,104 ▲1 | 2.02 ▼0.02 | 35.77 ▼5.38 | 31.32 ▼2.48 |
Add New Post /wp-admin/post-new.php | 1,534 ▲8 | 23.19 ▲0.14 | 606.29 ▼24.06 | 55.25 ▼6.36 |
Media Library /wp-admin/upload.php | 1,401 ▲4 | 4.19 ▼0.01 | 106.82 ▲5.37 | 44.51 ▲0.55 |
Flying Sankocho plugin Option /wp-admin/options-general.php?page=flyjpf_plugin_options | 899 | 2.15 | 26.33 | 34.03 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- Uninstall procedure had uncaught errors
- > Deprecated in wp-includes/class-wp-hook.php+310
Non-static method Ojama_Flying_sankocho::at_uninstall() should not be called statically
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=flyjpf_plugin_options
- > Notice in wp-content/plugins/ojama-flying-sankocho/flying_jpf.php+265
Undefined index: HTTP_ACCEPT_LANGUAGE
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/ojama-flying-sankocho/flying_jpf.php:55
- > 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 90% from 29 tests
readme.txt 88% from 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
Attributes that need to be fixed:
- Donate link: Invalid URI found ("")
- Screenshots: These screenshots do not have images: #1 (Japanese Paradise Flycatcher.), #2 (Option page english.)
ojama-flying-sankocho/flying_jpf.php 92% from 13 tests
The main file in "Ojama Flying Sankocho" v. 1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("ojama-flying-sankocho.php" instead of "flying_jpf.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected870 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 1 | 32 | 28 | 580 |
PHP | 1 | 43 | 43 | 245 |
CSS | 1 | 5 | 0 | 45 |
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.26 |
Average class complexity | 33.00 |
▷ Minimum class complexity | 33.00 |
▷ Maximum class complexity | 33.00 |
Average method complexity | 3.13 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 15 | |
▷ Static methods | 1 | 6.67% |
▷ Public methods | 11 | 73.33% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 4 | 26.67% |
Functions | 1 | |
▷ Named functions | 1 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
3 compressed PNG files occupy 0.09MB
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
san1.png | 29.30KB | 30.77KB | 0.00% |
san0.png | 40.49KB | 43.11KB | 0.00% |
moon.png | 17.27KB | 18.53KB | 0.00% |