Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.09MB] [CPU: ▼2.22ms] Passed 4 tests
An overview of server-side resources used by Briqpay Fortnox Product Sync
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.56 ▲0.09 | 47.41 ▲2.82 |
Dashboard /wp-admin | 3.39 ▲0.08 | 54.11 ▼3.58 |
Posts /wp-admin/edit.php | 3.51 ▲0.15 | 52.72 ▼2.04 |
Add New Post /wp-admin/post-new.php | 5.99 ▲0.10 | 91.09 ▼6.07 |
Media Library /wp-admin/upload.php | 3.32 ▲0.08 | 39.31 ▲5.71 |
Briqpay Fortnox Product Sync /wp-admin/tools.php?page=briqpay_fortnox_sync | 3.27 | 33.50 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 22 new files
Database: no new tables, 7 new options
New WordPress options |
---|
recovery_mode_email_last_sent |
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for Briqpay Fortnox Product Sync
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,891 ▲102 | 13.95 ▲0.79 | 5.46 ▲3.60 | 42.16 ▼3.45 |
Dashboard /wp-admin | 2,214 ▲5 | 4.82 ▼1.06 | 111.74 ▲10.50 | 40.92 ▼5.57 |
Posts /wp-admin/edit.php | 2,097 ▲5 | 2.01 ▼0.03 | 39.59 ▲3.28 | 35.47 ▲4.22 |
Add New Post /wp-admin/post-new.php | 1,524 ▲10 | 17.66 ▲0.20 | 654.79 ▲53.92 | 53.79 ▲8.67 |
Media Library /wp-admin/upload.php | 1,390 ▼1 | 4.21 ▲0.02 | 94.94 ▼8.16 | 41.20 ▼1.17 |
Briqpay Fortnox Product Sync /wp-admin/tools.php?page=briqpay_fortnox_sync | 683 | 1.53 | 6.83 | 17.18 |
Uninstaller [IO: ✅] [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
You still need to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- recovery_mode_email_last_sent
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/tools.php?page=briqpay_fortnox_sync
- > Error in wp-content/plugins/briqpay-fortnox-product-sync/admin/class-briqpay_fortnox_product_sync-admin.php+262
Uncaught Error: Class 'WC_Product_Query' not found in wp-content/plugins/briqpay-fortnox-product-sync/admin/class-briqpay_fortnox_product_sync-admin.php:262
Stack trace:
#0 wp-includes/class-wp-hook.php(310): Briqpay_fortnox_product_sync_Admin->render_fortnox_sync_page()
#1 wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#2 wp-includes/plugin.php(517): WP_Hook->do_action()
#3 wp-admin/admin.php(259): do_action()
#4 wp-admin/tools.php(40): require_once('/var/www/wordpr...')
#5 {main}
thrown
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
The following issues need your attention
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/briqpay-fortnox-product-sync/public/partials/briqpay_fortnox_product_sync-public-display.php
- > /wp-content/plugins/briqpay-fortnox-product-sync/admin/partials/briqpay_fortnox_product_sync-admin-display.php
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
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
8 plugin tags: fortnox, b2b, producs, business2business, briqpay...
briqpay-fortnox-product-sync/briqpay_fortnox_product_sync.php 85% from 13 tests
The entry point to "Briqpay Fortnox Product Sync" version 1.0.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Text Domain: The text domain should only use lowercase characters and dashes
- Main file name: Name the main plugin file the same as the plugin slug ("briqpay-fortnox-product-sync.php" instead of "briqpay_fortnox_product_sync.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected448 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 136 | 537 | 442 |
JavaScript | 2 | 4 | 54 | 6 |
CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 5.86 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 32.00 |
Average method complexity | 1.50 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 10.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 33 | |
▷ Static methods | 2 | 6.06% |
▷ Public methods | 28 | 84.85% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 15.15% |
Functions | 4 | |
▷ Named functions | 3 | 75.00% |
▷ Anonymous functions | 1 | 25.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin