Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.83MB] [CPU: ▲9.02ms] Passed 4 tests
This is a short check of server-side resources used by Website File Changes Monitor
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.25 ▲0.79 | 50.84 ▲9.77 |
| Dashboard /wp-admin | 4.15 ▲0.81 | 69.24 ▲7.22 |
| Posts /wp-admin/edit.php | 4.27 ▲0.91 | 66.14 ▲13.00 |
| Add New Post /wp-admin/post-new.php | 6.77 ▲0.89 | 109.26 ▲6.08 |
| Media Library /wp-admin/upload.php | 4.07 ▲0.85 | 55.32 ▲22.61 |
| Help & Contact Us /wp-admin/admin.php?page=wfcm-about | 4.14 | 44.16 |
| Settings /wp-admin/admin.php?page=wfcm-settings | 4.40 | 51.18 |
| Files Monitor /wp-admin/admin.php?page=wfcm-file-changes | 4.26 | 50.81 |
Server storage [IO: ▲1.19MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 101 new files
Database: 1 new table, 8 new options
| New tables |
|---|
| wp_wfcm_file_events |
| New WordPress options |
|---|
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_theysaidso_widget |
| wfcm_plugin_version |
| wfcm_version |
Browser metrics Passed 4 tests
Website File Changes Monitor: an overview of browser usage
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,843 ▲81 | 14.06 ▼0.65 | 1.57 ▼0.26 | 38.29 ▼8.72 |
| Dashboard /wp-admin | 2,251 ▲74 | 5.67 ▲0.05 | 127.61 ▲29.24 | 83.95 ▲41.22 |
| Posts /wp-admin/edit.php | 2,159 ▲59 | 1.97 ▼0.05 | 39.86 ▲3.77 | 33.24 ▼1.53 |
| Add New Post /wp-admin/post-new.php | 1,571 ▲45 | 23.61 ▲0.52 | 689.12 ▼13.31 | 60.22 ▲8.72 |
| Media Library /wp-admin/upload.php | 1,453 ▲56 | 4.11 ▼0.04 | 103.03 ▲5.91 | 64.62 ▲24.47 |
| Help & Contact Us /wp-admin/admin.php?page=wfcm-about | 930 | 2.00 | 25.63 | 44.58 |
| Settings /wp-admin/admin.php?page=wfcm-settings | 2,335 | 1.86 | 26.99 | 34.89 |
| Files Monitor /wp-admin/admin.php?page=wfcm-file-changes | 1,066 | 3.25 | 61.38 | 45.90 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- This plugin does not fully uninstall, leaving 1 table in the database
- wp_wfcm_file_events
- Zombie WordPress options detected upon uninstall: 8 options
- widget_recent-posts
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- theysaidso_admin_options
- wfcm_version
- wfcm_plugin_version
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
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
- 10× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Class 'WFCM_AbstractUpdateWrapper' not found in wp-content/plugins/website-file-changes-monitor/includes/class-wfcm-update-runner.php:17
- > PHP Fatal error
Uncaught Error: Class 'WP_Background_Process' not found in wp-content/plugins/website-file-changes-monitor/includes/bg/class-wfcm-background-event-deletion.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/website-file-changes-monitor/includes/wsal-events/alerts/custom-alerts.php:4
- > PHP Fatal error
Uncaught Error: Interface 'WFCM_UpdateWrapperInterface' not found in wp-content/plugins/website-file-changes-monitor/includes/update/abstract-update-wrapper.php:16
- > PHP Fatal error
Uncaught Error: Class 'WP_Background_Process' not found in wp-content/plugins/website-file-changes-monitor/includes/bg/class-wfcm-background-check-changes.php:8
- > PHP Fatal error
Uncaught Error: Class 'WFCM_AbstractUpdateWrapper' not found in wp-content/plugins/website-file-changes-monitor/includes/update/class-wfcm-create-file-events-table.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/website-file-changes-monitor/vendor/deliciousbrains/wp-background-processing/wp-background-processing.php:20
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/website-file-changes-monitor/includes/wsal-events/sensor-functions.php:6
- > PHP Fatal error
Uncaught Error: Class 'WP_Background_Process' not found in wp-content/plugins/website-file-changes-monitor/includes/bg/class-wfcm-background-scanner.php:9
- > PHP Fatal error
Uncaught Error: Class 'WP_Async_Request' not found in wp-content/plugins/website-file-changes-monitor/vendor/deliciousbrains/wp-background-processing/classes/wp-background-process.php:14
- > 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)
Everything seems fine on the user side
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
8 plugin tags: file scanner, file changes scanner, file monitor, file changes, file integrity scanner...
website-file-changes-monitor/website-file-changes-monitor.php Passed 13 tests
This is the main PHP file of "Website File Changes Monitor" version 1.9.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
89 characters long description:
A hassle-free way to get alerted of file changes on your WordPress site & boost security.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Everything looks great! No dangerous files found in this plugin7,411 lines of code in 84 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 64 | 1,690 | 4,278 | 6,944 |
| JavaScript | 6 | 0 | 42 | 264 |
| Markdown | 1 | 60 | 0 | 112 |
| JSON | 2 | 0 | 0 | 73 |
| SVG | 6 | 0 | 0 | 13 |
| CSS | 5 | 2 | 8 | 5 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| Average class complexity | 20.91 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 275.00 |
| Average method complexity | 3.34 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 54.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 4 | |
| Interfaces | 2 | |
| Traits | 0 | |
| Classes | 43 | |
| ▷ Abstract classes | 4 | 9.30% |
| ▷ Concrete classes | 39 | 90.70% |
| ▷ Final classes | 1 | 2.56% |
| Methods | 385 | |
| ▷ Static methods | 87 | 22.60% |
| ▷ Public methods | 312 | 81.04% |
| ▷ Protected methods | 29 | 7.53% |
| ▷ Private methods | 44 | 11.43% |
| Functions | 69 | |
| ▷ Named functions | 46 | 66.67% |
| ▷ Anonymous functions | 23 | 33.33% |
| Constants | 25 | |
| ▷ Global constants | 15 | 60.00% |
| ▷ Class constants | 10 | 40.00% |
| ▷ Public constants | 10 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
PNG images were not found in this plugin