Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼2.46ms] Passed 4 tests
Analyzing server-side resources used by FaniMani.pl
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.54 ▲0.07 | 40.39 ▲2.78 |
Dashboard /wp-admin | 3.38 ▲0.08 | 47.57 ▼1.40 |
Posts /wp-admin/edit.php | 3.44 ▲0.07 | 44.42 ▼1.57 |
Add New Post /wp-admin/post-new.php | 5.98 ▲0.09 | 83.34 ▼9.63 |
Media Library /wp-admin/upload.php | 3.31 ▲0.07 | 35.20 ▲3.87 |
FaniMani.pl /wp-admin/options-general.php?page=fanimani-settings | 3.28 | 31.00 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
FaniMani.pl: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,816 ▲29 | 14.33 ▲0.01 | 1.69 ▼0.10 | 43.86 ▲2.92 |
Dashboard /wp-admin | 2,221 ▲44 | 5.84 ▲0.26 | 85.94 ▼7.64 | 38.16 ▼6.81 |
Posts /wp-admin/edit.php | 2,125 ▲25 | 2.30 ▲0.32 | 35.15 ▼4.23 | 34.92 ▲0.34 |
Add New Post /wp-admin/post-new.php | 1,543 ▲17 | 23.17 ▼0.07 | 626.47 ▼58.44 | 34.25 ▼22.00 |
Media Library /wp-admin/upload.php | 1,426 ▲26 | 4.45 ▲0.25 | 100.42 ▼0.14 | 43.28 ▲1.25 |
FaniMani.pl /wp-admin/options-general.php?page=fanimani-settings | 850 | 1.95 | 29.81 | 24.02 |
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
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 50% 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× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_next_scheduled() in wp-content/plugins/fanimani-pl/fanimani.php:17
- > PHP Fatal error
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 93% from 29 tests
readme.txt Passed 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
6 plugin tags: fundraising, fanipay, faniseo, widget, ngo...
fanimani-pl/fanimani.php 85% from 13 tests
"FaniMani.pl" version 1.1.14's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: The principal plugin file should be the same as the plugin slug ("fanimani-pl.php" instead of "fanimani.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
Everything looks great! No dangerous files found in this plugin534 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 57 | 18 | 382 |
PO File | 1 | 32 | 35 | 131 |
JavaScript | 1 | 2 | 0 | 21 |
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.36 |
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 | 14 | |
▷ Named functions | 14 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected