Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼7.46ms] Passed 4 tests
Analyzing server-side resources used by f(x) Login Customizer
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 38.89 ▼4.71 |
| Dashboard /wp-admin | 3.34 ▼0.01 | 52.42 ▼11.12 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 46.65 ▼2.83 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 89.41 ▼11.17 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 41.42 ▲3.05 |
| Customize Login /wp-admin/customize.php?url=http%3A%2F%2Fwp.com%2Fwp-login.php | 5.71 | 159.63 |
Server storage [IO: ▲0.03MB] [DB: ▲0.01MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by f(x) Login Customizer
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,821 ▲60 | 13.25 ▼1.40 | 4.86 ▲2.94 | 44.52 ▲4.68 |
| Dashboard /wp-admin | 2,225 ▲19 | 5.86 ▼0.02 | 103.93 ▲0.41 | 39.81 ▲2.75 |
| Posts /wp-admin/edit.php | 2,104 ▲1 | 1.99 ▼0.03 | 36.06 ▼6.74 | 34.41 ▼6.77 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲17 | 22.94 ▼0.18 | 661.01 ▲30.95 | 58.06 ▲9.20 |
| Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.27 ▲0.16 | 109.49 ▼8.30 | 48.49 ▲1.24 |
| Customize Login /wp-admin/customize.php?url=http%3A%2F%2Fwp.com%2Fwp-login.php | 7,319 | 26.40 | 615.55 | 96.94 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 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
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Almost there, just fix the following server-side errors
- > GET request to /wp-admin/customize.php?url=http%3A%2F%2Fwp.com%2Fwp-login.php
- > User deprecated in wp-includes/functions.php+5828
Hook login_headertitle is deprecated since version 5.2.0! Use login_headertext instead. Usage of the title attribute on the login logo is not recommended for accessibility reasons. Use the link text instead.
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
Please take a closer look at the following
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function trailingslashit() in wp-content/plugins/fx-login-customizer/fx-login-customizer.php:29
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/fx-login-customizer/includes/customizer.php:8
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
These are user-side errors you should fix
- > GET request to /wp-admin/customize.php?url=http%3A%2F%2Fwp.com%2Fwp-login.php
- > Security (warning) in unknown
/wp-login.php?customize_changeset_uuid=87832968-00e6-4ddd-947e-c1eb19426ba2&customize_theme=twentytwentyone&customize_messenger_channel=preview-0 - An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
3 plugin tags: members only, protect rss, private site
fx-login-customizer/fx-login-customizer.php Passed 13 tests
The primary PHP file in "f(x) Login Customizer" version 1.0.1 is used by WordPress to initiate all plugin functionality
34 characters long description:
Customize login page with preview.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin210 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 59 | 126 | 170 |
| PO File | 1 | 5 | 5 | 27 |
| Markdown | 1 | 4 | 0 | 13 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.36 |
| 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 | 11 | |
| ▷ Named functions | 11 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 3 | |
| ▷ Global constants | 3 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin