Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.00MB] [CPU: ▼304.55ms] Passed 4 tests
This is a short check of server-side resources used by GFireM Action After
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.21 ▲0.01 | 58.65 ▼0.41 |
Dashboard /wp-admin | 4.04 ▲0.01 | 36.43 ▼0.30 |
Posts /wp-admin/edit.php | 4.33 ▲0.01 | 42.79 ▲0.27 |
Add New Post /wp-admin/post-new.php | 7.57 ▼0.02 | 95.05 ▼1,209.91 |
Media Library /wp-admin/upload.php | 3.98 ▲0.00 | 31.81 ▼7.58 |
Server storage [IO: ▲1.37MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 172 new files
Database: no new tables, 4 new options
New WordPress options |
---|
fs_active_plugins |
fs_accounts |
fs_api_cache |
fs_debug_mode |
Browser metrics Passed 4 tests
This is an overview of browser requirements for GFireM Action After
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,787 ▲33 | 15.93 ▼0.09 | 6.43 ▲0.35 | 2.20 ▼0.33 |
Dashboard /wp-admin | 2,895 ▲30 | 6.13 ▲0.00 | 117.65 ▼23.86 | 153.34 ▼27.34 |
Posts /wp-admin/edit.php | 2,670 ▼15 | 3.25 ▲0.01 | 92.33 ▲24.85 | 147.99 ▲1.92 |
Add New Post /wp-admin/post-new.php | 1,755 ▲120 | 17.65 ▲0.29 | 412.68 ▼18.65 | 163.28 ▲15.36 |
Media Library /wp-admin/upload.php | 1,695 ▼0 | 5.48 ▼0.04 | 140.17 ▼1.69 | 185.60 ▼2.71 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- Zombie WordPress options were found after uninstall: 4 options
- fs_api_cache
- fs_active_plugins
- fs_accounts
- fs_debug_mode
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
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
Please take a closer look at the following
- 7× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/gfirem-action-after/classes/actions/faa_delete_entry/view/delete_entry.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/gfirem-action-after/classes/actions/faa_delete_post/view/delete_post.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/gfirem-action-after/classes/actions/faa_reset_pass/view/faa_reset_pass_view.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/gfirem-action-after/classes/actions/faa_replace/view/faa_replace_view.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/gfirem-action-after/view/watch-row.php:1
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/gfirem-action-after/classes/actions/faa_mycred/view/faa_mycred_view.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/gfirem-action-after/view/action_top.php:2
- > 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)
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
7 plugin tags: formidable action, formidable, formidable action before, formidable wordpress actions, delete entry...
gfirem-action-after/gfirem_action_after.php 92% from 13 tests
The entry point to "GFireM Action After" version 1.1.6 is a PHP file that has certain tags in its header comment area
The following require your attention:
- Main file name: Name the main plugin file the same as the plugin slug ("gfirem-action-after.php" instead of "gfirem_action_after.php")
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
There were no executable files found in this plugin23,693 lines of code in 142 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 99 | 3,758 | 8,929 | 16,425 |
PO File | 6 | 1,901 | 1,928 | 4,896 |
Sass | 16 | 277 | 82 | 1,713 |
JavaScript | 6 | 58 | 68 | 391 |
Markdown | 1 | 61 | 0 | 192 |
JSON | 2 | 0 | 0 | 42 |
CSS | 12 | 1 | 9 | 34 |
PHP code 50% from 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
It is recommended to fix the following
- Class cyclomatic complexity should be reduced to less than 1000 (currently 1,051)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.51 |
Average class complexity | 29.10 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 1,051.00 |
Average method complexity | 3.27 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 76.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 60 | |
▷ Abstract classes | 2 | 3.33% |
▷ Concrete classes | 58 | 96.67% |
▷ Final classes | 0 | 0.00% |
Methods | 785 | |
▷ Static methods | 120 | 15.29% |
▷ Public methods | 602 | 76.69% |
▷ Protected methods | 13 | 1.66% |
▷ Private methods | 170 | 21.66% |
Functions | 75 | |
▷ Named functions | 73 | 97.33% |
▷ Anonymous functions | 2 | 2.67% |
Constants | 101 | |
▷ Global constants | 84 | 83.17% |
▷ Class constants | 17 | 16.83% |
▷ Public constants | 17 | 100.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
4 PNG files occupy 0.04MB with 0.02MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
classes/include/freemius/assets/img/formidable_action_after.png | 9.16KB | 5.26KB | ▼ 42.58% |
classes/include/freemius/assets/img/formidable-autocomplete.png | 9.16KB | 5.26KB | ▼ 42.58% |
classes/include/freemius/assets/img/plugin-icon.png | 9.16KB | 5.26KB | ▼ 42.58% |
classes/include/freemius/assets/img/gfirem_action_after.png | 9.16KB | 5.26KB | ▼ 42.58% |