Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.35MB] [CPU: ▼3.63ms] Passed 4 tests
An overview of server-side resources used by WPSSO Google Merchant Feed XML
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.84 ▲0.38 | 36.90 ▼2.78 |
| Dashboard /wp-admin | 3.69 ▲0.39 | 48.55 ▼18.88 |
| Posts /wp-admin/edit.php | 3.75 ▲0.39 | 50.43 ▲4.99 |
| Add New Post /wp-admin/post-new.php | 6.21 ▲0.33 | 93.65 ▲2.17 |
| Media Library /wp-admin/upload.php | 3.55 ▲0.33 | 38.41 ▲5.65 |
Server storage [IO: ▲0.44MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 100 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WPSSO Google Merchant Feed XML
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,796 ▲34 | 14.72 ▲0.08 | 1.74 ▲0.10 | 37.28 ▼9.22 |
| Dashboard /wp-admin | 2,201 ▲24 | 5.62 ▼0.07 | 98.15 ▲6.69 | 42.39 ▲0.63 |
| Posts /wp-admin/edit.php | 2,106 ▲6 | 1.97 ▼0.04 | 40.07 ▼1.78 | 37.34 ▲1.36 |
| Add New Post /wp-admin/post-new.php | 1,532 ▲6 | 23.22 ▲0.11 | 750.80 ▲132.09 | 47.62 ▼12.85 |
| Media Library /wp-admin/upload.php | 1,409 ▲12 | 4.28 ▲0.06 | 98.29 ▲0.14 | 42.24 ▲1.99 |
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
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following items
- 15× PHP files perform the action of outputting non-empty strings when accessed directly (only 10 are shown):
- > /wp-content/plugins/wpsso-google-merchant-feed/lib/register.php
- > /wp-content/plugins/wpsso-google-merchant-feed/gettext/gettext-lib-config.php
- > /wp-content/plugins/wpsso-google-merchant-feed/lib/abstract/add-on.php
- > /wp-content/plugins/wpsso-google-merchant-feed/lib/abstract/com/add-on.php
- > /wp-content/plugins/wpsso-google-merchant-feed/lib/actions.php
- > /wp-content/plugins/wpsso-google-merchant-feed/lib/filters.php
- > /wp-content/plugins/wpsso-google-merchant-feed/lib/submenu/google-merchant.php
- > /wp-content/plugins/wpsso-google-merchant-feed/lib/filters-edit.php
- > /wp-content/plugins/wpsso-google-merchant-feed/gettext/gettext-lib-abstract-com.php
- > /wp-content/plugins/wpsso-google-merchant-feed/wpsso-google-merchant-feed.php
- 20× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Trait 'Vitalybaev\\GoogleMerchant\\HasProperties' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/src/Inventory.php on line 5
- > PHP Fatal error
Trait 'Vitalybaev\\GoogleMerchant\\HasProperties' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/src/PropertyBag.php on line 5
- > PHP Fatal error
Uncaught Error: Interface 'Sabre\\Xml\\Element' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/sabre/xml/lib/Element/Uri.php:25
- > PHP Fatal error
Uncaught Error: Class 'Vitalybaev\\GoogleMerchant\\Product' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/src/Meta/Product.php:12
- > PHP Fatal error
require(): Failed opening required 'wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/tests/../vendor/autoload.php' (include_path='.:/usr/share/php') in wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/tests/bootstrap.php on line 3
- > PHP Fatal error
Uncaught Error: Interface 'Sabre\\Xml\\Element' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/sabre/xml/lib/Element/KeyValue.php:38
- > PHP Fatal error
Uncaught Error: Interface 'Sabre\\Xml\\XmlSerializable' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/sabre/xml/lib/Element/Cdata.php:22
- > PHP Fatal error
Uncaught Error: Interface 'Sabre\\Xml\\XmlSerializable' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/src/RssElement.php:5
- > PHP Warning
require(wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/tests/../vendor/autoload.php): failed to open stream: No such file or directory in wp-content/plugins/wpsso-google-merchant-feed/vendor/vitalybaev/google-merchant-feed/tests/bootstrap.php on line 3
- > PHP Fatal error
Uncaught Error: Interface 'Sabre\\Xml\\Element' not found in wp-content/plugins/wpsso-google-merchant-feed/vendor/sabre/xml/lib/Element/Elements.php:38
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
8 plugin tags: google shopping, easy digital downloads, polylang, google merchant center, woocommerce product feed...
wpsso-google-merchant-feed/wpsso-google-merchant-feed.php Passed 13 tests
This is the main PHP file of "WPSSO Google Merchant Feed XML" version 9.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
120 characters long description:
Google Merchant product and inventory feed XML for WooCommerce and custom product pages, including multilingual support.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin5,000 lines of code in 81 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 66 | 1,415 | 2,807 | 4,151 |
| JSON | 6 | 0 | 0 | 355 |
| Markdown | 3 | 62 | 0 | 203 |
| PO File | 1 | 70 | 73 | 176 |
| YAML | 2 | 12 | 2 | 72 |
| HTML | 2 | 32 | 0 | 30 |
| XML | 1 | 0 | 0 | 13 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 9.18 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 79.00 |
| Average method complexity | 2.70 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 25.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 12 | |
| Interfaces | 3 | |
| Traits | 2 | |
| Classes | 46 | |
| ▷ Abstract classes | 2 | 4.35% |
| ▷ Concrete classes | 44 | 95.65% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 247 | |
| ▷ Static methods | 49 | 19.84% |
| ▷ Public methods | 224 | 90.69% |
| ▷ Protected methods | 9 | 3.64% |
| ▷ Private methods | 14 | 5.67% |
| Functions | 25 | |
| ▷ Named functions | 18 | 72.00% |
| ▷ Anonymous functions | 7 | 28.00% |
| Constants | 22 | |
| ▷ Global constants | 7 | 31.82% |
| ▷ Class constants | 15 | 68.18% |
| ▷ Public constants | 15 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.04MB with 0.03MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| images/icon-128x128.png | 13.57KB | 5.74KB | ▼ 57.71% |
| images/icon-256x256.png | 30.77KB | 12.98KB | ▼ 57.82% |