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.00MB] [CPU: ▼3.06ms] Passed 4 tests
A check of server-side resources used by Viber Sharing Button for Jetpack
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 33.50 ▼7.89 |
Dashboard /wp-admin | 3.31 ▲0.00 | 44.88 ▼5.88 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 48.44 ▲1.56 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 92.98 ▲5.27 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.47 ▼0.02 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 22 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Viber Sharing Button for Jetpack
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.21 ▼1.21 | 4.46 ▲2.62 | 40.55 ▼5.30 |
Dashboard /wp-admin | 2,209 ▲18 | 5.89 ▼0.01 | 95.74 ▼4.89 | 41.17 ▼7.07 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.06 ▲0.01 | 39.43 ▲6.29 | 35.51 ▲2.52 |
Add New Post /wp-admin/post-new.php | 1,547 ▲28 | 18.36 ▼4.88 | 645.85 ▼38.65 | 65.99 ▲14.45 |
Media Library /wp-admin/upload.php | 1,382 ▼3 | 4.19 ▼0.02 | 95.72 ▼3.93 | 41.44 ▼2.10 |
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
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 3× GET requests to PHP files return non-empty strings:
- > /wp-content/plugins/viber-sharing-button-for-jetpack/includes/class.viber-source.php
- > /wp-content/plugins/viber-sharing-button-for-jetpack/jetpack-viber.php
- > /wp-content/plugins/viber-sharing-button-for-jetpack/includes/class.viber-service.php
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 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
10 plugin tags: viber sharing button for jetpack, social, viber, jetpack sharing, viber button for jetpack sharing...
viber-sharing-button-for-jetpack/jetpack-viber.php 85% from 13 tests
"Viber Sharing Button for Jetpack" version 1.1.3's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("viber-sharing-button-for-jetpack.php" instead of "jetpack-viber.php")
- 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 review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected334 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 52 | 22 | 217 |
CSS | 1 | 11 | 8 | 81 |
PO File | 1 | 9 | 12 | 35 |
JavaScript | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.29 |
Average class complexity | 7.33 |
▷ Minimum class complexity | 4.00 |
▷ Maximum class complexity | 13.00 |
Average method complexity | 1.86 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 3.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 22 | |
▷ Static methods | 4 | 18.18% |
▷ Public methods | 20 | 90.91% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 9.09% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.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
10 PNG files occupy 0.03MB with 0.01MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/shape-white.png | 1.30KB | 0.76KB | ▼ 41.15% |
assets/images/rectangle-ja.png | 2.34KB | 0.90KB | ▼ 61.39% |
assets/images/shape@2x.png | 1.98KB | 1.41KB | ▼ 28.80% |
assets/images/shape.png | 1.58KB | 0.92KB | ▼ 41.87% |
assets/images/rectangle-ja@2x.png | 4.01KB | 1.77KB | ▼ 55.93% |