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
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼1.97MB] [CPU: ▼51.58ms] Passed 4 tests
Analyzing server-side resources used by extLnk
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.03 ▼1.43 | 7.29 ▼31.05 |
Dashboard /wp-admin | 2.05 ▼1.30 | 6.37 ▼54.07 |
Posts /wp-admin/edit.php | 2.05 ▼1.31 | 6.90 ▼40.95 |
Add New Post /wp-admin/post-new.php | 2.05 ▼3.84 | 6.31 ▼80.25 |
Media Library /wp-admin/upload.php | 2.05 ▼1.18 | 6.24 ▼25.89 |
Server storage [IO: ▲0.41MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 53 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for extLnk
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,802 ▲52 | 14.35 ▼0.25 | 1.57 ▼0.20 | 36.35 ▼13.28 |
Dashboard /wp-admin | 2,195 ▲18 | 5.51 ▼0.14 | 81.79 ▼11.09 | 38.49 ▲0.54 |
Posts /wp-admin/edit.php | 2,103 ▲3 | 1.98 ▼0.04 | 34.26 ▼0.96 | 30.12 ▼4.57 |
Add New Post /wp-admin/post-new.php | 1,538 ▲12 | 23.23 ▼0.22 | 666.06 ▼1.76 | 57.11 ▲2.94 |
Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.15 ▼0.13 | 95.99 ▼1.57 | 40.95 ▼0.95 |
extLnk /wp-admin/extlnk.php | 26 | 0.42 | 0.18 | 12.25 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
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 take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_bloginfo() in wp-content/plugins/extlnk/extlnk.php:77
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please fix the following browser errors
- > GET request to /wp-admin/extlnk.php
- > Network (severe)
wp-admin/extlnk.php - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
These attributes need to be fixed:
- Tags: You are using too many tags: 40 tag instead of maximum 10
extlnk/extlnk.php 92% from 13 tests
Analyzing the main PHP file in "extLnk" version 1.3
Please take the time to fix the following:
- Description: Please keep the plugin description shorter than 140 characters (currently 150 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected3,466 lines of code in 17 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 324 | 349 | 1,601 |
PO File | 2 | 272 | 582 | 1,075 |
JavaScript | 4 | 89 | 38 | 454 |
Markdown | 3 | 102 | 0 | 175 |
JSON | 4 | 0 | 0 | 114 |
HTML | 2 | 0 | 0 | 37 |
YAML | 1 | 0 | 0 | 10 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 211.00 |
▷ Minimum class complexity | 211.00 |
▷ Maximum class complexity | 211.00 |
Average method complexity | 5.57 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 47.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 | 46 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 46 | 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 | 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
PNG files should be compressed to save space and minimize bandwidth usage
28 PNG files occupy 0.08MB with 0.06MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/select-arrow.png | 1.16KB | 0.32KB | ▼ 72.19% |
images/screenshot.png | 14.23KB | 7.77KB | ▼ 45.39% |
images/wordpress.png | 3.16KB | 0.51KB | ▼ 83.98% |
icons/standard.png | 0.97KB | 0.13KB | ▼ 86.81% |
images/close.png | 2.95KB | 0.31KB | ▼ 89.32% |