Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.02MB] [CPU: ▼9.33ms] Passed 4 tests
Server-side resources used by WP Historical Weather
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 42.27 ▼0.34 |
| Dashboard /wp-admin | 3.33 ▼0.01 | 49.34 ▼23.49 |
| Posts /wp-admin/edit.php | 3.38 ▲0.03 | 52.41 ▲2.72 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 94.43 ▼11.62 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 36.82 ▼1.86 |
Server storage [IO: ▲0.35MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 14 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| db_upgraded |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
A check of browser resources used by WP Historical Weather
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,791 ▲45 | 14.22 ▼0.16 | 1.75 ▲0.04 | 43.58 ▼0.17 |
| Dashboard /wp-admin | 2,195 ▲15 | 5.52 ▼0.14 | 85.86 ▼7.93 | 39.58 ▼4.60 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 2.14 ▲0.16 | 32.85 ▼2.48 | 34.57 ▼1.15 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.14 ▲0.10 | 667.60 ▼18.72 | 48.70 ▼21.42 |
| Media Library /wp-admin/upload.php | 1,394 ▼9 | 4.17 ▼0.04 | 95.04 ▼13.82 | 43.13 ▼6.18 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-historical-weather/hw.php:10
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
Attributes that require attention:
- Screenshots: These screenshots do not have images: #1 (https://github.com/TurnereManager/Historical-Weather/blob/master/inline.png), #2 (https://github.com/TurnereManager/Historical-Weather/blob/master/historical.PNG), #3 (https://github.com/TurnereManager/Historical-Weather/blob/master/thumbnail.png)
wp-historical-weather/hw.php 92% from 13 tests
The primary PHP file in "WP Historical Weather" version 1.0 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("wp-historical-weather.php" instead of "hw.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
There were no executable files found in this plugin684 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 2 | 0 | 45 | 389 |
| SVG | 1 | 0 | 0 | 153 |
| PHP | 2 | 12 | 8 | 137 |
| Markdown | 1 | 3 | 0 | 5 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.35 |
| Average class complexity | 11.00 |
| ▷ Minimum class complexity | 11.00 |
| ▷ Maximum class complexity | 11.00 |
| Average method complexity | 3.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 9.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 | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 3 | 75.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 1 | 25.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.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
3 PNG files occupy 0.04MB with 0.02MB in potential savings
Potential savings
| Compression of 3 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| thumbnail.png | 5.31KB | 2.52KB | ▼ 52.46% |
| historical.PNG | 8.17KB | 4.59KB | ▼ 43.83% |
| inline.png | 23.23KB | 10.06KB | ▼ 56.69% |