Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼11.63ms] Passed 4 tests
Server-side resources used by 360 Product Viewer for WooCommerce
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 37.50 ▼19.64 |
Dashboard /wp-admin | 3.31 ▲0.00 | 45.77 ▼7.16 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 45.92 ▼2.20 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 82.78 ▼17.51 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.00 ▼0.54 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 48 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
db_upgraded |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for 360 Product Viewer for WooCommerce
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 14.44 ▼0.15 | 1.79 ▼0.41 | 44.54 ▲1.66 |
Dashboard /wp-admin | 2,206 ▲21 | 4.84 ▼1.02 | 101.99 ▲1.32 | 40.46 ▼1.34 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.03 ▲0.03 | 36.20 ▲0.35 | 32.62 ▼6.56 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.24 ▲0.18 | 666.65 ▼8.21 | 57.78 ▲3.99 |
Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.24 ▲0.04 | 94.42 ▼17.93 | 43.95 ▼4.68 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Looking good! No server-side errors or output on direct access of PHP files
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
5 plugin tags: 360viewproduct, woocommerce, woocommerceproducts, 360, threesixty
360-product-viewer-for-woocommerce/wp_360view.php 85% from 13 tests
"360 Product Viewer for WooCommerce" version 1.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("360-product-viewer-for-woocommerce.php" instead of "wp_360view.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
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
Good job! No executable or dangerous file extensions detected3,054 lines of code in 28 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 5 | 115 | 227 | 1,246 |
JavaScript | 6 | 201 | 510 | 1,138 |
PHP | 16 | 320 | 496 | 669 |
Markdown | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 5.33 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 27.00 |
Average method complexity | 2.49 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 27.00 |
Code structure | ||
---|---|---|
Namespaces | 6 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 12 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 12 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 35 | |
▷ Static methods | 6 | 17.14% |
▷ Public methods | 33 | 94.29% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 5.71% |
Functions | 10 | |
▷ Named functions | 8 | 80.00% |
▷ Anonymous functions | 2 | 20.00% |
Constants | 8 | |
▷ Global constants | 4 | 50.00% |
▷ Class constants | 4 | 50.00% |
▷ Public constants | 4 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
16 PNG files occupy 0.04MB with 0.02MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/hand_open.png | 1.18KB | 0.74KB | ▼ 37.10% |
images/sprite-left.png | 1.72KB | 0.93KB | ▼ 46.02% |
images/sprites.png | 3.52KB | 1.26KB | ▼ 64.06% |
images/close.png | 6.10KB | 3.08KB | ▼ 49.54% |
images/sprite-play.png | 1.50KB | 0.93KB | ▼ 37.66% |