Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Please fix the following installer errors
- The plugin did not install without errors
- > Deprecated in wp-content/plugins/adluge-visitor-tracking/AdLugeVT.php+24
Methods with the same name as their class will not be constructors in a future version of PHP; AdLugeVT has a deprecated constructor
Server metrics [RAM: ▼2.47MB] [CPU: ▼338.86ms] Passed 4 tests
An overview of server-side resources used by AdLuge Visitor Tracker
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.55 ▲0.04 | 52.98 ▲2.46 |
Dashboard /wp-admin | 1.85 ▼1.55 | 3.84 ▼31.38 |
Posts /wp-admin/edit.php | 1.86 ▼1.78 | 3.94 ▼34.64 |
Add New Post /wp-admin/post-new.php | 1.85 ▼5.11 | 3.85 ▼1,262.61 |
Media Library /wp-admin/upload.php | 1.86 ▼1.44 | 3.53 ▼26.80 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 10 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by AdLuge Visitor Tracker
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,923 ▲201 | 16.03 ▲0.36 | 5.60 ▼0.08 | 2.09 ▼0.27 |
Dashboard /wp-admin | 3,020 ▲159 | 7.28 ▲1.13 | 127.10 ▼3.78 | 164.41 ▲6.61 |
Posts /wp-admin/edit.php | 2,817 ▲130 | 3.41 ▲0.16 | 67.76 ▲2.88 | 132.39 ▼3.45 |
Add New Post /wp-admin/post-new.php | 1,779 ▲27 | 16.32 ▼5.01 | 398.52 ▼48.67 | 213.02 ▲56.99 |
Media Library /wp-admin/upload.php | 1,821 ▲126 | 6.03 ▲0.49 | 138.51 ▼11.10 | 205.83 ▲14.17 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Uninstall procedure validation failed for this plugin
- > User notice in wp-includes/functions.php+5768
wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the AdLugeVTStyleSheet1 handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
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 | 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
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/adluge-visitor-tracking/AdLugeVT-sidebar.php
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/adluge-visitor-tracking/AdLugeVT.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Please fix the following attributes:
- Tags: Please delete some tags, you are using 12 tag instead of maximum 10
adluge-visitor-tracking/AdLugeVT.php 92% from 13 tests
This is the main PHP file of "AdLuge Visitor Tracker" version 1.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("adluge-visitor-tracking.php" instead of "AdLugeVT.php")
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
Good job! No executable or dangerous file extensions detected817 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 2 | 83 | 17 | 453 |
PHP | 2 | 58 | 8 | 194 |
CSS | 2 | 28 | 1 | 170 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.28 |
Average class complexity | 14.00 |
▷ Minimum class complexity | 14.00 |
▷ Maximum class complexity | 14.00 |
Average method complexity | 2.30 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.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 | 10 | |
▷ Static methods | 3 | 30.00% |
▷ Public methods | 10 | 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 | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/logo-wp-admin.png | 12.07KB | 5.03KB | ▼ 58.32% |
img/switch.png | 3.01KB | 0.64KB | ▼ 78.70% |