Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.94ms] Passed 4 tests
A check of server-side resources used by Login Logo Editor
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.76 ▼0.50 |
Dashboard /wp-admin | 3.32 ▲0.02 | 49.54 ▼1.64 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.81 ▲5.56 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 81.98 ▼23.67 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.04 ▼1.94 |
Login Logo /wp-admin/options-general.php?page=login_logo_editor | 3.29 | 34.99 |
Server storage [IO: ▲0.05MB] [DB: ▲0.07MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 9 new files
Database: no new tables, 10 new options
New WordPress options |
---|
widget_theysaidso_widget |
db_upgraded |
widget_recent-comments |
widget_recent-posts |
can_compress_scripts |
lle_login_logo_title |
lle_login_logo_img |
lle_login_logo_link |
theysaidso_admin_options |
lle_login_logo_css |
Browser metrics Passed 4 tests
Login Logo Editor: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,796 ▲50 | 13.20 ▼1.43 | 1.57 ▼0.35 | 37.91 ▼5.42 |
Dashboard /wp-admin | 2,210 ▲21 | 5.86 ▲0.98 | 96.62 ▼8.65 | 37.45 ▼4.28 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.05 ▲0.01 | 38.93 ▼1.13 | 34.24 ▼2.82 |
Add New Post /wp-admin/post-new.php | 1,531 ▲3 | 23.41 ▲4.98 | 674.75 ▲70.66 | 51.47 ▼1.63 |
Media Library /wp-admin/upload.php | 1,395 ▲10 | 4.18 ▼0.01 | 91.32 ▼8.53 | 40.42 ▼3.76 |
Login Logo /wp-admin/options-general.php?page=login_logo_editor | 1,086 | 3.15 | 39.08 | 56.54 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 6 options
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- can_compress_scripts
- db_upgraded
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)
Even though everything seems fine, this is not an exhaustive test
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
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/login-logo-editor-by-oizuled/login-logo-by-oizuled.php:33
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/login-logo-editor-by-oizuled/options.php:4
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
Optimizations
Plugin configuration 96% from 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
6 plugin tags: customize, login screen, logo, login, plugin...
login-logo-editor-by-oizuled/login-logo-by-oizuled.php 92% from 13 tests
"Login Logo Editor" version 1.3.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("login-logo-editor-by-oizuled.php" instead of "login-logo-by-oizuled.php")
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
Everything looks great! No dangerous files found in this plugin228 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 21 | 54 | 173 |
CSS | 1 | 1 | 0 | 33 |
JavaScript | 1 | 12 | 4 | 22 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
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 | 12 | |
▷ Named functions | 12 | 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
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 |
w-logo-blue.png | 4.60KB | 3.09KB | ▼ 32.80% |
wordpress-logo.png | 4.75KB | 5.22KB | 0.00% |