Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▼0.58MB] [CPU: ▼12.65ms] Passed 4 tests
A check of server-side resources used by ContentMX Content Publisher
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.56 ▲0.10 | 39.69 ▼4.05 |
| Dashboard /wp-admin | 3.40 ▲0.10 | 46.09 ▼0.10 |
| Posts /wp-admin/edit.php | 3.52 ▲0.16 | 50.69 ▲4.56 |
| Add New Post /wp-admin/post-new.php | 3.28 ▼2.61 | 34.83 ▼48.33 |
| Media Library /wp-admin/upload.php | 3.32 ▲0.10 | 34.43 ▲1.89 |
Server storage [IO: ▲0.36MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 10 new files
Database: 2 new tables, 9 new options
| New tables |
|---|
| wp_contentmx_block_list |
| wp_contentmx_ccm |
| New WordPress options |
|---|
| widget_recent-comments |
| db_upgraded |
| cmx_ccm_vers |
| cmx_ccm_ip_whitelist |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
| theysaidso_admin_options |
| cmx_ccm_call_dir_target |
Browser metrics Passed 4 tests
An overview of browser requirements for ContentMX Content Publisher
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,812 ▲66 | 13.29 ▼1.33 | 1.59 ▼0.60 | 41.45 ▼10.39 |
| Dashboard /wp-admin | 2,212 ▲24 | 5.79 ▲0.87 | 102.61 ▼5.44 | 40.58 ▲1.03 |
| Posts /wp-admin/edit.php | 2,101 ▲12 | 1.99 ▼0.06 | 40.11 ▲2.14 | 35.51 ▲0.01 |
| Add New Post /wp-admin/post-new.php | 1,552 ▲38 | 18.32 ▲0.70 | 647.13 ▼26.54 | 51.35 ▼3.41 |
| Media Library /wp-admin/upload.php | 1,400 ▲12 | 4.32 ▲0.10 | 95.74 ▼10.39 | 41.41 ▼0.80 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- Zombie tables detected upon uninstall: 2 tables
- wp_contentmx_ccm
- wp_contentmx_block_list
- Zombie WordPress options were found after uninstall: 9 options
- theysaidso_admin_options
- cmx_ccm_vers
- db_upgraded
- cmx_ccm_ip_whitelist
- cmx_ccm_call_dir_target
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following
- 5× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/contentmx-content-publisher/index_cmx.php:14
- > PHP Notice
Trying to get property 'wp_posts' of non-object in wp-content/plugins/contentmx-content-publisher/inc/admin.php on line 10
- > PHP Notice
Trying to get property 'prefix' of non-object in wp-content/plugins/contentmx-content-publisher/inc/admin.php on line 5
- > PHP Fatal error
Uncaught Error: Call to a member function get_results() on null in wp-content/plugins/contentmx-content-publisher/inc/admin.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function contentmx_content_manager\\get_option() in wp-content/plugins/contentmx-content-publisher/inc/functions.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 94% from 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
Attributes that need to be fixed:
- Screenshots: These screenshots require images: #1 (After you have installed the plugin and activated it. Create a Wordpress network in your ContentMX account. Add a plugin to that network using the URL of your wordpress site. Click the plus icon to add the URL.), #2 (Click "Activate connection" next to the plugin you just added. This will prompt you to login to your Wordpress site and authorize the connection. Once you sign in, you should see the ContentMX account has been added to Wordpress.), #3 (Now go back to your Wordpress network or add a new network in your ContentMX account. You should see that the connection has been established. Click "Test connection" next to the plugin. This will verify that you can publish content and that nothing is blocking this feature.), #4 (If you see "Connected" and "Able to post" in green next to your plugin you can now check the radio button next to the plugin to select it as the connection for this Wordpress network.), #5 (Scroll to the bottom of the page and click to Save the network.)
contentmx-content-publisher/index_cmx.php 69% from 13 tests
"ContentMX Content Publisher" version 1.0.6's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Requires PHP: Required version does not match the one declared in readme.txt ("7.0" instead of "5.6")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 362 characters long)
- Main file name: The principal plugin file should be the same as the plugin slug ("contentmx-content-publisher.php" instead of "index_cmx.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
There were no executable files found in this plugin528 lines of code in 3 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 105 | 49 | 528 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.57 |
| 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 | 1 | |
| 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 | 21 | |
| ▷ Named functions | 20 | 95.24% |
| ▷ Anonymous functions | 1 | 4.76% |
| 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
5 PNG files occupy 0.34MB with 0.21MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/2.png | 71.19KB | 26.01KB | ▼ 63.47% |
| assets/1.png | 77.15KB | 27.87KB | ▼ 63.88% |
| assets/4.png | 99.75KB | 34.89KB | ▼ 65.02% |
| assets/5.png | 21.67KB | 9.00KB | ▼ 58.46% |
| assets/3.png | 74.96KB | 27.37KB | ▼ 63.49% |