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.06MB] [CPU: ▼6.70ms] Passed 4 tests
Server-side resources used by m1.MiniWeather
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 38.15 ▼4.95 |
Dashboard /wp-admin | 3.37 ▲0.06 | 45.85 ▼4.23 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 42.98 ▼5.02 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 78.82 ▼12.59 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 34.91 ▲1.36 |
Server storage [IO: ▲0.89MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 16 new files
Database: no new tables, 7 new options
New WordPress options |
---|
db_upgraded |
can_compress_scripts |
widget_m1_miniweather_widget |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
Checking browser requirements for m1.MiniWeather
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,791 ▲30 | 14.39 ▼0.17 | 1.72 ▲0.15 | 45.57 ▲6.17 |
Dashboard /wp-admin | 2,198 ▲20 | 5.63 ▼0.07 | 83.81 ▼18.66 | 38.40 ▼2.10 |
Posts /wp-admin/edit.php | 2,097 ▼3 | 1.95 ▼0.02 | 36.01 ▲1.25 | 34.85 ▼0.45 |
Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.35 ▼0.21 | 669.52 ▼15.30 | 60.85 ▲5.46 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.20 ▲0.02 | 95.90 ▲0.22 | 43.75 ▼1.98 |
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
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- widget_m1_miniweather_widget
- widget_recent-comments
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just 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 load_plugin_textdomain() in wp-content/plugins/m1miniweather/index.php:16
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Please fix the following attributes:
- Screenshots: These screenshots require images: #1 (example screenshot), #2 (find longitude (e.g. 13.41053) & latitude (e.g. 52.524368)), #3 (WordPress backend, Widget m1.MiniWeather)
- Tags: There are too many tags (18 tag instead of maximum 10)
m1miniweather/index.php 85% from 13 tests
The main file in "m1.MiniWeather" v. 0.3 serves as a complement to information provided in readme.txt and as the entry point to the plugin
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 ("m1miniweather.php" instead of "index.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 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected499 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 1 | 0 | 0 | 257 |
PHP | 1 | 38 | 24 | 131 |
PO File | 2 | 32 | 32 | 110 |
CSS | 1 | 0 | 40 | 1 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
Average class complexity | 9.50 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 13.00 |
Average method complexity | 3.43 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 7 | |
▷ Static methods | 2 | 28.57% |
▷ Public methods | 7 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.38MB with 0.25MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 72.41KB | 23.80KB | ▼ 67.12% |
screenshot-1.png | 273.18KB | 101.20KB | ▼ 62.96% |
screenshot-3.png | 43.97KB | 15.18KB | ▼ 65.47% |