Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼1.52ms] Passed 4 tests
Analyzing server-side resources used by Calendario del Perú
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 40.07 ▲1.98 |
Dashboard /wp-admin | 3.34 ▲0.04 | 48.94 ▲0.69 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 48.82 ▲1.99 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 84.04 ▼9.10 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 35.58 ▲0.37 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Calendario del Perú
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲90 | 14.74 ▲0.51 | 2.06 ▲0.32 | 45.72 ▲5.16 |
Dashboard /wp-admin | 2,206 ▲21 | 5.91 ▲0.05 | 107.13 ▲0.55 | 39.44 ▼1.89 |
Posts /wp-admin/edit.php | 2,089 ▲3 | 1.98 ▼0.01 | 39.52 ▲3.34 | 35.40 ▲1.85 |
Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 23.30 ▲0.04 | 691.21 ▲16.11 | 53.33 ▲3.25 |
Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.19 ▼0.02 | 93.75 ▼18.57 | 45.71 ▼2.82 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_register_sidebar_widget() in wp-content/plugins/calendario-del-peru/wp-xml-rss-parser.php:43
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
- Tags: There are too many tags (16 tag instead of maximum 10)
- Screenshots: These screenshots require images: #1 (Muestra como se ve el widget screenshot-1.png en el tema Twenty Fourteen), #2 (Instalando el widget en su tema)
calendario-del-peru/wp-xml-rss-parser.php 77% from 13 tests
"Calendario del Perú" version 1...'s main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
You should first fix the following items:
- Description: Please don't use more than 140 characters for the plugin description (currently 274 characters long)
- Version: Plugin version number should only contain digits separated by dots (ex. "1.0.3" instead of "1...")
- Main file name: It is recommended to name the main PHP file as the plugin slug ("calendario-del-peru.php" instead of "wp-xml-rss-parser.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
No dangerous file extensions were detected150 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 21 | 63 | 150 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.45 |
Average class complexity | 35.00 |
▷ Minimum class complexity | 35.00 |
▷ Maximum class complexity | 35.00 |
Average method complexity | 9.50 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 25.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
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.09MB with 0.06MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 71.36KB | 19.96KB | ▼ 72.03% |
screenshot-1.png | 18.34KB | 5.01KB | ▼ 72.69% |