Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼189.47ms] Passed 4 tests
An overview of server-side resources used by Fantastic Content Protector Free
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.88 ▲0.04 | 24.49 ▲3.33 |
| Dashboard /wp-admin | 3.11 ▲0.04 | 37.09 ▲1.60 |
| Posts /wp-admin/edit.php | 3.16 ▲0.05 | 31.16 ▼2.24 |
| Add New Post /wp-admin/post-new.php | 5.47 ▲0.03 | 72.04 ▼756.49 |
| Media Library /wp-admin/upload.php | 3.05 ▲0.04 | 22.64 ▼0.74 |
| Fantastic Content Protector Free /wp-admin/options-general.php?page=content_protector_free | 3.02 | 23.50 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 5 new options
| New WordPress options |
|---|
| credit_text_new |
| credits_nofollow_new |
| credits_name_new |
| credit_link_content_protect |
| credits_defaults_new |
Browser metrics Passed 4 tests
Fantastic Content Protector Free: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,677 ▲76 | 15.57 ▼0.06 | 4.85 ▲0.04 | 75.36 ▼1.49 |
| Dashboard /wp-admin | 2,935 ▲39 | 6.12 ▼0.06 | 114.28 ▼19.30 | 164.58 ▼15.78 |
| Posts /wp-admin/edit.php | 2,748 ▲8 | 3.22 ▼0.01 | 61.82 ▼3.82 | 137.17 ▼12.51 |
| Add New Post /wp-admin/post-new.php | 3,810 ▲67 | 18.58 ▼0.78 | 433.17 ▲4.40 | 158.84 ▼0.81 |
| Media Library /wp-admin/upload.php | 1,757 ▲5 | 5.49 ▼0.07 | 158.64 ▲18.22 | 196.28 ▲7.39 |
| Fantastic Content Protector Free /wp-admin/options-general.php?page=content_protector_free | 1,207 | 2.43 | 56.45 | 121.00 |
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
The following items require your attention
- The uninstall procedure has failed, leaving 5 options in the database
- credit_link_content_protect
- credit_text_new
- credits_defaults_new
- credits_nofollow_new
- credits_name_new
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
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/fantastic-content-protector-free/fantasticcontentprotectorfree.php:157
- > 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 90% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need your attention:
- Plugin Name: You should set the name of your plugin on the first line (
=== fantastic-content-protector-free ===)
fantastic-content-protector-free/fantasticcontentprotectorfree.php 85% from 13 tests
"Fantastic Content Protector Free" version 2.6's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("fantastic-content-protector-free.php" instead of "fantasticcontentprotectorfree.php")
- Description: Please don't use more than 140 characters for the plugin description (currently 252 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected447 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 33 | 16 | 271 |
| CSS | 1 | 32 | 0 | 176 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 10.00 |
| ▷ Minimum class complexity | 10.00 |
| ▷ Maximum class complexity | 10.00 |
| Average method complexity | 2.80 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.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 | 5 | |
| ▷ Static methods | 4 | 80.00% |
| ▷ Public methods | 5 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.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
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/favicon.png | 19.01KB | 6.16KB | ▼ 67.58% |