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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.05MB] [CPU: ▼8.77ms] Passed 4 tests
An overview of server-side resources used by Pure Feed Widget
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 39.95 ▲4.77 |
| Dashboard /wp-admin | 3.36 ▲0.02 | 47.07 ▼12.17 |
| Posts /wp-admin/edit.php | 3.41 ▲0.06 | 42.72 ▼4.25 |
| Add New Post /wp-admin/post-new.php | 5.94 ▲0.06 | 78.55 ▼18.76 |
| Media Library /wp-admin/upload.php | 3.28 ▲0.06 | 32.56 ▲0.09 |
Server storage [IO: ▲1.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 26 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| widget_pure_widget |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for Pure Feed Widget
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,825 ▲54 | 13.20 ▼1.20 | 2.05 ▲0.32 | 45.03 ▲3.02 |
| Dashboard /wp-admin | 2,206 ▲24 | 4.84 ▼1.06 | 104.09 ▲4.17 | 41.86 ▼0.36 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.01 ▼0.04 | 34.22 ▼3.47 | 33.42 ▼1.00 |
| Add New Post /wp-admin/post-new.php | 1,535 ▲21 | 23.30 ▲5.70 | 668.33 ▲11.76 | 53.79 ▼5.20 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.34 ▲0.09 | 93.54 ▼8.50 | 41.57 ▼1.01 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- Zombie WordPress options detected upon uninstall: 7 options
- widget_pure_widget
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% 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)
The smoke test was a success, however most plugin functionality was not tested
SRP 0% 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 take a closer look at the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/pure-feed-widget/tests/bootstrap.php
- 11× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Warning
require_once(PureWsRest.php): failed to open stream: No such file or directory in wp-content/plugins/pure-feed-widget/tests/test-purewsrest.php on line 3
- > PHP Fatal error
require_once(): Failed opening required 'PureWsRest.php' (include_path='.:/usr/share/php') in wp-content/plugins/pure-feed-widget/tests/test-publication.php on line 6
- > PHP Fatal error
Uncaught Error: Class 'WP_UnitTestCase' not found in wp-content/plugins/pure-feed-widget/tests/test-parsing-pure-wsrest-response.php:8
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/pure-feed-widget/class-pure-widget.php:15
- > PHP Fatal error
require_once(): Failed opening required 'PureWsRest.php' (include_path='.:/usr/share/php') in wp-content/plugins/pure-feed-widget/tests/test-purewsrest.php on line 3
- > PHP Fatal error
Uncaught Error: Class 'WP_UnitTestCase' not found in wp-content/plugins/pure-feed-widget/tests/test-widget.php:6
- > PHP Fatal error
Uncaught Error: Class 'WP_UnitTestCase' not found in wp-content/plugins/pure-feed-widget/tests/test-sample.php:11
- > PHP Warning
require_once(PureWsRestRendering.php): failed to open stream: No such file or directory in wp-content/plugins/pure-feed-widget/tests/test-purewsrestrendering.php on line 6
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/pure-feed-widget/class-pure-widget.php:15
- > PHP Fatal error
require_once(): Failed opening required 'PureWsRestRendering.php' (include_path='.:/usr/share/php') in wp-content/plugins/pure-feed-widget/tests/test-purewsrestrendering.php on line 6
- > PHP Warning
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 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
Please fix the following attributes:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Pure offers rendering items in various bibliographical style. Below is example output with the [APA style](https://apastyle.apa.org/) style, without any fancy CSS.), #2 (Example output with the *short* style)
pure-feed-widget/pure-feed-widget.php Passed 13 tests
"Pure Feed Widget" version 0.2.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
42 characters long description:
Render content from Elsevier Pure systems.
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
Everything looks great! No dangerous files found in this plugin11,748 lines of code in 21 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| XML | 5 | 5 | 12 | 11,017 |
| PHP | 12 | 93 | 206 | 491 |
| Bourne Shell | 1 | 21 | 11 | 123 |
| YAML | 1 | 7 | 0 | 60 |
| Markdown | 1 | 17 | 0 | 55 |
| Lisp | 1 | 1 | 1 | 2 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.16 |
| Average class complexity | 4.30 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 24.00 |
| Average method complexity | 1.87 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 15.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 1 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 10 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 10 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 39 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 37 | 94.87% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 2 | 5.13% |
| Functions | 3 | |
| ▷ Named functions | 1 | 33.33% |
| ▷ Anonymous functions | 2 | 66.67% |
| Constants | 3 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 3 | 100.00% |
| ▷ Public constants | 3 | 100.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
2 PNG files occupy 0.19MB with 0.13MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-2.png | 80.75KB | 26.21KB | ▼ 67.54% |
| assets/screenshot-1.png | 115.08KB | 42.29KB | ▼ 63.25% |