Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▼0.84MB] [CPU: ▼26.37ms] Passed 4 tests
Analyzing server-side resources used by Front Profile Builder
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.58 ▲0.12 | 47.38 ▲8.90 |
| Dashboard /wp-admin | 3.11 ▼0.20 | 34.65 ▼19.04 |
| Posts /wp-admin/edit.php | 3.11 ▼0.25 | 29.83 ▼22.42 |
| Add New Post /wp-admin/post-new.php | 3.11 ▼2.78 | 31.26 ▼58.96 |
| Media Library /wp-admin/upload.php | 3.11 ▼0.12 | 27.85 ▼5.04 |
| Front Profile Builder /wp-admin/admin.php?page=custom_profilebuilder | 3.11 | 30.10 |
| Profile Builder Pro /wp-admin/admin.php?page=profile-builder-pro-menu | 3.11 | 32.10 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 14 new files
Database: no new tables, 11 new options
| New WordPress options |
|---|
| db_upgraded |
| passwordreset-form |
| passwordlost-form |
| editprofile-form |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| registration-form |
| login-form |
| ... |
Browser metrics Passed 4 tests
A check of browser resources used by Front Profile Builder
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,812 ▲51 | 14.35 ▼0.01 | 1.90 ▲0.18 | 43.33 ▼1.25 |
| Dashboard /wp-admin | 2,221 ▲41 | 5.60 ▼0.06 | 89.53 ▼12.75 | 42.18 ▼0.64 |
| Posts /wp-admin/edit.php | 2,120 ▲23 | 2.02 ▲0.01 | 37.51 ▼0.61 | 35.80 ▼0.40 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲17 | 23.11 ▼0.06 | 675.64 ▲38.23 | 55.20 ▲3.41 |
| Media Library /wp-admin/upload.php | 1,426 ▲23 | 4.18 ▼0.00 | 101.14 ▲2.34 | 41.27 ▼1.78 |
| Front Profile Builder /wp-admin/admin.php?page=custom_profilebuilder | 781 | 2.02 | 24.92 | 28.07 |
| Profile Builder Pro /wp-admin/admin.php?page=profile-builder-pro-menu | 868 | 1.99 | 23.15 | 30.33 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin did not uninstall without warnings or errors
- > User deprecated in wp-includes/functions.php+5453
Function add_object_page is deprecated since version 4.5.0! Use add_menu_page() instead.
- This plugin did not uninstall successfully, leaving 11 options in the database
- registration-form
- db_upgraded
- theysaidso_admin_options
- login-form
- editprofile-form
- can_compress_scripts
- passwordlost-form
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- ...
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These server-side errors were triggered
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=profile-builder-pro-menu
- > User deprecated in wp-includes/functions.php+5453
Function add_object_page is deprecated since version 4.5.0! Use add_menu_page() instead.
SRP 0% 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
Please fix the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/front-profile-builder/includes/frontprofile_builder_pro.php
- 5× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/front-profile-builder/includes/frontend_edit_user_profile.php:184
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/front-profile-builder/gen-frontprofile-builder.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/front-profile-builder/includes/password_lost.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/front-profile-builder/includes/password_reset.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/front-profile-builder/includes/front-end-registration-login.php:29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Please fix the following attributes:
- Requires at least: Version not formatted correctly
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Login- Front end Custom login), #2 (Register - Edit profile), #3 (Lost password), #4 (Reset Password)
- Tags: Please delete some tags, you are using 11 tag instead of maximum 10
front-profile-builder/gen-frontprofile-builder.php 85% from 13 tests
The main PHP script in "Front Profile Builder" version 1.0 is automatically included on every request by WordPress
The following require your attention:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Main file name: Name the main plugin file the same as the plugin slug ("front-profile-builder.php" instead of "gen-frontprofile-builder.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
No dangerous file extensions were detected683 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 8 | 107 | 182 | 683 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| 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 | 26 | |
| ▷ Named functions | 26 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 8 | |
| ▷ Global constants | 8 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
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 |
| screenshot-3.png | 9.91KB | 4.47KB | ▼ 54.89% |
| screenshot-1.png | 10.50KB | 4.20KB | ▼ 60.02% |
| screenshot-2.png | 13.11KB | 4.64KB | ▼ 64.63% |
| screenshot-4.png | 10.93KB | 5.54KB | ▼ 49.29% |