Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▼1.58MB] [CPU: ▼53.23ms] Passed 4 tests
An overview of server-side resources used by runnerplace-calendar
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.41 ▼1.05 | 11.59 ▼33.93 |
| Dashboard /wp-admin | 2.42 ▼0.88 | 13.07 ▼42.76 |
| Posts /wp-admin/edit.php | 2.43 ▼0.93 | 12.26 ▼43.31 |
| Add New Post /wp-admin/post-new.php | 2.42 ▼3.46 | 11.32 ▼92.92 |
| Media Library /wp-admin/upload.php | 2.43 ▼0.80 | 10.41 ▼29.65 |
Server storage [IO: ▲0.09MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_rprc_widget |
| widget_recent-posts |
| can_compress_scripts |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for runnerplace-calendar
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.33 ▼0.23 | 1.69 ▼0.06 | 42.39 ▼4.11 |
| Dashboard /wp-admin | 2,198 ▲21 | 5.63 ▲0.04 | 94.66 ▲3.67 | 41.79 ▼3.04 |
| Posts /wp-admin/edit.php | 2,100 ▼3 | 1.95 ▼0.06 | 36.90 ▼4.27 | 35.09 ▲0.92 |
| Add New Post /wp-admin/post-new.php | 1,534 ▲6 | 18.22 ▼4.82 | 615.41 ▼76.16 | 66.79 ▲6.21 |
| Media Library /wp-admin/upload.php | 1,397 ▼3 | 4.19 ▼0.01 | 97.00 ▼22.52 | 42.78 ▼9.74 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Uninstall procedure had uncaught errors
- > Deprecated in wp-content/plugins/calendario-runnerplace/includes/widget.php+4
Methods with the same name as their class will not be constructors in a future version of PHP; RPRC_widget has a deprecated constructor
- Zombie WordPress options detected upon uninstall: 7 options
- widget_theysaidso_widget
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_rprc_widget
- can_compress_scripts
- 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)
The smoke test was a success, however most plugin functionality was not tested
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
Please fix the following
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/calendario-runnerplace/includes/widget.php
- > /wp-content/plugins/calendario-runnerplace/runnerplace-calendar.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 96% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
2 plugin tags: runnerplace, calendario-carreras-populares
calendario-runnerplace/runnerplace-calendar.php 92% from 13 tests
The principal PHP file in "runnerplace-calendar" v. 1.1.2 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("calendario-runnerplace.php" instead of "runnerplace-calendar.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin383 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 47 | 32 | 383 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.27 |
| Average class complexity | 21.00 |
| ▷ Minimum class complexity | 21.00 |
| ▷ Maximum class complexity | 21.00 |
| Average method complexity | 6.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 14.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 | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.07MB with 0.05MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-2.png | 44.13KB | 14.23KB | ▼ 67.76% |
| assets/screenshot-1.png | 27.92KB | 10.95KB | ▼ 60.79% |