Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▼1.54MB] [CPU: ▼48.09ms] Passed 4 tests
Analyzing server-side resources used by ExXmlRpc for WordPressPost
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.45 ▼1.01 | 9.40 ▼33.49 |
| Dashboard /wp-admin | 2.46 ▼0.84 | 12.62 ▼34.01 |
| Posts /wp-admin/edit.php | 2.46 ▼0.89 | 11.30 ▼40.18 |
| Add New Post /wp-admin/post-new.php | 2.46 ▼3.42 | 12.40 ▼84.66 |
| Media Library /wp-admin/upload.php | 2.46 ▼0.76 | 11.96 ▼23.34 |
Server storage [IO: ▲0.64MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| theysaidso_admin_options |
| db_upgraded |
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for ExXmlRpc for WordPressPost
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.22 ▼1.03 | 1.71 ▼0.30 | 44.58 ▲5.51 |
| Dashboard /wp-admin | 2,209 ▲21 | 5.88 ▼0.03 | 101.49 ▼8.04 | 41.06 ▲1.90 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 1.99 ▼0.06 | 35.42 ▼1.98 | 30.91 ▼0.79 |
| Add New Post /wp-admin/post-new.php | 1,533 ▼0 | 22.92 ▼0.21 | 660.23 ▼30.42 | 53.26 ▲2.74 |
| Media Library /wp-admin/upload.php | 1,379 ▼6 | 4.19 ▼0.03 | 98.29 ▲4.41 | 42.08 ▼3.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The plugin did not uninstall gracefully
- > Notice in wp-content/plugins/exxmlrpc/exXmlRpc.php+19
Trying to access array offset on value of type bool
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for 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 | 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
The following issues need your attention
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/exxmlrpc/exXmlRpc.php:14
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 81% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== exxmlrpc ===) - Donate link: Please fix this invalid url: ""
- Screenshots: Please add images for these screenshots: #1 (WordPressPost ( windows software )), #2 (Support Media library.), #3 (Support to easy edit images.), #4 (Support to embed youtube movies.)
exxmlrpc/exXmlRpc.php 92% from 13 tests
The entry point to "ExXmlRpc for WordPressPost" version 0.2.1.0 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("exxmlrpc.php" instead of "exXmlRpc.php")
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 detected589 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 199 | 66 | 589 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.44 |
| Average class complexity | 130.00 |
| ▷ Minimum class complexity | 130.00 |
| ▷ Maximum class complexity | 130.00 |
| Average method complexity | 10.92 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 29.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 | 13 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 13 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 2 | |
| ▷ Named functions | 2 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 1 | |
| ▷ Global constants | 1 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
4 PNG files occupy 0.62MB with 0.39MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 76.76KB | 27.66KB | ▼ 63.96% |
| screenshot-3.png | 227.06KB | 78.21KB | ▼ 65.55% |
| screenshot-1.png | 256.24KB | 93.00KB | ▼ 63.71% |
| screenshot-4.png | 71.54KB | 31.09KB | ▼ 56.54% |