Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲1.76MB] [CPU: ▲9.83ms] Passed 4 tests
A check of server-side resources used by Fuerte-WP
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 5.21 ▲1.75 | 58.93 ▲14.43 |
| Dashboard /wp-admin | 5.11 ▲1.81 | 58.66 ▼0.37 |
| Posts /wp-admin/edit.php | 5.16 ▲1.81 | 61.82 ▲13.74 |
| Add New Post /wp-admin/post-new.php | 7.65 ▲1.76 | 107.53 ▲11.51 |
| Media Library /wp-admin/upload.php | 4.95 ▲1.72 | 51.45 ▲15.86 |
Server storage [IO: ▲10.43MB] [DB: ▲0.01MB] 67% from 3 tests
Filesystem and database footprint
It is recommended to fix the following issues
- Illegal file modification found: 1 file (0.95KB) outside of "wp-content/plugins/fuerte-wp/" and "wp-content/uploads/"
- (modified) .htaccess
Filesystem: 501 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-posts |
| db_upgraded |
| widget_theysaidso_widget |
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
Fuerte-WP: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,962 ▲200 | 18.50 ▲4.15 | 1.68 ▼0.04 | 42.88 ▼3.32 |
| Dashboard /wp-admin | 2,368 ▲191 | 9.07 ▲3.43 | 195.97 ▲107.87 | 39.40 ▼3.86 |
| Posts /wp-admin/edit.php | 2,305 ▲202 | 6.20 ▲4.19 | 89.17 ▲50.31 | 33.65 ▼1.42 |
| Add New Post /wp-admin/post-new.php | 1,592 ▲66 | 26.74 ▲3.54 | 657.00 ▲29.30 | 45.84 ▼2.27 |
| Media Library /wp-admin/upload.php | 1,439 ▲45 | 6.75 ▲2.56 | 118.66 ▲15.32 | 41.80 ▼0.59 |
| Fuerte-WP /wp-admin/crb_carbon_fields_container_fuerte-wp.php | 26 | 0.41 | 0.07 | 14.22 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following items
- 3× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/fuerte-wp/config-sample/index.php
- > /wp-content/plugins/fuerte-wp/index.php
- > /wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/templates/Exception/incorrect-syntax.php
- 117× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Field\\Field' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Field/Predefined_Options_Field.php:12
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Container\\Condition\\Condition' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Container/Condition/Term_Level_Condition.php:10
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Field\\Field' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Field/Date_Field.php:8
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/templates/Container/nav_menu_item.php:1
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Field\\Select_Field' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Field/Radio_Field.php:8
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Container\otFoundExceptionInterface' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Pimple/Exception/UnknownIdentifierException.php:36
- > PHP Fatal error
Uncaught Error: Class 'Walker_Nav_Menu_Edit' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Walker/Nav_Menu_Item_Edit_Walker.php:10
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/templates/Container/common/options-page.php:2
- > PHP Fatal error
Uncaught Error: Class 'Carbon_Fields\\Datastore\\Key_Value_Datastore' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Datastore/Widget_Datastore.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Carbon_Fields\\Datastore\\Datastore_Holder_Interface' not found in wp-content/plugins/fuerte-wp/vendor/htmlburger/carbon-fields/core/Field/Field.php:17
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Please fix the following user-side errors
- > GET request to /wp-admin/crb_carbon_fields_container_fuerte-wp.php
- > Network (severe)
wp-admin/crb_carbon_fields_container_fuerte-wp.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
1 plugin tags: security
fuerte-wp/fuerte-wp.php Passed 13 tests
The principal PHP file in "Fuerte-WP" v. 1.4.12 is loaded by WordPress automatically on each request
77 characters long description:
Stronger WP. Limit access to critical WordPress areas, even other for admins.
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 plugin34,162 lines of code in 444 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 176 | 7,103 | 10,984 | 16,206 |
| PHP | 172 | 2,984 | 8,059 | 10,544 |
| PO File | 30 | 1,080 | 1,315 | 2,803 |
| CSS | 9 | 240 | 1,165 | 2,221 |
| Sass | 49 | 365 | 3 | 1,868 |
| JSON | 3 | 0 | 0 | 369 |
| Markdown | 5 | 45 | 0 | 151 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.32 |
| Average class complexity | 9.31 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 179.00 |
| Average method complexity | 2.09 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 18.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 24 | |
| Interfaces | 5 | |
| Traits | 0 | |
| Classes | 139 | |
| ▷ Abstract classes | 11 | 7.91% |
| ▷ Concrete classes | 128 | 92.09% |
| ▷ Final classes | 2 | 1.56% |
| Methods | 993 | |
| ▷ Static methods | 124 | 12.49% |
| ▷ Public methods | 809 | 81.47% |
| ▷ Protected methods | 170 | 17.12% |
| ▷ Private methods | 14 | 1.41% |
| Functions | 118 | |
| ▷ Named functions | 30 | 25.42% |
| ▷ Anonymous functions | 88 | 74.58% |
| Constants | 42 | |
| ▷ Global constants | 17 | 40.48% |
| ▷ Class constants | 25 | 59.52% |
| ▷ Public constants | 25 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG images were found in this plugin