Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Install script ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼6.70ms] Passed 4 tests
Server-side resources used by Force Update Check for Plugins and Themes
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 41.81 ▲3.86 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 44.07 ▼15.06 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 47.46 ▲1.05 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.97 ▼8.92 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 32.15 ▼3.85 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Force Update Check for Plugins and Themes
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 14.40 ▼0.38 | 1.98 ▲0.30 | 39.15 ▼0.33 |
| Dashboard /wp-admin | 2,206 ▲15 | 4.85 ▼1.06 | 95.58 ▼5.78 | 37.32 ▼6.04 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.00 ▼0.16 | 40.63 ▲6.12 | 35.94 ▲1.54 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼5 | 17.64 ▼5.39 | 600.89 ▼84.28 | 48.83 ▼23.19 |
| Media Library /wp-admin/upload.php | 1,382 ▼9 | 4.14 ▼0.10 | 98.72 ▼0.90 | 42.65 ▼0.68 |
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
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
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
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/force-update-check-for-plugins-and-themes/ags-force-updates.php:42
- > 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 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Attributes that need to be fixed:
- Donate link: Please fix this invalid URI: ""
force-update-check-for-plugins-and-themes/ags-force-updates.php 85% from 13 tests
The main PHP file in "Force Update Check for Plugins and Themes" ver. 1.0.1 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("force-update-check-for-plugins-and-themes.php" instead of "ags-force-updates.php")
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected35 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 21 | 32 | 35 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 3.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 3 | |
| ▷ Static methods | 3 | 100.00% |
| ▷ Public methods | 3 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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 images were found in this plugin