Benchmarks
Plugin footprint 65% 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.78MB] [CPU: ▲1.17ms] 75% from 4 tests
This is a short check of server-side resources used by Floating Awesome Button (Sticky Button & Popup) - CTA, Back to Top, Shortcodes, Widget, & More
The following require your attention
- CPU: You should keep total CPU usage under 500.00ms (currently 1,845.46ms on /wp-admin/options-general.php?page=floating-awesome-button-setting)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.30 ▲0.84 | 45.68 ▲4.24 |
Dashboard /wp-admin | 4.08 ▲0.78 | 52.92 ▼5.09 |
Posts /wp-admin/edit.php | 4.12 ▲0.77 | 53.06 ▲3.21 |
Add New Post /wp-admin/post-new.php | 6.69 ▲0.80 | 98.43 ▲2.31 |
Media Library /wp-admin/upload.php | 4.01 ▲0.78 | 49.48 ▲13.89 |
Add New /wp-admin/post-new.php?post_type=fab | 6.69 | 95.79 |
Floating Awesome Button /wp-admin/options-general.php?page=floating-awesome-button-setting | 4.36 | 1,845.46 |
FAB /wp-admin/edit.php?post_type=fab | 4.05 | 44.00 |
Freemius Debug [v.2.5.2] /wp-admin/admin.php?page=freemius | 4.34 | 44.08 |
Server storage [IO: ▲5.48MB] [DB: ▲0.08MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 349 new files
Database: no new tables, 11 new options
New WordPress options |
---|
fab_config |
widget_theysaidso_widget |
fs_active_plugins |
fs_debug_mode |
fs_accounts |
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
... |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Floating Awesome Button (Sticky Button & Popup) - CTA, Back to Top, Shortcodes, Widget, & More
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,009 ▲248 | 13.87 ▼0.48 | 14.65 ▲12.90 | 27.67 ▼9.38 |
Dashboard /wp-admin | 2,255 ▲78 | 5.81 ▲0.22 | 82.90 ▼11.15 | 101.77 ▲63.23 |
Posts /wp-admin/edit.php | 2,183 ▲86 | 2.35 ▲0.36 | 47.32 ▲7.92 | 37.65 ▼0.49 |
Add New Post /wp-admin/post-new.php | 1,738 ▲212 | 22.36 ▼0.71 | 713.84 ▲95.45 | 32.60 ▼44.77 |
Media Library /wp-admin/upload.php | 1,472 ▲69 | 4.45 ▲0.17 | 100.99 ▲1.30 | 119.77 ▲78.67 |
Add New /wp-admin/post-new.php?post_type=fab | 7,190 | 19.83 | 886.26 | 57.01 |
Floating Awesome Button /wp-admin/options-general.php?page=floating-awesome-button-setting | 1,055 | 2.20 | 36.74 | 67.05 |
FAB /wp-admin/edit.php?post_type=fab | 1,151 | 2.46 | 38.15 | 35.62 |
Freemius Debug [v.2.5.2] /wp-admin/admin.php?page=freemius | 1,140 | 2.06 | 30.72 | 32.08 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.08MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Uninstall procedure validation failed for this plugin
- > Notice in wp-content/plugins/floating-awesome-button/vendor/freemius/wordpress-sdk/includes/class-freemius.php+8772
Undefined property: stdClass::$plugins
- This plugin did not uninstall successfully, leaving 11 options in the database
- fs_active_plugins
- fs_accounts
- fs_debug_mode
- widget_recent-posts
- fs_gdpr
- fab_config
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- ...
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
Almost there! Just fix the following items
- 11× PHP files output non-empty strings when accessed directly via GET requests (only 10 are shown):
- > /wp-content/plugins/floating-awesome-button/src/View/Element/reload.php
- > /wp-content/plugins/floating-awesome-button/src/View/Frontend/button.php
- > /wp-content/plugins/floating-awesome-button/src/View/Backend/Metabox/setting.php
- > /wp-content/plugins/floating-awesome-button/src/View/Frontend/Module/search.php
- > /wp-content/plugins/floating-awesome-button/src/View/Backend/setting.php
- > /wp-content/plugins/floating-awesome-button/src/View/Frontend/modal.php
- > /wp-content/plugins/floating-awesome-button/src/View/Backend/Metabox/location.php
- > /wp-content/plugins/floating-awesome-button/src/View/Tailwind/element.php
- > /wp-content/plugins/floating-awesome-button/src/View/Backend/Metabox/trigger.php
- > /wp-content/plugins/floating-awesome-button/src/View/Backend/Metabox/design.php
- 74× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Fab\\Controller\\Base' not found in wp-content/plugins/floating-awesome-button/src/Plugin/Customizer.php:14
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/floating-awesome-button/src/View/Template/backend/default.php:9
- > PHP Fatal error
Uncaught Error: Class 'Fab\\Feature\\Feature' not found in wp-content/plugins/floating-awesome-button/src/Feature/Design.php:14
- > PHP Fatal error
Uncaught Error: Class 'Fab\\Controller\\Base' not found in wp-content/plugins/floating-awesome-button/src/Controller/Backend/BackendPage.php:18
- > PHP Fatal error
Uncaught Error: Class 'Fab\\Feature\\Feature' not found in wp-content/plugins/floating-awesome-button/src/Feature/Frontend.php:14
- > PHP Fatal error
Uncaught Error: Class 'Fab\\Controller\\Base' not found in wp-content/plugins/floating-awesome-button/src/Controller/Metabox/MetaboxSetting.php:20
- > PHP Fatal error
Uncaught Error: Class 'Fab\\Controller\\Base' not found in wp-content/plugins/floating-awesome-button/src/Controller/Metabox/MetaboxTrigger.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_url() in wp-content/plugins/floating-awesome-button/src/View/Element/loading-field.php:8
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/floating-awesome-button/src/View/Template/backend/box.php:1
- > PHP Fatal error
Uncaught Error: Class 'Fab\\Wordpress\\Model\\Model' not found in wp-content/plugins/floating-awesome-button/src/Wordpress/Model/Type.php:17
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Please take a look at the following user-side issues
- > GET request to /wp-admin/post-new.php?post_type=fab
- > Javascript (severe) in unknown
/wp-content/plugins/floating-awesome-button/assets/build/components/metabox-trigger/bundle.js?ver=1.0 0:2488 Uncaught TypeError: Cannot read properties of undefined (reading '$$')
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Screenshots: No descriptions were found for these screenshots #1, #2, #3, #4, #5, #6 in floating-awesome-button/assets to your readme.txt
floating-awesome-button/floating-awesome-button.php 92% from 13 tests
Analyzing the main PHP file in "Floating Awesome Button (Sticky Button & Popup) - CTA, Back to Top, Shortcodes, Widget, & More" version 1.6.1
The following require your attention:
- Description: The description should be shorter than 140 characters (currently 142 characters long)
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
There were no executable files found in this plugin38,666 lines of code in 282 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 237 | 9,268 | 20,263 | 38,383 |
JavaScript | 20 | 34 | 77 | 211 |
JSON | 2 | 0 | 0 | 49 |
CSS | 23 | 0 | 19 | 23 |
PHP code 50% from 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Please tend to the following items
- Cyclomatic complexity of classes has to be reduced to less than 1000 (currently 3,089)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.58 |
Average class complexity | 38.84 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 3,089.00 |
Average method complexity | 3.87 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 89.00 |
Code structure | ||
---|---|---|
Namespaces | 16 | |
Interfaces | 0 | |
Traits | 13 | |
Classes | 115 | |
▷ Abstract classes | 7 | 6.09% |
▷ Concrete classes | 108 | 93.91% |
▷ Final classes | 0 | 0.00% |
Methods | 1,725 | |
▷ Static methods | 211 | 12.23% |
▷ Public methods | 1,339 | 77.62% |
▷ Protected methods | 17 | 0.99% |
▷ Private methods | 369 | 21.39% |
Functions | 97 | |
▷ Named functions | 94 | 96.91% |
▷ Anonymous functions | 3 | 3.09% |
Constants | 151 | |
▷ Global constants | 104 | 68.87% |
▷ Class constants | 47 | 31.13% |
▷ Public constants | 47 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
vendor/freemius/wordpress-sdk/assets/img/plugin-icon.png | 9.16KB | 5.26KB | ▼ 42.58% |
assets/img/logo.png | 3.93KB | 0.74KB | ▼ 81.21% |
assets/img/icon.png | 2.84KB | 0.41KB | ▼ 85.64% |
vendor/freemius/wordpress-sdk/assets/img/theme-icon.png | 10.97KB | 5.78KB | ▼ 47.37% |