Does Floating Awesome Button work with WordPress 6.7.1 and PHP 8.1.12? A smoke test was performed on .
No PHP errors, warnings or notices | |
No JavaScript exceptions | |
All test pages loaded successfully | |
No resource errors | |
Looks good! No problems were detected. |
Memory usage: 324.41 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
WordPress version | 6.7.1 |
---|---|
PHP version | 8.1.12 |
MySQL version | 10.6.10 |
PHP memory limit | 512M |
Last updated | |
---|---|
Active installs | 900+ |
WordPress.org page | https://wordpress.org/plugins/floating-awesome-button/ |
Badges |
|
URL | /wp-admin/options-general.php?page=floating-awesome-button-setting |
---|---|
Requested URL | /wp-admin/plugins.php?action=activate&plugin=floating-awesome-button%2Ffloating-awesome-button.php&plugin_status=all&paged=1&s&_wpnonce=c35f92bd81 |
Aspect | after-activation |
HTTP status | 200 |
Load time | 1.151 s |
Memory usage | 4.15 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/edit.php?post_type=fab |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.172 s |
Memory usage | 3.81 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/post-new.php?post_type=fab |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.947 s |
Memory usage | 6.39 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=floating-awesome-button-setting |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 0.471 s |
Memory usage | 3.8 MiB |
JS errors | None |
Resource errors | None |
URL | /wp-admin/options-general.php?page=floating-awesome-button-setting-pricing |
---|---|
Aspect | menu-item |
HTTP status | 200 |
Load time | 1.216 s |
Memory usage | 3.8 MiB |
JS errors | None |
Resource errors | None |
URL | / |
---|---|
Aspect | front-page |
HTTP status | 200 |
Load time | 0.284 s |
Memory usage | 3.69 MiB |
JS errors | None |
Resource errors | None |
URL | Load time | Memory usage | ||||
---|---|---|---|---|---|---|
Inactive | Active | Change | Inactive | Active | Change | |
/wp-admin/index.php | 0.309 s | 0.357 s | +0.048 s | 3.48 MiB | 3.82 MiB | + 345.37 KiB |
/wp-admin/edit.php | 0.170 s | 0.196 s | +0.026 s | 3.54 MiB | 3.89 MiB | + 355.14 KiB |
/wp-admin/post-new.php | 0.709 s | 0.635 s | -0.074 s | 5.92 MiB | 6.37 MiB | + 452.14 KiB |
/wp-admin/upload.php | 0.517 s | 0.348 s | -0.169 s | 3.5 MiB | 3.76 MiB | + 273.3 KiB |
/wp-admin/options-writing.php | 0.174 s | 0.423 s | +0.249 s | 3.47 MiB | 3.75 MiB | + 280.25 KiB |
/wp-admin/media-new.php | 0.232 s | 0.265 s | +0.033 s | 3.46 MiB | 3.74 MiB | + 284.68 KiB |
/wp-admin/edit-tags.php?taxonomy=category | 0.155 s | 0.209 s | +0.054 s | 3.48 MiB | 3.78 MiB | + 307.25 KiB |
/wp-admin/post-new.php?post_type=page | 0.561 s | 0.603 s | +0.042 s | 5.92 MiB | 6.36 MiB | + 443.07 KiB |
/wp-admin/options-discussion.php | 0.280 s | 0.247 s | -0.033 s | 3.47 MiB | 3.75 MiB | + 277.43 KiB |
/wp-admin/edit-comments.php | 0.174 s | 0.207 s | +0.033 s | 3.49 MiB | 3.78 MiB | + 293.54 KiB |
/ | 0.270 s | 0.245 s | -0.025 s | 3.41 MiB | 3.66 MiB | + 256.33 KiB |
Average | 0.323 s | 0.340 s | +0.017 s | 3.92 MiB | 4.24 MiB | + 324.41 KiB |
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
Language | % | Lines of code | Comment lines | Files | |
---|---|---|---|---|---|
JSON | 56.5% | 6,895 | 0 | 2 | |
PHP | 43.4% | 5,304 | 2,896 | 116 | |
JavaScript | 0.1% | 10 | 5 | 9 | |
CSS | 0.0% | 2 | 0 | 2 | |
Total | 12,211 | 2,901 | 129 |
Lines of code | 4,667 |
---|---|
Total complexity | 820 |
Median class complexity | 6.0 |
Median method complexity | 1.0 |
Most complex class | Fab\Helper\FABItem |
Most complex function | Fab\Helper\FABItem::match() |
Classes | 67 |
---|---|
Methods | 395 |
Functions | 2 |
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
wp_options
5ID | Name |
---|---|
fab | FAB |
{
"fab": {
"fab-metabox-design": {
"title": "Design",
"context": "advanced"
},
"fab-metabox-location": {
"title": "Location (Premium)",
"context": "advanced"
},
"fab-metabox-settings": {
"title": "Setting",
"context": "advanced"
},
"fab-metabox-triggers": {
"title": "Trigger (Premium)",
"context": "advanced"
}
}
}
The log file is empty.