Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.62ms] Passed 4 tests
Server-side resources used by Jetpack Widget Visibility - WPML Languages
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 49.67 ▲10.58 |
Dashboard /wp-admin | 3.31 ▲0.01 | 42.28 ▼8.90 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 42.31 ▼2.67 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 80.98 ▼18.67 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 29.62 ▼0.22 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Jetpack Widget Visibility - WPML Languages
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 14.44 ▲0.06 | 2.00 ▲0.24 | 63.63 ▲13.00 |
Dashboard /wp-admin | 2,206 ▲21 | 5.86 ▲1.01 | 112.56 ▲0.57 | 42.78 ▲1.28 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▼0.05 | 38.99 ▼1.26 | 33.94 ▼0.50 |
Add New Post /wp-admin/post-new.php | 1,533 ▲10 | 23.41 ▲0.26 | 676.19 ▲43.00 | 50.13 ▼25.83 |
Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.20 ▼0.11 | 95.13 ▼3.64 | 41.78 ▼0.95 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
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
Please take a closer look at the following
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/jetpack-widget-visibility-additional-fields-wpml-language/jetpack-widget-visibility-wpml-lang.php:39
- > 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)
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
4 plugin tags: extend, widget, jetpack, visibility
jetpack-widget-visibility-additional-fields-wpml-language/jetpack-widget-visibility-wpml-lang.php 92% from 13 tests
The main PHP file in "Jetpack Widget Visibility - WPML Languages" ver. 1.0.0 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("jetpack-widget-visibility-additional-fields-wpml-language.php" instead of "jetpack-widget-visibility-wpml-lang.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Success! There were no dangerous files found in this plugin24 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 10 | 8 | 24 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.23 |
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 | 3 | |
▷ Named functions | 3 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.03MB with 0.02MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 35.40KB | 10.20KB | ▼ 71.19% |