Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼0.11MB] [CPU: ▼8.24ms] Passed 4 tests
Analyzing server-side resources used by Frontier Buttons
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.66 ▲0.15 | 47.69 ▲1.80 |
Dashboard /wp-admin | 3.51 ▲0.17 | 51.19 ▲0.51 |
Posts /wp-admin/edit.php | 3.61 ▲0.22 | 50.14 ▼5.06 |
Add New Post /wp-admin/post-new.php | 5.01 ▼0.91 | 64.59 ▼30.22 |
Media Library /wp-admin/upload.php | 3.42 ▲0.15 | 41.17 ▲6.03 |
Frontier-Buttons /wp-admin/options-general.php?page=frontier-buttons/include/settings-menu.php | 3.51 | 35.41 |
Server storage [IO: ▲0.67MB] [DB: ▲0.01MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 59 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
theysaidso_admin_options |
widget_recent-comments |
frontier-buttons-general-settings |
Browser metrics Passed 4 tests
Checking browser requirements for Frontier Buttons
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,795 ▲34 | 14.18 ▼0.41 | 1.66 ▼0.14 | 45.94 ▲3.10 |
Dashboard /wp-admin | 2,204 ▲27 | 5.63 ▲0.00 | 88.42 ▼0.93 | 37.51 ▼3.90 |
Posts /wp-admin/edit.php | 2,106 ▲3 | 2.01 ▲0.05 | 32.73 ▼7.63 | 35.91 ▼0.57 |
Add New Post /wp-admin/post-new.php | 1,531 ▲5 | 23.17 ▼0.40 | 634.95 ▼59.18 | 64.68 ▲13.00 |
Media Library /wp-admin/upload.php | 1,409 ▲12 | 4.19 ▲0.01 | 101.85 ▼3.20 | 47.01 ▼0.81 |
Frontier-Buttons /wp-admin/options-general.php?page=frontier-buttons/include/settings-menu.php | 2,643 | 7.80 | 149.29 | 61.55 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
These errors were triggered by the plugin
- > GET request to /wp-admin/options-general.php?page=frontier-buttons/include/settings-menu.php
- > Deprecated in wp-content/plugins/frontier-buttons/include/menu-item-main.php+98
implode(): Passing glue string after array is deprecated. Swap the parameters
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
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/frontier-buttons/include/frontier-buttons-hooks.php:109
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/frontier-buttons/frontier-buttons.php:24
- > PHP Fatal error
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)
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need your attention:
- Donate link: Invalid url: ""
frontier-buttons/frontier-buttons.php 92% from 13 tests
The principal PHP file in "Frontier Buttons" v. 2.5.4 is loaded by WordPress automatically on each request
The following require your attention:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 142 characters long)
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
There were no executable files found in this plugin2,090 lines of code in 40 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 10 | 653 | 529 | 1,443 |
CSS | 4 | 102 | 35 | 476 |
PO File | 1 | 102 | 158 | 137 |
JavaScript | 25 | 0 | 1 | 34 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.31 |
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 | 54 | |
▷ Named functions | 54 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 16 | |
▷ Global constants | 16 | 100.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
There are no PNG files in this plugin