Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.07MB] [CPU: ▼2.86ms] Passed 4 tests
A check of server-side resources used by Frontend Admin by DynamiApps
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.53 ▲0.07 | 40.14 ▼0.38 |
| Dashboard /wp-admin | 3.37 ▲0.07 | 47.76 ▼4.59 |
| Posts /wp-admin/edit.php | 3.42 ▲0.07 | 50.41 ▼0.61 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.07 | 96.66 ▼3.19 |
| Media Library /wp-admin/upload.php | 3.29 ▲0.07 | 36.42 ▼3.05 |
Server storage [IO: ▲3.32MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 176 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Frontend Admin by DynamiApps
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,806 ▲45 | 14.73 ▲0.17 | 1.71 ▲0.18 | 44.72 ▲4.48 |
| Dashboard /wp-admin | 2,212 ▲32 | 5.57 ▼0.02 | 97.21 ▲1.85 | 45.63 ▲2.42 |
| Posts /wp-admin/edit.php | 2,117 ▲17 | 2.03 ▲0.05 | 42.75 ▼2.64 | 38.96 ▼1.67 |
| Add New Post /wp-admin/post-new.php | 1,538 ▲10 | 23.39 ▲0.63 | 655.63 ▼27.00 | 50.02 ▲0.89 |
| Media Library /wp-admin/upload.php | 1,420 ▲23 | 4.26 ▲0.08 | 100.97 ▼1.70 | 42.80 ▼1.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin does not fully uninstall, 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 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)
Good news, no errors were detected
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
- 76× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\Field_Base' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/general/class-url.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\Field_Base' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/general/class-password.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\upload_image' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/post/class-featured-image.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\Field_Base' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/general/class-submit-button.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\Field_Base' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/general/class-checkbox.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Elementor\\Widgets\\ACF_Form' not found in wp-content/plugins/acf-frontend-form-element/main/elementor/widgets/products/new_product.php:13
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\Field_Base' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/general/class-text-editor.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\Field_Base' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/post/class-post-to-edit.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\Field_Base' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/general/class-upload-files.php:6
- > PHP Fatal error
Uncaught Error: Class 'Frontend_Admin\\Field_Types\\text' not found in wp-content/plugins/acf-frontend-form-element/main/frontend/fields/term/class-term-slug.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
6 plugin tags: frontend editing, acf form, acf, elementor, acf frontend...
acf-frontend-form-element/acf-frontend.php 85% from 13 tests
The main file in "Frontend Admin by DynamiApps" v. 3.18.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Description: Please don't use more than 140 characters for the plugin description (currently 161 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("acf-frontend-form-element.php" instead of "acf-frontend.php")
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected68,217 lines of code in 167 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JSON | 4 | 0 | 0 | 37,320 |
| PHP | 134 | 6,269 | 7,105 | 26,046 |
| JavaScript | 18 | 768 | 494 | 3,514 |
| CSS | 11 | 346 | 6 | 1,337 |
PHP code 50% from 2 tests
This is a very shot review of cyclomatic complexity and code structure
Please tend to the following items
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 107)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.43 |
| Average class complexity | 25.02 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 304.00 |
| Average method complexity | 3.92 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 107.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 9 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 122 | |
| ▷ Abstract classes | 1 | 0.82% |
| ▷ Concrete classes | 121 | 99.18% |
| ▷ Final classes | 2 | 1.65% |
| Methods | 1,006 | |
| ▷ Static methods | 21 | 2.09% |
| ▷ Public methods | 983 | 97.71% |
| ▷ Protected methods | 22 | 2.19% |
| ▷ Private methods | 1 | 0.10% |
| Functions | 46 | |
| ▷ Named functions | 39 | 84.78% |
| ▷ Anonymous functions | 7 | 15.22% |
| Constants | 6 | |
| ▷ Global constants | 5 | 83.33% |
| ▷ Class constants | 1 | 16.67% |
| ▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/plugin-logo.png | 5.32KB | 2.93KB | ▼ 44.94% |
| assets/icon.png | 1.58KB | 1.15KB | ▼ 27.54% |