Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.14MB] [CPU: ▼8.17ms] Passed 4 tests
This is a short check of server-side resources used by Keyring Reactions Importer
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.80 ▲0.34 | 44.00 ▲0.51 |
Dashboard /wp-admin | 3.50 ▲0.20 | 36.16 ▼12.18 |
Posts /wp-admin/edit.php | 3.57 ▲0.21 | 40.42 ▼5.69 |
Add New Post /wp-admin/post-new.php | 5.74 ▼0.14 | 71.07 ▼13.76 |
Media Library /wp-admin/upload.php | 3.51 ▲0.28 | 32.58 ▼1.04 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for Keyring Reactions Importer
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,910 ▲139 | 13.54 ▼0.86 | 9.28 ▲7.12 | 43.21 ▲1.33 |
Dashboard /wp-admin | 2,204 ▲13 | 4.83 ▼0.03 | 101.25 ▼3.68 | 39.73 ▼0.87 |
Posts /wp-admin/edit.php | 2,097 ▲5 | 2.06 ▲0.00 | 36.39 ▼6.15 | 31.11 ▼6.57 |
Add New Post /wp-admin/post-new.php | 1,535 ▲7 | 23.03 ▲4.60 | 663.06 ▲15.55 | 58.04 ▼2.05 |
Media Library /wp-admin/upload.php | 1,396 ▲8 | 4.23 ▲0.06 | 108.20 ▲10.84 | 47.58 ▲6.60 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% 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 take a closer look at the following
- 7× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/import.php' (include_path='.:/usr/share/php') in wp-content/plugins/keyring-reactions-importer/keyring-reactions-importer.php on line 45
- > PHP Warning
require_once(ABSPATHwp-admin/includes/import.php): failed to open stream: No such file or directory in wp-content/plugins/keyring-reactions-importer/keyring-reactions-importer.php on line 45
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/keyring-reactions-importer/importers/keyring-reactions-flickr.php:217
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/keyring-reactions-importer/importers/keyring-reactions-500px.php:219
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/keyring-reactions-importer/importers/keyring-reactions-facebook.php:209
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/keyring-reactions-importer/keyring-reactions-importer.php on line 45
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/keyring-reactions-importer/importers/keyring-reactions-instagram.php:161
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
9 plugin tags: favorites, facebook, backfeed, likes, flickr...
keyring-reactions-importer/keyring-reactions-importer.php Passed 13 tests
The main file in "Keyring Reactions Importer" v. 1.1 serves as a complement to information provided in readme.txt and as the entry point to the plugin
61 characters long description:
A recations (comments, favs, etc. ) importer based on Keyring
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
Everything looks great! No dangerous files found in this plugin1,383 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 368 | 382 | 1,383 |
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.38 |
Average class complexity | 47.20 |
▷ Minimum class complexity | 22.00 |
▷ Maximum class complexity | 127.00 |
Average method complexity | 5.28 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 5 | |
▷ Abstract classes | 1 | 20.00% |
▷ Concrete classes | 4 | 80.00% |
▷ Final classes | 0 | 0.00% |
Methods | 55 | |
▷ Static methods | 2 | 3.64% |
▷ Public methods | 43 | 78.18% |
▷ Protected methods | 12 | 21.82% |
▷ Private methods | 0 | 0.00% |
Functions | 9 | |
▷ Named functions | 5 | 55.56% |
▷ Anonymous functions | 4 | 44.44% |
Constants | 46 | |
▷ Global constants | 3 | 6.52% |
▷ Class constants | 43 | 93.48% |
▷ Public constants | 43 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin