Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲0.66MB] [CPU: ▲2,068.02ms] 75% from 4 tests
This is a short check of server-side resources used by Auto Post, Auto Publish and Schedule to Facebook, Twitter, LinkedIn - WP to Buffer
Please have a look at the following items
- Extra CPU: Try to keep extra CPU usage under 200.00ms (currently 2,068.02ms on /wp-admin/admin.php?page=wp-to-buffer-upgrade)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.74 ▲0.27 | 47,502.81 ▲8,327.35 |
Dashboard /wp-admin | 3.74 ▲0.27 | 47,896.33 ▲8,233.06 |
Posts /wp-admin/edit.php | 4.50 ▲1.10 | 65.76 ▲13.06 |
Add New Post /wp-admin/post-new.php | 6.99 ▲1.06 | 109.21 ▲12.69 |
Media Library /wp-admin/upload.php | 4.31 ▲1.03 | 51.86 ▲13.27 |
Settings /wp-admin/admin.php?page=wp-to-buffer-settings | 4.31 | 46.95 |
Logs /wp-admin/admin.php?page=wp-to-buffer-log | 4.35 | 46.60 |
Upgrade /wp-admin/admin.php?page=wp-to-buffer-upgrade | 2.31 | 10.13 |
Server storage [IO: ▲1.11MB] [DB: ▲0.01MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 398 new files
Database: 1 new table, 9 new options
New tables |
---|
wp_to_buffer_log |
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
wp-to-buffer-pro-log |
wp-to-buffer-pro-post |
widget_theysaidso_widget |
widget_recent-posts |
wp-to-buffer-version |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Auto Post, Auto Publish and Schedule to Facebook, Twitter, LinkedIn - WP to Buffer
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,860 ▲114 | 14.25 ▼0.31 | 1.63 ▲0.05 | 44.50 ▲3.08 |
Dashboard /wp-admin | 2,269 ▲98 | 5.59 ▲0.02 | 86.15 ▼2.16 | 83.82 ▲43.61 |
Posts /wp-admin/edit.php | 2,172 ▲72 | 1.98 ▼0.02 | 40.38 ▼2.69 | 36.28 ▲1.56 |
Add New Post /wp-admin/post-new.php | 6,564 ▲5,036 | 29.19 ▲6.15 | 958.66 ▲271.03 | 72.62 ▲17.71 |
Media Library /wp-admin/upload.php | 1,468 ▲68 | 4.22 ▼0.02 | 115.19 ▼0.09 | 85.94 ▲35.04 |
Settings /wp-admin/admin.php?page=wp-to-buffer-settings | 1,050 | 3.09 | 43.12 | 83.65 |
Logs /wp-admin/admin.php?page=wp-to-buffer-log | 1,504 | 1.99 | 26.62 | 35.30 |
Upgrade /wp-admin/admin.php?page=wp-to-buffer-upgrade | 3,221 | 12.53 | 386.35 | 156.48 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- The uninstall procedure failed, leaving 1 table in the database
- wp_to_buffer_log
- This plugin did not uninstall successfully, leaving 9 options in the database
- widget_recent-comments
- db_upgraded
- wp-to-buffer-version
- wp-to-buffer-pro-log
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- wp-to-buffer-pro-post
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Smoke test failed, please fix the following
- 91 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-to-buffer-upgrade
- > Warning in wp-content/plugins/easy-age-verifier/lib/extras/wpApi.php+48
file_get_contents(): php_network_getaddresses: getaddrinfo failed: Name or service not known
- 91 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wp-to-buffer-upgrade
- > Warning in wp-content/plugins/easy-age-verifier/lib/extras/wpApi.php+48
file_get_contents(http://www.fillyourtaproom.com/wp-json/wp/v2/posts?per_page=10): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 28× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-to-buffer/includes/cron.php:27
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/wp-to-buffer/lib/views/settings-post-action-status.php:11
- > PHP Fatal error
Uncaught Error: Class 'WP_List_Table' not found in wp-content/plugins/wp-to-buffer/lib/includes/class-wp-to-social-pro-log-table.php:16
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/wp-to-buffer/lib/views/log.php:12
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/wp-to-buffer/_modules/dashboard/views/sidebar-upgrade.php:14
- > PHP Fatal error
Uncaught Error: Using $this when not in object context in wp-content/plugins/wp-to-buffer/_modules/dashboard/views/footer-upgrade-embedded.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/wp-to-buffer/_modules/dashboard/views/modal.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/wp-to-buffer/wp-to-buffer.php:28
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/wp-to-buffer/lib/views/settings-post-action.php:11
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/wp-to-buffer/lib/views/settings-post.php:21
- > 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 Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
5 plugin tags: buffer, social media scheduling, auto publish, auto post, social media automation
wp-to-buffer/wp-to-buffer.php Passed 13 tests
"Auto Post, Auto Publish and Schedule to Facebook, Twitter, LinkedIn - WP to Buffer" version 3.9.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
129 characters long description:
Send WordPress Pages, Posts or Custom Post Types to your Buffer (buffer.com) account for scheduled publishing to social networks.
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 plugin15,607 lines of code in 396 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 42 | 1,669 | 2,247 | 6,688 |
PHP | 49 | 1,940 | 4,849 | 6,132 |
Sass | 5 | 234 | 0 | 2,098 |
SVG | 297 | 0 | 2 | 686 |
CSS | 3 | 0 | 0 | 3 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.41 |
Average class complexity | 37.71 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 150.00 |
Average method complexity | 3.87 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 48.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 21 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 21 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 269 | |
▷ Static methods | 1 | 0.37% |
▷ Public methods | 211 | 78.44% |
▷ Protected methods | 2 | 0.74% |
▷ Private methods | 56 | 20.82% |
Functions | 6 | |
▷ Named functions | 6 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin