Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼0.85ms] Passed 4 tests
Analyzing server-side resources used by WooCommerce View
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.06 | 43.21 ▼2.84 |
Dashboard /wp-admin | 3.37 ▲0.07 | 56.92 ▲3.66 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 50.38 ▲1.01 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 92.13 ▼4.54 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 41.37 ▲2.99 |
Server storage [IO: ▲0.73MB] [DB: ▲0.00MB] 67% from 3 tests
Filesystem and database footprint
Just a few items left to fix
- You have illegally modified 1 file (4.00KB) outside of "wp-content/plugins/woocommerce-view/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by WooCommerce View
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,815 ▲54 | 13.17 ▼1.58 | 1.73 ▼0.15 | 43.98 ▼1.10 |
Dashboard /wp-admin | 2,215 ▲12 | 4.84 ▼0.14 | 107.30 ▼10.70 | 39.91 ▼4.02 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.05 ▲0.05 | 39.45 ▲2.40 | 34.28 ▼1.63 |
Add New Post /wp-admin/post-new.php | 1,550 ▲3 | 23.40 ▲0.06 | 647.77 ▼54.96 | 56.18 ▲2.05 |
Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.25 ▲0.03 | 107.76 ▲1.21 | 47.03 ▲0.30 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- 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 no errors were found, this is by no means an exhaustive test
SRP 50% 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
Please fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/woocommerce-view/view.php:34
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Screenshots: These screenshots require images: #1 (List View), #2 (Date View), #3 (Grid View), #4 (Map View)
woocommerce-view/view.php 69% from 13 tests
"WooCommerce View" version 1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Domain Path: The domain path folder does not exist ("/languages/")
- Requires at least: Required version does not match the one declared in readme.txt ("3.0.1" instead of "3.1")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("woocommerce-view.php" instead of "view.php")
- Text Domain: The text domain name must use dashes instead of underscores, and it must be lowercase
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
Everything looks great! No dangerous files found in this plugin2,014 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 4 | 186 | 432 | 1,445 |
PHP | 1 | 87 | 27 | 391 |
CSS | 1 | 54 | 8 | 178 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 46.00 |
▷ Minimum class complexity | 46.00 |
▷ Maximum class complexity | 46.00 |
Average method complexity | 3.65 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 10.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 | 17 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 17 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
All PNG images should be compressed to minimize bandwidth usage for end users
6 PNG files occupy 0.62MB with 0.42MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-4.png | 203.26KB | 71.30KB | ▼ 64.92% |
screenshot-1.png | 90.85KB | 31.52KB | ▼ 65.30% |
assets/images/icon.png | 12.52KB | 3.53KB | ▼ 71.80% |
screenshot-3.png | 238.24KB | 78.74KB | ▼ 66.95% |
screenshot-2.png | 92.44KB | 32.47KB | ▼ 64.87% |