Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.14MB] [CPU: ▼6.73ms] Passed 4 tests
Server-side resources used by Sortter Rahoituslaskuri
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.60 ▲0.14 | 36.10 ▼1.34 |
Dashboard /wp-admin | 3.44 ▲0.14 | 47.11 ▼0.44 |
Posts /wp-admin/edit.php | 3.56 ▲0.20 | 48.36 ▼2.61 |
Add New Post /wp-admin/post-new.php | 6.04 ▲0.16 | 80.98 ▼22.54 |
Media Library /wp-admin/upload.php | 3.37 ▲0.14 | 37.00 ▲1.16 |
Sortter Rahoituslaskuri /wp-admin/admin.php?page=sortter-laskuri | 3.34 | 31.34 |
Settings /wp-admin/admin.php?page=sortter-laskuri-settings | 3.33 | 32.20 |
Server storage [IO: ▲1.10MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 50 new files
Database: no new tables, 10 new options
New WordPress options |
---|
can_compress_scripts |
sortter-laskuri_seller_code |
widget_theysaidso_widget |
widget_recent-comments |
sortter-laskuri_default_sum |
sortter-laskuri_page_id |
widget_recent-posts |
theysaidso_admin_options |
sortter-laskuri_default_time |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Sortter Rahoituslaskuri
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,961 ▲226 | 14.42 ▲0.04 | 16.30 ▲14.58 | 36.96 ▼4.23 |
Dashboard /wp-admin | 2,233 ▲42 | 5.02 ▲0.11 | 114.03 ▲3.96 | 42.56 ▲1.10 |
Posts /wp-admin/edit.php | 2,116 ▲27 | 2.02 ▼0.02 | 42.05 ▲0.18 | 35.58 ▲0.96 |
Add New Post /wp-admin/post-new.php | 1,537 ▼3 | 17.71 ▼0.72 | 665.71 ▲51.00 | 49.36 ▼8.41 |
Media Library /wp-admin/upload.php | 1,409 ▲27 | 4.24 ▲0.04 | 95.34 ▼7.51 | 41.22 ▼2.30 |
Sortter Rahoituslaskuri /wp-admin/admin.php?page=sortter-laskuri | 884 | 2.18 | 24.20 | 37.40 |
Settings /wp-admin/admin.php?page=sortter-laskuri-settings | 838 | 2.04 | 25.81 | 26.28 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
Smoke tests 50% 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 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
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/sortter-rahoituslaskuri/public/partials/sortter-laskuri-public-display.php
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/sortter-rahoituslaskuri/public/partials/sortter-laskuri-public-form-display.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/sortter-rahoituslaskuri/admin/partials/sortter-laskuri-admin-settings-display.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/sortter-rahoituslaskuri/admin/partials/sortter-laskuri-admin-display.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
4 plugin tags: rahoitus, loan, sortter, financing
sortter-rahoituslaskuri/sortter-laskuri.php 85% from 13 tests
The main PHP script in "Sortter Rahoituslaskuri" version 1.1.0 is automatically included on every request by WordPress
You should first fix the following items:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 182 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("sortter-rahoituslaskuri.php" instead of "sortter-laskuri.php")
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
No dangerous file extensions were detected1,873 lines of code in 28 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 16 | 154 | 684 | 630 |
PO File | 5 | 143 | 170 | 523 |
CSS | 3 | 12 | 14 | 521 |
JavaScript | 2 | 12 | 50 | 124 |
Markdown | 1 | 19 | 0 | 59 |
HTML | 1 | 8 | 0 | 16 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.20 |
Average class complexity | 5.78 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 22.00 |
Average method complexity | 2.16 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 19.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 9 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 9 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 37 | |
▷ Static methods | 4 | 10.81% |
▷ Public methods | 31 | 83.78% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 6 | 16.22% |
Functions | 4 | |
▷ Named functions | 4 | 100.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 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.91MB with 0.63MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-4.png | 68.24KB | 20.44KB | ▼ 70.04% |
assets/screenshot-3.png | 352.84KB | 101.48KB | ▼ 71.24% |
assets/screenshot-2.png | 190.01KB | 53.85KB | ▼ 71.66% |
assets/screenshot-1.png | 316.11KB | 102.77KB | ▼ 67.49% |