Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼6.18ms] Passed 4 tests
Analyzing server-side resources used by Woostagram Connect
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 35.07 ▼6.09 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 44.92 ▼7.30 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 46.75 ▲0.44 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 86.53 ▼11.78 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.21 ▲0.83 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Woostagram Connect
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 14.51 ▲0.20 | 1.84 ▲0.15 | 42.20 ▼1.86 |
| Dashboard /wp-admin | 2,203 ▲14 | 5.83 ▲0.87 | 93.54 ▼31.76 | 37.91 ▼6.42 |
| Posts /wp-admin/edit.php | 2,092 ▲24 | 2.05 ▲0.04 | 40.48 ▲4.52 | 33.53 ▲1.21 |
| Add New Post /wp-admin/post-new.php | 1,532 ▼6 | 23.40 ▲0.29 | 640.33 ▼43.60 | 50.50 ▼9.12 |
| Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.28 ▲0.10 | 96.01 ▼3.07 | 40.59 ▼3.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please fix the following items
- 5× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/woostagram-connect/navigation/options.php
- > /wp-content/plugins/woostagram-connect/navigation/view_feed_woostagram.php
- > /wp-content/plugins/woostagram-connect/woostagram.php
- > /wp-content/plugins/woostagram-connect/oauth/auth.php
- > /wp-content/plugins/woostagram-connect/navigation/view_woostagram_connect.php
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
4 plugin tags: instagram, commerce, woocommerce, import
woostagram-connect/woostagram.php 92% from 13 tests
The main file in "Woostagram Connect" v. 1.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("woostagram-connect.php" instead of "woostagram.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected403 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 6 | 75 | 113 | 386 |
| JavaScript | 1 | 4 | 3 | 17 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.21 |
| Average class complexity | 5.33 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 9.00 |
| Average method complexity | 1.83 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 2 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 13 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 12 | 92.31% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 7.69% |
| Functions | 4 | |
| ▷ Named functions | 3 | 75.00% |
| ▷ Anonymous functions | 1 | 25.00% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| img/instagram.png | 2.17KB | 1.26KB | ▼ 42.20% |