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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼7.53ms] Passed 4 tests
Analyzing server-side resources used by Yasham Live Feed
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 36.09 ▼3.80 |
Dashboard /wp-admin | 3.32 ▲0.02 | 53.03 ▼3.01 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 50.27 ▼1.64 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 88.18 ▼21.43 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.90 ▼1.89 |
Add Feed /wp-admin/admin.php?page=add_feed | 3.19 | 30.58 |
Settings /wp-admin/admin.php?page=settings_feed | 3.19 | 34.48 |
Server storage [IO: ▲3.29MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 31 new files
Database: no new tables, 7 new options
New WordPress options |
---|
yslf_yasham_livefeed_settings |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Yasham Live Feed: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,993 ▲247 | 14.96 ▲0.58 | 23.56 ▲21.80 | 41.80 ▼3.70 |
Dashboard /wp-admin | 2,247 ▲50 | 5.90 ▲1.00 | 101.53 ▼3.89 | 38.47 ▼3.87 |
Posts /wp-admin/edit.php | 2,123 ▲23 | 2.00 ▼0.04 | 37.06 ▲1.09 | 33.22 ▼3.48 |
Add New Post /wp-admin/post-new.php | 1,564 ▲19 | 23.30 ▼0.08 | 601.67 ▼107.10 | 66.47 ▲3.54 |
Media Library /wp-admin/upload.php | 1,426 ▲26 | 4.21 ▼0.02 | 108.11 ▼3.54 | 44.88 ▼3.44 |
Add Feed /wp-admin/admin.php?page=add_feed | 1,381 | 7.32 | 145.21 | 55.97 |
Settings /wp-admin/admin.php?page=settings_feed | 873 | 2.16 | 26.30 | 31.73 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 7 options
- widget_recent-comments
- db_upgraded
- yslf_yasham_livefeed_settings
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Please fix the following server-side errors
- 10 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=settings_feed
- > Notice in wp-content/plugins/yasham-live-feed/includes/feedsettings.php+84
Trying to access array offset on value of type bool
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
Almost there! Just fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/yasham-live-feed/yasham-livefeed.php:11
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please fix the following browser errors
- > GET request to /wp-admin/admin.php?page=add_feed
- > Console-api (severe) in unknown
https://www.gstatic.com/firebasejs/7.8.2/firebase-database.js?ver=7 0:11374 "[2023-10-13T21:36:54.037Z] @firebase/database:" "FIREBASE FATAL ERROR: Cannot parse Firebase url. Please use https://\u003CYOUR FIREBASE>.firebaseio.com "
- > GET request to /wp-admin/admin.php?page=add_feed
- > Javascript (severe) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1 1:28721 Uncaught Error: FIREBASE FATAL ERROR: Cannot parse Firebase url. Please use https://.firebaseio.com
- > GET request to /wp-admin/admin.php?page=settings_feed
- > Console-api (warning) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1 1:28609 "jQuery.Deferred exception: $(...).wpColorPicker is not a function" "TypeError: $(...).wpColorPicker is not a function\n at HTMLDocument.\u003Canonymous> (/wp-admin/admin.php?page=settings_feed:154:30)\n at e (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1:2:26990)\n at t (/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1:2:27292)" undefined
- > GET request to /wp-admin/admin.php?page=settings_feed
- > Javascript (severe) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1 1:28721 Uncaught TypeError: $(...).wpColorPicker is not a function
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that require attention:
- Tags: There are too many tags (12 tag instead of maximum 10)
yasham-live-feed/yasham-livefeed.php 92% from 13 tests
The entry point to "Yasham Live Feed" version 1.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("yasham-live-feed.php" instead of "yasham-livefeed.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Success! There were no dangerous files found in this plugin531 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 40 | 21 | 256 |
JavaScript | 2 | 13 | 22 | 111 |
CSS | 2 | 2 | 0 | 77 |
PO File | 1 | 23 | 23 | 65 |
SVG | 1 | 0 | 0 | 22 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.07 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 11 | |
▷ Named functions | 10 | 90.91% |
▷ Anonymous functions | 1 | 9.09% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
12 PNG files occupy 3.17MB with 2.11MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screens/11.png | 76.71KB | 30.53KB | ▼ 60.19% |
screens/5.png | 441.63KB | 109.71KB | ▼ 75.16% |
screens/9.png | 168.88KB | 53.30KB | ▼ 68.44% |
screens/8.png | 123.76KB | 41.03KB | ▼ 66.85% |
screens/2.png | 351.08KB | 130.59KB | ▼ 62.80% |