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: ▼1.72MB] [CPU: ▼191.61ms] Passed 4 tests
Analyzing server-side resources used by addfreespace
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.94 ▲0.10 | 44.56 ▲4.93 |
Dashboard /wp-admin | 1.93 ▼1.12 | 6.05 ▼31.66 |
Posts /wp-admin/edit.php | 1.93 ▼1.17 | 6.29 ▼40.95 |
Add New Post /wp-admin/post-new.php | 1.93 ▼3.50 | 5.81 ▼665.79 |
Media Library /wp-admin/upload.php | 1.93 ▼1.07 | 7.20 ▼28.03 |
addfreespace /wp-admin/options-general.php?page=addfreespace/addfreespace.php | 1.93 | 6.15 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 7 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
Checking browser requirements for addfreespace
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,692 ▲96 | 15.92 ▲0.39 | 10.05 ▲1.24 | 47.47 ▼1.37 |
Dashboard /wp-admin | 2,986 ▲52 | 6.04 ▼0.09 | 150.43 ▼2.13 | 103.91 ▼16.00 |
Posts /wp-admin/edit.php | 2,752 ▲13 | 2.75 ▲0.06 | 71.17 ▼2.76 | 98.34 ▲0.04 |
Add New Post /wp-admin/post-new.php | 1,615 ▼0 | 18.45 ▼2.64 | 372.78 ▲81.04 | 138.57 ▲27.26 |
Media Library /wp-admin/upload.php | 1,823 ▲13 | 5.09 ▲0.01 | 159.09 ▲6.22 | 123.98 ▲7.91 |
addfreespace /wp-admin/options-general.php?page=addfreespace/addfreespace.php | 1,911 | 2.37 | 65.37 | 113.41 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- This plugin cannot be uninstalled
- > User notice in wp-includes/functions.php+5663
wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=addfreespace/addfreespace.php
- > User notice in wp-includes/functions.php+5663
wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the jquery handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/options-general.php?page=addfreespace/addfreespace.php
- > User notice in wp-includes/functions.php+5663
wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the addfreespace_func1 handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/options-general.php?page=addfreespace/addfreespace.php
- > User notice in wp-includes/functions.php+5663
wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the addfreespace_func2 handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/options-general.php?page=addfreespace/addfreespace.php
- > User notice in wp-includes/functions.php+5663
wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the addfreespace_func3 handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- > GET request to /wp-admin/options-general.php?page=addfreespace/addfreespace.php
- > User notice in wp-includes/functions.php+5663
wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the addfreespace_css handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
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
Please take a closer look at the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/addfreespace/addfreespace.php:33
- > 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 on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that require attention:
- Tags: No tags were detected
- Donate link: Invalid URI found ("")
addfreespace/addfreespace.php Passed 13 tests
The main PHP script in "addfreespace" version 0.1.3 is automatically included on every request by WordPress
121 characters long description:
記事上下に自由な記述ができるフリースペースを加えることができます。You can add freespace.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
No dangerous file extensions were detected1,053 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 3 | 28 | 109 | 547 |
PHP | 2 | 39 | 43 | 485 |
CSS | 1 | 0 | 0 | 21 |
PHP code Passed 2 tests
This is a short overview 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.52 |
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 | 28 | |
▷ Named functions | 28 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.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
PNG images were not found in this plugin