Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
It is recommended to fix the following installer errors
- Install procedure validation failed for this plugin
- > Deprecated in wp-content/plugins/wp-jtweets/class_widget.php+2
Methods with the same name as their class will not be constructors in a future version of PHP; jTweetsWidget has a deprecated constructor
Server metrics [RAM: ▼1.83MB] [CPU: ▼54.13ms] Passed 4 tests
Analyzing server-side resources used by WP-jTweets
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.18 ▼1.29 | 4.42 ▼33.50 |
| Dashboard /wp-admin | 2.20 ▼1.15 | 7.47 ▼49.42 |
| Posts /wp-admin/edit.php | 2.20 ▼1.16 | 6.93 ▼44.49 |
| Add New Post /wp-admin/post-new.php | 2.20 ▼3.69 | 6.03 ▼89.09 |
| Media Library /wp-admin/upload.php | 2.20 ▼1.04 | 6.50 ▼26.53 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 8 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| can_compress_scripts |
| widget_jtweetswidget |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
WP-jTweets: an overview of browser usage
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,883 ▲148 | 13.54 ▼1.20 | 8.20 ▲6.50 | 41.41 ▼6.88 |
| Dashboard /wp-admin | 2,206 ▲18 | 4.81 ▼1.09 | 102.46 ▲1.48 | 40.55 ▼4.83 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.01 ▼0.01 | 42.75 ▲1.09 | 37.16 ▼2.50 |
| Add New Post /wp-admin/post-new.php | 1,514 ▼19 | 17.39 ▼5.60 | 688.35 ▲74.40 | 51.57 ▼0.89 |
| Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.24 ▲0.04 | 98.01 ▼3.99 | 42.76 ▼1.77 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin cannot be uninstalled
- > Deprecated in wp-content/plugins/wp-jtweets/class_widget.php+2
Methods with the same name as their class will not be constructors in a future version of PHP; jTweetsWidget has a deprecated constructor
- This plugin did not uninstall successfully, leaving 7 options in the database
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
- widget_jtweetswidget
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking 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
Please fix the following
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/wp-jtweets/index.php:29
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/wp-jtweets/class_widget.php:2
- > 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 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
7 plugin tags: twitter, json, status, cycle, tweets...
wp-jtweets/index.php 92% from 13 tests
Analyzing the main PHP file in "WP-jTweets" version 1.1.5
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("wp-jtweets.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin1,028 lines of code in 6 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 211 | 333 | 986 |
| JavaScript | 1 | 5 | 0 | 30 |
| CSS | 1 | 3 | 2 | 12 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.30 |
| Average class complexity | 10.92 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 47.00 |
| Average method complexity | 2.72 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 28.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 13 | |
| ▷ Abstract classes | 2 | 15.38% |
| ▷ Concrete classes | 11 | 84.62% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 79 | |
| ▷ Static methods | 10 | 12.66% |
| ▷ Public methods | 68 | 86.08% |
| ▷ Protected methods | 2 | 2.53% |
| ▷ Private methods | 9 | 11.39% |
| Functions | 6 | |
| ▷ Named functions | 6 | 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 Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
There are no PNG files in this plugin