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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.03MB] [CPU: ▼143.82ms] Passed 4 tests
A check of server-side resources used by Pinterest Widget
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.87 ▲0.03 | 31.77 ▲0.33 |
| Dashboard /wp-admin | 3.09 ▲0.04 | 40.94 ▼2.78 |
| Posts /wp-admin/edit.php | 3.14 ▲0.03 | 38.03 ▼6.60 |
| Add New Post /wp-admin/post-new.php | 5.45 ▲0.01 | 90.53 ▼566.23 |
| Media Library /wp-admin/upload.php | 3.03 ▲0.03 | 34.37 ▲1.38 |
Server storage [IO: ▲1.40MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 8 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| widget_pinterest_widget |
Browser metrics Passed 4 tests
Checking browser requirements for Pinterest Widget
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,679 ▲83 | 15.86 ▲0.39 | 7.29 ▼3.31 | 49.39 ▼2.14 |
| Dashboard /wp-admin | 2,973 ▲42 | 5.84 ▼0.09 | 139.51 ▼2.24 | 121.85 ▲1.55 |
| Posts /wp-admin/edit.php | 2,739 ▼0 | 2.68 ▼0.02 | 62.21 ▼3.72 | 86.55 ▼8.10 |
| Add New Post /wp-admin/post-new.php | 1,876 ▲4 | 19.40 ▲0.07 | 388.51 ▲1.61 | 105.88 ▼3.38 |
| Media Library /wp-admin/upload.php | 1,807 ▼0 | 5.01 ▲0.01 | 144.85 ▼5.88 | 126.64 ▲8.59 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 1 option in the database
- widget_pinterest_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
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
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/pinterest-widget/pinterest_widget.php:14
- > 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 errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 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
These attributes need your attention:
- Requires at least: Version format is invalid
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Screenshot of the front end), #2 (Screen shot of Backend)
pinterest-widget/pinterest_widget.php 92% from 13 tests
The main PHP script in "Pinterest Widget" version 3.5.0 is automatically included on every request by WordPress
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("pinterest-widget.php" instead of "pinterest_widget.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 plugin311 lines of code in 5 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 28 | 19 | 139 |
| PHP | 1 | 35 | 36 | 114 |
| CSS | 1 | 16 | 0 | 31 |
| JSON | 1 | 0 | 0 | 27 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.18 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 11.00 |
| ▷ Maximum class complexity | 11.00 |
| Average method complexity | 2.43 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 5.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 7 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 7 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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 50% from 2 tests
Image compression 50% from 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 1.38MB with 0.88MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 25.66KB | 12.72KB | ▼ 50.42% |
| screenshot-1.png | 1,388.17KB | 314.09KB | ▼ 77.37% |