Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼7.44ms] Passed 4 tests
Server-side resources used by Veracity Bot Detection Tag for WordPress
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.01 | 38.07 ▼0.12 |
Dashboard /wp-admin | 3.32 ▼0.02 | 46.55 ▼14.05 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 51.77 ▼0.75 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 81.71 ▼11.70 |
Media Library /wp-admin/upload.php | 3.25 ▲0.01 | 33.53 ▼3.27 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
can_compress_scripts |
widget_theysaidso_widget |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Veracity Bot Detection Tag for WordPress
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,806 ▲44 | 14.22 ▼0.43 | 2.21 ▲0.52 | 37.61 ▲0.85 |
Dashboard /wp-admin | 2,211 ▲33 | 5.62 ▼0.09 | 92.30 ▼21.20 | 38.38 ▼8.45 |
Posts /wp-admin/edit.php | 2,119 ▲19 | 2.02 ▲0.07 | 39.51 ▲1.14 | 36.49 ▼1.29 |
Add New Post /wp-admin/post-new.php | 1,539 ▲13 | 23.62 ▲0.28 | 619.56 ▼17.42 | 46.12 ▼3.59 |
Media Library /wp-admin/upload.php | 1,416 ▲13 | 4.23 ▲0.05 | 98.57 ▼8.03 | 42.12 ▼2.21 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests 50% 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 0% 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
Almost there! Just fix the following items
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/beacon-web-analytics/Beacon_Tracking_WP.php
- > /wp-content/plugins/beacon-web-analytics/admin/index.php
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/beacon-web-analytics/views/admin.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
9 plugin tags: wp, tracking, cyber security, analytics, monitoring...
beacon-web-analytics/Beacon_Tracking_WP.php 85% from 13 tests
"Veracity Bot Detection Tag for WordPress" version 3.0.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("beacon-web-analytics.php" instead of "Beacon_Tracking_WP.php")
- Description: Please keep the plugin description shorter than 140 characters (currently 156 characters long)
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
There were no executable files found in this plugin63 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 17 | 23 | 63 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
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 | 7 | |
▷ Named functions | 6 | 85.71% |
▷ Anonymous functions | 1 | 14.29% |
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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
No PNG files were detected