Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼5.30ms] Passed 4 tests
A check of server-side resources used by Vejret Widget
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 45.50 ▲1.62 |
Dashboard /wp-admin | 3.32 ▲0.02 | 46.95 ▲1.50 |
Posts /wp-admin/edit.php | 3.37 ▲0.02 | 42.47 ▼4.02 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 82.87 ▼20.28 |
Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 33.18 ▲1.59 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 22 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_vejret_widget |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
Browser metrics Passed 4 tests
A check of browser resources used by Vejret Widget
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,887 ▲141 | 13.56 ▼1.03 | 5.52 ▲3.76 | 44.10 ▼0.20 |
Dashboard /wp-admin | 2,207 ▲28 | 5.80 ▼0.05 | 97.16 ▼7.30 | 37.29 ▼3.88 |
Posts /wp-admin/edit.php | 2,090 ▲4 | 2.02 ▲0.03 | 35.68 ▼0.28 | 29.42 ▼4.50 |
Add New Post /wp-admin/post-new.php | 1,518 ▼12 | 22.88 ▼0.29 | 600.37 ▼74.44 | 48.99 ▼7.06 |
Media Library /wp-admin/upload.php | 1,392 ▲7 | 4.22 ▲0.01 | 95.61 ▼5.21 | 42.24 ▼1.17 |
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
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- widget_vejret_widget
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
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
Almost there! Just fix the following items
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/vejret-widget/admin/partials/vejret-admin-display.php
- > /wp-content/plugins/vejret-widget/public/partials/vejret-public-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Screenshots: Add a description for screenshot #1 in vejret-widget/assets to your readme.txt
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== vejret-widget ===
)
vejret-widget/vejret.php 85% from 13 tests
This is the main PHP file of "Vejret Widget" version 1.0.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("vejret-widget.php" instead of "vejret.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Good job! No executable or dangerous file extensions detected744 lines of code in 16 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 12 | 147 | 542 | 398 |
JavaScript | 2 | 38 | 52 | 183 |
CSS | 2 | 18 | 8 | 163 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 4.62 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 27.00 |
Average method complexity | 2.07 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 24.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 27 | |
▷ Static methods | 2 | 7.41% |
▷ Public methods | 22 | 81.48% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 18.52% |
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 Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin