Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲1.89MB] [CPU: ▲11.77ms] Passed 4 tests
Server-side resources used by F12 Floating Menu, sticky menu for WordPress
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.28 ▲0.82 | 46.39 ▲2.58 |
| Dashboard /wp-admin | 5.65 ▲2.35 | 74.21 ▲23.45 |
| Posts /wp-admin/edit.php | 5.79 ▲2.44 | 74.72 ▲19.76 |
| Add New Post /wp-admin/post-new.php | 7.87 ▲1.99 | 107.06 ▲8.09 |
| Media Library /wp-admin/upload.php | 5.64 ▲2.41 | 53.33 ▲16.63 |
| Settings /wp-admin/edit.php?post_type=floating_menu&page=f12_floating_menu_settings | 5.64 | 51.36 |
| Add New /wp-admin/post-new.php?post_type=floating_menu | 5.70 | 69.83 |
| Floating Menu /wp-admin/edit.php?post_type=floating_menu | 5.77 | 53.29 |
| Dashboard /wp-admin/edit.php?post_type=floating_menu&page=f12_floating_menu | 5.64 | 49.97 |
Server storage [IO: ▲3.53MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 78 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| db_upgraded |
Browser metrics Passed 4 tests
F12 Floating Menu, sticky menu for WordPress: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,150 ▲389 | 16.03 ▲1.61 | 7.12 ▲5.53 | 41.76 ▲1.02 |
| Dashboard /wp-admin | 2,439 ▲262 | 7.30 ▲1.63 | 128.39 ▲39.36 | 42.94 ▼3.47 |
| Posts /wp-admin/edit.php | 2,364 ▲264 | 4.07 ▲2.05 | 61.32 ▲15.12 | 35.19 ▼2.88 |
| Add New Post /wp-admin/post-new.php | 1,625 ▲88 | 23.99 ▲5.83 | 609.42 ▼9.69 | 35.31 ▼40.14 |
| Media Library /wp-admin/upload.php | 1,501 ▲101 | 5.28 ▲1.17 | 97.78 ▼9.56 | 45.52 ▼0.95 |
| Settings /wp-admin/edit.php?post_type=floating_menu&page=f12_floating_menu_settings | 1,942 | 4.80 | 84.31 | 41.54 |
| Add New /wp-admin/post-new.php?post_type=floating_menu | 8,265 | 5.15 | 140.44 | 56.90 |
| Floating Menu /wp-admin/edit.php?post_type=floating_menu | 1,328 | 3.98 | 56.76 | 30.56 |
| Dashboard /wp-admin/edit.php?post_type=floating_menu&page=f12_floating_menu | 1,101 | 4.04 | 47.05 | 26.15 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Everything seems fine, however this is by no means an exhaustive test
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 83% from 29 tests
readme.txt 75% 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
Please fix the following attributes:
- Tags: There are too many tags (15 tag instead of maximum 10)
- Requires php: The plugin version is formatted incorrectly
- Screenshots: Please add descriptions for these screenshots #1, #2, #3 in f12-floating-menu/assets to your readme.txt
- Requires at least: The plugin version is formatted incorrectly
f12-floating-menu/Application.class.php 92% from 13 tests
The main PHP script in "F12 Floating Menu, sticky menu for WordPress" version 1.3.3 is automatically included on every request by WordPress
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("f12-floating-menu.php" instead of "Application.class.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected20,383 lines of code in 59 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| SVG | 3 | 0 | 0 | 9,552 |
| PHP | 27 | 652 | 1,079 | 5,541 |
| CSS | 9 | 1,644 | 142 | 3,901 |
| JavaScript | 18 | 206 | 497 | 937 |
| Sass | 2 | 78 | 0 | 452 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.28 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 51.00 |
| Average method complexity | 2.72 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 3 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 27 | |
| ▷ Abstract classes | 3 | 11.11% |
| ▷ Concrete classes | 24 | 88.89% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 163 | |
| ▷ Static methods | 10 | 6.13% |
| ▷ Public methods | 125 | 76.69% |
| ▷ Protected methods | 16 | 9.82% |
| ▷ Private methods | 22 | 13.50% |
| Functions | 2 | |
| ▷ Named functions | 0 | 0.00% |
| ▷ Anonymous functions | 2 | 100.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.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
2 PNG files occupy 0.03MB with 0.02MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| core/assets/logo-forge12-dark.png | 18.66KB | 6.28KB | ▼ 66.37% |
| core/assets/logo-forge12.png | 10.04KB | 3.91KB | ▼ 61.10% |