Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼9.24ms] Passed 4 tests
This is a short check of server-side resources used by Disable FLoC
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 40.60 ▼1.05 |
Dashboard /wp-admin | 3.33 ▼0.01 | 47.21 ▼13.48 |
Posts /wp-admin/edit.php | 3.45 ▲0.09 | 43.62 ▲0.21 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 80.57 ▼22.62 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 33.96 ▲2.46 |
Server storage [IO: ▲0.06MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 26 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Disable FLoC
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.24 ▼1.13 | 4.60 ▲2.71 | 44.62 ▲0.36 |
Dashboard /wp-admin | 2,206 ▲15 | 4.87 ▼0.99 | 110.34 ▲4.57 | 42.05 ▼3.25 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.01 | 38.52 ▲1.70 | 34.87 ▼0.68 |
Add New Post /wp-admin/post-new.php | 1,541 ▼1 | 23.13 ▲5.07 | 643.48 ▲42.57 | 54.79 ▼0.89 |
Media Library /wp-admin/upload.php | 1,391 ▲3 | 4.23 ▼0.08 | 96.69 ▼0.67 | 42.38 ▼0.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
- 6× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Interface 'WpMunich\\wpmfloc\\Component_Interface' not found in wp-content/plugins/wpm-floc/inc/Settings/Component.php:16
- > PHP Fatal error
Uncaught Error: Interface 'WpMunich\\wpmfloc\\Component_Interface' not found in wp-content/plugins/wpm-floc/inc/FLoCCheck/Component.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function add_cacheaction() in wp-content/plugins/wpm-floc/inc/WPSC/wpsc.php:16
- > PHP Fatal error
Uncaught Error: Interface 'WpMunich\\wpmfloc\\Component_Interface' not found in wp-content/plugins/wpm-floc/inc/WPSC/Component.php:14
- > PHP Fatal error
Uncaught Error: Interface 'WpMunich\\wpmfloc\\Component_Interface' not found in wp-content/plugins/wpm-floc/inc/FLoC/Component.php:16
- > PHP Fatal error
Uncaught Error: Interface 'WpMunich\\wpmfloc\\Component_Interface' not found in wp-content/plugins/wpm-floc/inc/i18n/Component.php:16
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 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
9 plugin tags: privacy, tracking, floc, google, cohorts...
wpm-floc/wpmfloc.php 92% from 13 tests
The principal PHP file in "Disable FLoC" v. 1.3.3 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("wpm-floc.php" instead of "wpmfloc.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
No dangerous file extensions were detected1,098 lines of code in 25 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 23 | 332 | 571 | 1,020 |
JavaScript | 2 | 6 | 39 | 78 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 9.69 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 47.00 |
Average method complexity | 2.49 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 8 | |
Interfaces | 2 | |
Traits | 0 | |
Classes | 11 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 11 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 80 | |
▷ Static methods | 15 | 18.75% |
▷ Public methods | 75 | 93.75% |
▷ Protected methods | 2 | 2.50% |
▷ Private methods | 3 | 3.75% |
Functions | 7 | |
▷ Named functions | 4 | 57.14% |
▷ Anonymous functions | 3 | 42.86% |
Constants | 4 | |
▷ Global constants | 4 | 100.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
No PNG files were detected