Benchmarks
Plugin footprint 48% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲2.67MB] [CPU: ▼275.99ms] Passed 4 tests
A check of server-side resources used by Frontend Admin - Add and edit posts, pages, users and more all from the frontend
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 6.25 ▲2.74 | 64.55 ▲10.28 |
| Dashboard /wp-admin | 6.03 ▲2.62 | 43.81 ▲10.77 |
| Posts /wp-admin/edit.php | 6.26 ▲2.62 | 49.11 ▲12.76 |
| Add New Post /wp-admin/post-new.php | 9.66 ▲2.69 | 111.87 ▼1,137.70 |
| Media Library /wp-admin/upload.php | 6.07 ▲2.78 | 37.44 ▲12.70 |
| Freemius Debug [v.2.4.3] /wp-admin/admin.php?page=freemius | 6.32 | 32.55 |
Server storage [IO: ▲14.35MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 565 new files
Database: 1 new table, 7 new options
| New tables |
|---|
| wp_fea_submissions |
| New WordPress options |
|---|
| acf_version |
| fs_accounts |
| fs_debug_mode |
| fs_gdpr |
| frontend_admin_hide_by |
| fs_active_plugins |
| frontend_admin_hide_wp_dashboard |
Browser metrics Passed 4 tests
An overview of browser requirements for Frontend Admin - Add and edit posts, pages, users and more all from the frontend
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,833 ▲89 | 15.68 ▼0.28 | 5.69 ▼0.78 | 2.24 ▼0.23 |
| Dashboard /wp-admin | 2,942 ▲81 | 6.16 ▲0.01 | 116.68 ▼13.59 | 169.18 ▲11.19 |
| Posts /wp-admin/edit.php | 2,738 ▲50 | 3.23 ▼0.00 | 63.24 ▼0.18 | 149.39 ▲10.31 |
| Add New Post /wp-admin/post-new.php | 2,495 ▲834 | 23.77 ▲7.67 | 567.55 ▲158.25 | 162.83 ▲9.49 |
| Media Library /wp-admin/upload.php | 2,409 ▲711 | 10.91 ▲5.41 | 231.26 ▲97.45 | 209.32 ▲23.60 |
| Freemius Debug [v.2.4.3] /wp-admin/admin.php?page=freemius | 1,469 | 2.70 | 53.85 | 112.13 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- This plugin cannot be uninstalled
- > Notice in wp-content/plugins/frontend-admin/includes/freemius/includes/class-freemius.php+8575
Undefined property: stdClass::$plugins
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_fea_submissions
- Zombie WordPress options detected upon uninstall: 7 options
- fs_active_plugins
- frontend_admin_hide_wp_dashboard
- frontend_admin_hide_by
- fs_gdpr
- fs_accounts
- fs_debug_mode
- acf_version
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
The following issues need your attention
- 131× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/frontend-admin/includes/acf/includes/fields/class-acf-field-output.php:5
- > PHP Notice
Undefined variable: rule in wp-content/plugins/frontend-admin/includes/acf/includes/admin/views/html-location-rule.php on line 7
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/frontend-admin/includes/acf/includes/fields/class-acf-field-number.php:5
- > PHP Fatal error
Uncaught Error: Class 'Frontend_WP\\Widgets\\ACF_Frontend_Form_Widget' not found in wp-content/plugins/frontend-admin/main/elementor/widgets/posts/duplicate_post.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/frontend-admin/includes/acf/includes/acf-utility-functions.php:106
- > PHP Fatal error
Uncaught Error: Class 'Elementor\\Widget_Base' not found in wp-content/plugins/frontend-admin/main/elementor/widgets/general/edit_button.php:23
- > PHP Fatal error
Uncaught Error: Class 'OxyEl' not found in wp-content/plugins/frontend-admin/main/oxygen/elements/general/frontend-form.php:3
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/frontend-admin/main/frontend/fields/user/role.php:5
- > PHP Fatal error
Uncaught Error: Class 'Frontend_WP\\Widgets\\ACF_Frontend_Form_Widget' not found in wp-content/plugins/frontend-admin/main/elementor/widgets/terms/edit_term.php:13
- > PHP Fatal error
Uncaught Error: Class 'acf_field_text' not found in wp-content/plugins/frontend-admin/main/frontend/fields/user/username.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Screenshots: These screenshots do not have images: #1 (The New Post Form widget enables users to add new posts to a custom or WordPress standard post type from the frontend of a WordPress website, without needing to interact with the WordPress dashboard. The page to host the form is built in Elementor. Important: By default a user needs to be logged in and carry the “administrator” role to add a post. This can be changed, however, in the Permissions settings of this widget.), #2 (The Field Type defines the type of field being edited. Changing this will affect the other available options. All the field types have options which can be changed to customize both the content and the style of the field.), #3 (Here we have several options for additional actions to take place outside the form itself. You can define where the page should redirect to after submitting. By default it will reload the current Page/Post. We can choose to redirect to the live post by selecting Custom URL. You can also define a custom success message, or choose no success message, whatever suits your needs.), #4 (This is where we limit which kinds of users can access the form. It is very important to configure this correctly, as otherwise your users might not be able to see the form at all! By default, only administrators can see the form. If you want to allow other users to access it, you need to add them. You can choose Roles under the Select By Role option, or add specific users under the Select By User option.), #5 (The Edit Post Form widget enables users to edit existing posts from the frontend of a WordPress website, without needing to interact with the WordPress dashboard.)
frontend-admin/frontend-admin.php 85% from 13 tests
The primary PHP file in "Frontend Admin - Add and edit posts, pages, users and more all from the frontend" version 3.3.41 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Domain Path: The domain path is invalid: folder "/languages/" does not exist
- Description: Keep the plugin description shorter than 140 characters (currently 155 characters long)
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected205,603 lines of code in 463 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 358 | 20,286 | 39,290 | 72,596 |
| PO File | 31 | 23,805 | 40,551 | 48,965 |
| JavaScript | 35 | 6,538 | 6,345 | 40,998 |
| JSON | 2 | 0 | 0 | 36,305 |
| CSS | 34 | 694 | 746 | 6,721 |
| SVG | 3 | 0 | 0 | 18 |
PHP code 50% from 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
It is recommended to fix the following
- Class cyclomatic complexity has to be reduced to less than 1000 (currently 2,910)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.49 |
| Average class complexity | 32.26 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 2,910.00 |
| Average method complexity | 3.92 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 86.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 10 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 248 | |
| ▷ Abstract classes | 6 | 2.42% |
| ▷ Concrete classes | 242 | 97.58% |
| ▷ Final classes | 1 | 0.41% |
| Methods | 2,693 | |
| ▷ Static methods | 186 | 6.91% |
| ▷ Public methods | 2,305 | 85.59% |
| ▷ Protected methods | 42 | 1.56% |
| ▷ Private methods | 346 | 12.85% |
| Functions | 568 | |
| ▷ Named functions | 562 | 98.94% |
| ▷ Anonymous functions | 6 | 1.06% |
| Constants | 145 | |
| ▷ Global constants | 118 | 81.38% |
| ▷ Class constants | 27 | 18.62% |
| ▷ Public constants | 27 | 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
10 compressed PNG files occupy 0.04MB
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| includes/acf/assets/inc/datepicker/images/ui-icons_DDDDDD_256x240.png | 3.68KB | 4.17KB | 0.00% |
| includes/acf/assets/inc/select2/3/select2x2.png | 0.64KB | 0.77KB | 0.00% |
| includes/freemius/assets/img/plugin-icon.png | 9.16KB | 5.26KB | ▼ 42.58% |
| includes/acf/assets/inc/select2/3/select2.png | 0.51KB | 0.99KB | 0.00% |
| includes/acf/assets/images/acf-logo.png | 3.40KB | 3.39KB | 0.23% |