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.18MB] [CPU: ▼3.98ms] Passed 4 tests
A check of server-side resources used by 3DVieweronline
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.67 ▲0.16 | 41.86 ▼1.75 |
Dashboard /wp-admin | 4.82 ▲1.48 | 184,252.87 ▲184,199.17 |
Posts /wp-admin/edit.php | 3.62 ▲0.22 | 60.96 ▲4.54 |
Add New Post /wp-admin/post-new.php | 6.10 ▲0.17 | 90.28 ▼19.13 |
Media Library /wp-admin/upload.php | 3.43 ▲0.16 | 39.16 ▲0.43 |
Server storage [IO: ▲1.66MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 50 new files
Database: no new tables, 7 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
settings-threed-iframe |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for 3DVieweronline
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,938 ▲177 | 13.60 ▼0.62 | 11.03 ▲9.35 | 40.87 ▼4.04 |
Dashboard /wp-admin | 2,206 ▲32 | 5.80 ▲0.15 | 83.40 ▼10.38 | 77.78 ▲33.75 |
Posts /wp-admin/edit.php | 2,129 ▲29 | 2.01 ▲0.03 | 37.24 ▲1.15 | 37.17 ▼0.92 |
Add New Post /wp-admin/post-new.php | 6,388 ▲4,860 | 27.54 ▲4.60 | 978.81 ▲286.20 | 43.09 ▼25.08 |
Media Library /wp-admin/upload.php | 1,426 ▲26 | 4.15 ▼0.06 | 116.99 ▲2.41 | 68.59 ▲20.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
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Good news, no errors were detected
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
Please fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/3dvieweronline-wp/admin/partials/threedvieweronline-iframe-admin-display.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
6 plugin tags: 3dvieweronline, 3d e-commerce, woocommerce 3d viewer, 3d product viewer, 3d viewer...
3dvieweronline-wp/threedvieweronline-iframe.php 77% from 13 tests
The main PHP file in "3DVieweronline" ver. 2.2.2 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 149 characters long)
- 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
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("3dvieweronline-wp.php" instead of "threedvieweronline-iframe.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
Good job! No executable or dangerous file extensions detected15,627 lines of code in 32 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 2 | 0 | 0 | 7,134 |
JavaScript | 10 | 1,218 | 671 | 4,113 |
SVG | 1 | 0 | 0 | 2,671 |
CSS | 6 | 141 | 27 | 918 |
PHP | 12 | 263 | 590 | 777 |
Sass | 1 | 1 | 0 | 14 |
PHP code Passed 2 tests
This is a short overview 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.32 |
Average class complexity | 11.57 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 36.00 |
Average method complexity | 2.23 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 60 | |
▷ Static methods | 3 | 5.00% |
▷ Public methods | 53 | 88.33% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 7 | 11.67% |
Functions | 3 | |
▷ Named functions | 3 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/custom-icon.png | 1.53KB | 0.29KB | ▼ 80.80% |
assets/images/icon.png | 1.03KB | 0.56KB | ▼ 46.07% |
assets/images/logo.png | 0.46KB | 0.41KB | ▼ 12.24% |