Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.14MB] [CPU: ▼6.46ms] Passed 4 tests
A check of server-side resources used by Floating Action Button
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 37.21 ▼1.40 |
| Dashboard /wp-admin | 3.48 ▲0.18 | 48.36 ▼8.87 |
| Posts /wp-admin/edit.php | 3.56 ▲0.20 | 47.43 ▲1.72 |
| Add New Post /wp-admin/post-new.php | 6.11 ▲0.23 | 75.58 ▼13.76 |
| Media Library /wp-admin/upload.php | 3.34 ▲0.11 | 31.10 ▼1.82 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 19 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Floating Action Button
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,999 ▲253 | 14.77 ▲0.39 | 2.11 ▲0.42 | 43.42 ▲0.04 |
| Dashboard /wp-admin | 2,383 ▲195 | 6.68 ▲0.78 | 123.19 ▲8.80 | 36.79 ▼7.87 |
| Posts /wp-admin/edit.php | 2,286 ▲197 | 3.56 ▲1.55 | 55.67 ▲20.28 | 35.13 ▼0.93 |
| Add New Post /wp-admin/post-new.php | 1,544 ▲22 | 23.41 ▲0.44 | 594.09 ▼38.15 | 36.31 ▼8.99 |
| Media Library /wp-admin/upload.php | 1,419 ▲31 | 4.27 ▲0.10 | 83.43 ▼15.43 | 41.76 ▼4.28 |
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
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following
- 3× 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/floating-action-button/views/settings.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/floating-action-button/index.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/floating-action-button/views/fab-button.php:3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Tags: Please delete some tags, you are using 12 tag instead of maximum 10
floating-action-button/index.php 92% from 13 tests
The main PHP file in "Floating Action Button" ver. 1.2.2 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("floating-action-button.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected919 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 36 | 14 | 723 |
| CSS | 2 | 2 | 0 | 101 |
| JavaScript | 3 | 11 | 0 | 95 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| 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 | 10 | |
| ▷ Named functions | 3 | 30.00% |
| ▷ Anonymous functions | 7 | 70.00% |
| Constants | 5 | |
| ▷ Global constants | 5 | 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
10 PNG files occupy 0.04MB with 0.01MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/img/viber.png | 2.54KB | 2.62KB | 0.00% |
| assets/img/phone.png | 5.11KB | 2.39KB | ▼ 53.17% |
| assets/img/email.png | 4.80KB | 2.66KB | ▼ 44.62% |
| assets/img/intercom.png | 5.16KB | 3.12KB | ▼ 39.65% |
| assets/img/messenger.png | 2.92KB | 1.87KB | ▼ 35.88% |