Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.15ms] Passed 4 tests
A check of server-side resources used by Floating Publish Button
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 41.99 ▼3.06 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 44.66 ▼5.04 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 51.07 ▲1.96 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 79.92 ▼14.69 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 35.00 ▼1.80 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
Browser metrics Passed 4 tests
Floating Publish Button: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲58 | 13.27 ▼1.17 | 4.10 ▲2.48 | 41.04 ▼0.93 |
| Dashboard /wp-admin | 2,210 ▲22 | 4.87 ▼0.96 | 118.70 ▲17.60 | 42.83 ▼2.77 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 2.08 ▲0.06 | 39.56 ▲3.48 | 35.12 ▲1.39 |
| Add New Post /wp-admin/post-new.php | 1,518 ▲4 | 17.69 ▲0.16 | 689.64 ▼16.17 | 54.07 ▼0.91 |
| Media Library /wp-admin/upload.php | 1,392 ▲4 | 4.20 ▼0.04 | 107.42 ▲0.02 | 42.45 ▼1.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
The smoke test was a success, however most plugin functionality was not tested
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
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/floating-publish-button/index.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Tags: You are using too many tags: 16 tag instead of maximum 10
floating-publish-button/index.php 85% from 13 tests
The principal PHP file in "Floating Publish Button" v. 1.0.6 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("floating-publish-button.php" instead of "index.php")
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 148 characters long)
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 detected40 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 10 | 10 | 35 |
| JavaScript | 2 | 2 | 10 | 5 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.13 |
| 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
PNG images were not found in this plugin