Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.48ms] Passed 4 tests
Server-side resources used by Pull To Resfresh
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 36.09 ▼2.04 |
Dashboard /wp-admin | 3.31 ▲0.01 | 44.23 ▼3.96 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.47 ▼2.58 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 83.57 ▼13.34 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.10 ▲2.29 |
Server storage [IO: ▲0.10MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 12 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-comments |
db_upgraded |
can_compress_scripts |
widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Pull To Resfresh
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,971 ▲236 | 13.71 ▼0.85 | 11.80 ▲10.02 | 50.70 ▲5.85 |
Dashboard /wp-admin | 2,206 ▲15 | 5.86 ▲0.97 | 106.96 ▲2.80 | 39.77 ▼5.67 |
Posts /wp-admin/edit.php | 2,089 ▼3 | 1.98 ▼0.05 | 35.83 ▼7.82 | 37.22 ▲1.39 |
Add New Post /wp-admin/post-new.php | 1,514 ▼28 | 17.41 ▼0.73 | 683.80 ▲64.78 | 57.93 ▼13.30 |
Media Library /wp-admin/upload.php | 1,382 ▼6 | 4.20 ▼0.08 | 97.20 ▲1.99 | 41.98 ▲1.85 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- 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
Even though no errors were found, this is by no means an exhaustive test
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× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/pull-to-refresh/pulltorefresh.php:60
- > 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 Passed 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
4 plugin tags: refresh, pull down, pull to refresh, refresh page
pull-to-refresh/pulltorefresh.php 85% from 13 tests
The primary PHP file in "Pull To Resfresh" version 1.1 is used by WordPress to initiate all plugin functionality
Please make the necessary changes and fix the following:
- Description: Please don't use more than 140 characters for the plugin description (currently 476 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("pull-to-refresh.php" instead of "pulltorefresh.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected1,726 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 2 | 475 | 1,022 | 1,483 |
PHP | 1 | 72 | 57 | 160 |
CSS | 1 | 18 | 24 | 81 |
HTML | 2 | 0 | 0 | 2 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.00 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 5 | |
▷ Named functions | 5 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 compressed PNG files occupy 0.00MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/css/assets/img/spinner.png | 0.78KB | 1.00KB | 0.00% |
assets/css/assets/img/arrow.png | 0.49KB | 0.57KB | 0.00% |