Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼9.46ms] Passed 4 tests
Server-side resources used by WPF Force External Nofollow
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.01 | 38.41 ▼1.68 |
| Dashboard /wp-admin | 3.32 ▼0.03 | 46.56 ▼14.68 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 48.75 ▼1.83 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 84.65 ▼19.66 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 38.87 ▲1.05 |
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: 3 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-comments |
Browser metrics Passed 4 tests
WPF Force External Nofollow: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.24 ▼1.17 | 1.73 ▲0.15 | 44.25 ▲7.38 |
| Dashboard /wp-admin | 2,206 ▲17 | 6.01 ▲1.03 | 92.94 ▼14.26 | 38.56 ▼3.19 |
| Posts /wp-admin/edit.php | 2,092 ▼0 | 2.01 ▲0.00 | 39.40 ▼2.47 | 33.88 ▼1.14 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼9 | 22.96 ▲4.45 | 672.87 ▲45.73 | 52.13 ▼0.13 |
| Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.18 ▼0.01 | 102.40 ▲4.34 | 44.21 ▲0.97 |
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
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-posts
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Good news, no errors were detected
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 fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/wpf-force-external-nofollow/force-external-nofollow.php:12
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% 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:
- Screenshots: Please add an image for screenshot #1 (Example of how the `rel="nofollow"` tag is inserted into all the external links.)
wpf-force-external-nofollow/force-external-nofollow.php 92% from 13 tests
The primary PHP file in "WPF Force External Nofollow" version 1.3 is used by WordPress to initiate all plugin functionality
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 ("wpf-force-external-nofollow.php" instead of "force-external-nofollow.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected40 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 7 | 9 | 40 |
PHP code Passed 2 tests
This is a short overview 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.55 |
| 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 | 1 | |
| ▷ Named functions | 1 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 4.90KB | 4.08KB | ▼ 16.82% |