Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
This plugin's installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼4.21ms] Passed 4 tests
An overview of server-side resources used by FikraTicker
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 40.30 ▲1.85 |
| Dashboard /wp-admin | 3.34 ▼0.01 | 52.68 ▼14.45 |
| Posts /wp-admin/edit.php | 3.39 ▲0.03 | 50.20 ▼1.63 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 96.84 ▲2.08 |
| Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 37.63 ▼2.59 |
| FikraTicker /wp-admin/options-general.php?page=fikraticker/news.php | 3.23 | 37.59 |
Server storage [IO: ▲0.08MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_theysaidso_widget |
| widget_recent-comments |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for FikraTicker
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,925 ▲179 | 14.04 ▼0.24 | 5.65 ▲3.89 | 45.27 ▲2.15 |
| Dashboard /wp-admin | 2,225 ▲25 | 5.91 ▼0.10 | 108.20 ▲5.22 | 40.27 ▼5.57 |
| Posts /wp-admin/edit.php | 2,104 ▲4 | 2.00 ▼0.02 | 37.41 ▼4.35 | 33.33 ▼3.83 |
| Add New Post /wp-admin/post-new.php | 1,553 ▲8 | 23.06 ▼0.17 | 656.02 ▼43.14 | 55.20 ▼8.00 |
| Media Library /wp-admin/upload.php | 1,404 ▲7 | 4.21 ▲0.02 | 106.81 ▼35.97 | 45.57 ▼11.60 |
| FikraTicker /wp-admin/options-general.php?page=fikraticker/news.php | 974 | 2.23 | 23.82 | 26.68 |
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
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/fikraticker/news.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/fikraticker/index.php:3
- > 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)
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Screenshots: These screenshots require images: #1 (fikraticker), #2 (Admin Panel)
fikraticker/news.php 92% from 13 tests
The principal PHP file in "FikraTicker" v. 0.2 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("fikraticker.php" instead of "news.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
Everything looks great! No dangerous files found in this plugin735 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 3 | 77 | 231 | 372 |
| PHP | 3 | 24 | 24 | 363 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| 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 | 5 | |
| ▷ Named functions | 5 | 100.00% |
| ▷ Anonymous functions | 0 | 0.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
PNG files should be compressed to save space and minimize bandwidth usage
2 PNG files occupy 0.04MB with 0.02MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 5.61KB | 3.34KB | ▼ 40.53% |
| screenshot-2.png | 37.29KB | 12.15KB | ▼ 67.42% |