Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▼0.19MB] [CPU: ▲289.65ms] 75% from 4 tests
This is a short check of server-side resources used by Gravatar Google Image
Please have a look at the following items
- Extra CPU: Try to keep extra CPU usage under 200.00ms (currently 289.65ms on /wp-admin/upload.php)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.40 ▼0.06 | 342.72 ▲302.70 |
Dashboard /wp-admin | 3.13 ▼0.17 | 349.31 ▲294.99 |
Posts /wp-admin/edit.php | 3.26 ▼0.10 | 333.56 ▲285.28 |
Add New Post /wp-admin/post-new.php | 5.45 ▼0.43 | 370.19 ▲275.62 |
Media Library /wp-admin/upload.php | 3.19 ▼0.04 | 344.10 ▲308.73 |
Server storage [IO: ▲0.06MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 6 new files
Database: no new tables, 9 new options
New WordPress options |
---|
widget_recent-comments |
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
avatar_google |
gravatars_cache |
avatar_default_save |
widget_theysaidso_widget |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Gravatar Google Image
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,815 ▲80 | 13.33 ▼1.05 | 2.31 ▲0.63 | 37.69 ▼7.47 |
Dashboard /wp-admin | 2,209 ▲17 | 5.82 ▲0.71 | 92.64 ▼18.79 | 80.39 ▲33.10 |
Posts /wp-admin/edit.php | 2,092 ▲6 | 2.00 ▲0.03 | 33.64 ▼2.25 | 33.44 ▲2.69 |
Add New Post /wp-admin/post-new.php | 1,528 ▲14 | 18.41 ▲0.99 | 670.66 ▼7.00 | 64.46 ▲10.84 |
Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.23 ▲0.01 | 103.46 ▲2.25 | 49.69 ▲8.91 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- This plugin does not fully uninstall, leaving 9 options in the database
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- avatar_default_save
- gravatars_cache
- widget_theysaidso_widget
- avatar_google
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
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
Almost there! Just fix the following items
- 1× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/baw-gravatar-google-image/tyniaf.php
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_upload_dir() in wp-content/plugins/baw-gravatar-google-image/bawggi.php:11
- > 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)
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need your attention:
- Screenshots: Please add descriptions for these screenshots #2, #3, #4, #5 in baw-gravatar-google-image/assets to your readme.txt
baw-gravatar-google-image/bawggi.php 92% from 13 tests
The primary PHP file in "Gravatar Google Image" version 1.9.3 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("baw-gravatar-google-image.php" instead of "bawggi.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin633 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 41 | 9 | 519 |
PO File | 1 | 38 | 58 | 94 |
JavaScript | 1 | 1 | 0 | 20 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
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 | 21 | |
▷ Named functions | 21 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 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
No PNG files were detected