Benchmarks
Plugin footprint 83% 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.02MB] [CPU: ▼9.57ms] Passed 4 tests
Server-side resources used by Post To Twitter
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 41.61 ▼2.64 |
Dashboard /wp-admin | 3.34 ▼0.01 | 50.45 ▼19.08 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 48.88 ▼1.50 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 92.56 ▼13.97 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 36.56 ▼2.60 |
Post To Twitter /wp-admin/options-general.php?page=post-to-twitter | 3.23 | 36.13 |
Server storage [IO: ▲0.31MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 8 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
db_upgraded |
can_compress_scripts |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Post To Twitter
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲47 | 14.34 ▲0.19 | 1.97 ▲0.16 | 45.45 ▲0.76 |
Dashboard /wp-admin | 2,199 ▲25 | 5.50 ▼0.16 | 90.63 ▼2.17 | 38.66 ▼6.60 |
Posts /wp-admin/edit.php | 2,104 ▲1 | 2.02 ▲0.01 | 35.59 ▼7.79 | 36.27 ▼3.41 |
Add New Post /wp-admin/post-new.php | 1,529 ▼6 | 23.18 ▲4.95 | 672.52 ▲16.39 | 72.32 ▲3.56 |
Media Library /wp-admin/upload.php | 1,404 ▲7 | 4.26 ▲0.07 | 100.63 ▼2.21 | 41.46 ▼3.69 |
Post To Twitter /wp-admin/options-general.php?page=post-to-twitter | 891 | 2.04 | 23.04 | 30.52 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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 take a closer look at the following
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/post-to-twitter-duco/index.php
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_fields() in wp-content/plugins/post-to-twitter-duco/views/settings.php:15
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_meta() in wp-content/plugins/post-to-twitter-duco/views/twitter_metabox.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
Please fix the following attributes:
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== post-to-twitter-duco ===
)
post-to-twitter-duco/index.php 92% from 13 tests
The main file in "Post To Twitter" v. 0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("post-to-twitter-duco.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Success! There were no dangerous files found in this plugin1,151 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 163 | 530 | 1,151 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 125.00 |
▷ Minimum class complexity | 125.00 |
▷ Maximum class complexity | 125.00 |
Average method complexity | 3.95 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 42 | |
▷ Static methods | 3 | 7.14% |
▷ Public methods | 15 | 35.71% |
▷ Protected methods | 27 | 64.29% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 14 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 2 | 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
PNG images were not found in this plugin