Benchmarks
Plugin footprint Passed 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.07MB] [CPU: ▼146.11ms] Passed 4 tests
Analyzing server-side resources used by Simple Login Screen Customizer
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.89 ▲0.17 | 39.02 ▲15.53 |
| Dashboard /wp-admin | 3.12 ▲0.06 | 49.24 ▼5.84 |
| Posts /wp-admin/edit.php | 3.20 ▲0.10 | 53.17 ▼2.84 |
| Add New Post /wp-admin/post-new.php | 5.48 ▲0.04 | 101.50 ▼574.56 |
| Media Library /wp-admin/upload.php | 3.06 ▲0.06 | 38.67 ▼1.19 |
| Login Screen /wp-admin/options-general.php?page=simpleloginscreencustomizer_plugin_options | 3.06 | 37.63 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 13 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| simpleloginscreencustomizer_plugin_display_options |
Browser metrics Passed 4 tests
Checking browser requirements for Simple Login Screen Customizer
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,711 ▲139 | 15.85 ▲0.46 | 15.20 ▲1.86 | 52.21 ▼1.46 |
| Dashboard /wp-admin | 2,972 ▲40 | 5.91 ▼0.01 | 153.32 ▼32.69 | 121.71 ▲4.71 |
| Posts /wp-admin/edit.php | 2,744 ▲5 | 2.72 ▲0.01 | 80.59 ▲0.87 | 92.75 ▼3.86 |
| Add New Post /wp-admin/post-new.php | 1,686 ▲105 | 18.56 ▼0.40 | 452.51 ▲29.27 | 121.27 ▲1.30 |
| Media Library /wp-admin/upload.php | 1,753 ▼54 | 5.00 ▼0.03 | 166.10 ▲2.42 | 120.55 ▼11.43 |
| Login Screen /wp-admin/options-general.php?page=simpleloginscreencustomizer_plugin_options | 1,967 | 4.64 | 127.59 | 101.51 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The plugin uninstalled completely, with no zombie files or tables
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
These errors were triggered by the plugin
- > GET request to /wp-admin/options-general.php?page=simpleloginscreencustomizer_plugin_options
- > User deprecated in wp-includes/functions.php+5221
screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=simpleloginscreencustomizer_plugin_options
- > User deprecated in wp-includes/functions.php+5221
get_screen_icon is deprecated since version 3.8.0 with no alternative available.
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=simpleloginscreencustomizer_plugin_options
- > Notice in wp-content/plugins/simple-login-screen-customizer/simple-login-screen-customizer-admin.php+140
Trying to access array offset on value of type null
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
The following issues need your attention
- 3× 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/simple-login-screen-customizer/simple-login-screen-customizer-admin.php:35
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/simple-login-screen-customizer/simple-login-screen-customizer-public.php:73
- > PHP Fatal error
Uncaught Error: Call to undefined function screen_icon() in wp-content/plugins/simple-login-screen-customizer/views/admin.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
6 plugin tags: custom colors, login screen, logo, customize, login...
simple-login-screen-customizer/simple-login-screen-customizer.php 92% from 13 tests
The entry point to "Simple Login Screen Customizer" version 1.0.4 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- 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
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Success! There were no dangerous files found in this plugin405 lines of code in 9 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 75 | 102 | 329 |
| PO File | 1 | 14 | 14 | 45 |
| JavaScript | 2 | 8 | 4 | 31 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.14 |
| 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 | 22 | |
| ▷ Named functions | 22 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin