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
Installer ran successfully
Server metrics [RAM: ▲0.47MB] [CPU: ▼1.53ms] Passed 4 tests
Analyzing server-side resources used by Tweeple
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.94 ▲0.47 | 42.55 ▲2.65 |
Dashboard /wp-admin | 3.82 ▲0.51 | 50.24 ▲0.05 |
Posts /wp-admin/edit.php | 3.87 ▲0.51 | 52.55 ▲4.81 |
Add New Post /wp-admin/post-new.php | 6.33 ▲0.44 | 88.13 ▼13.63 |
Media Library /wp-admin/upload.php | 3.68 ▲0.44 | 39.61 ▲5.60 |
Tweeple /wp-admin/tools.php?page=tweeple | 3.65 | 35.83 |
Server storage [IO: ▲0.38MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 8 new options
New WordPress options |
---|
can_compress_scripts |
db_upgraded |
tweeple_plugin_version |
widget_recent-posts |
widget_tweeple_feed_widget |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Tweeple: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,793 ▲32 | 14.21 ▼0.14 | 1.71 ▼0.01 | 41.58 ▼4.65 |
Dashboard /wp-admin | 2,202 ▲28 | 5.67 ▲0.09 | 90.26 ▼8.24 | 42.65 ▼0.74 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.01 ▲0.01 | 35.71 ▼3.65 | 39.72 ▲1.96 |
Add New Post /wp-admin/post-new.php | 1,529 ▲1 | 23.37 ▲0.10 | 661.77 ▼22.01 | 51.12 ▲0.44 |
Media Library /wp-admin/upload.php | 1,398 ▼2 | 4.20 ▼0.00 | 100.66 ▼9.27 | 43.51 ▼4.77 |
Tweeple /wp-admin/tools.php?page=tweeple | 869 | 2.07 | 27.53 | 27.07 |
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
It is recommended to fix the following
- The uninstall procedure has failed, leaving 8 options in the database
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
- widget_tweeple_feed_widget
- widget_theysaidso_widget
- tweeple_plugin_version
- db_upgraded
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
Good news, no errors were detected
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 items
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/tweeple/inc/class-tweeple-feed-widget.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function plugins_url() in wp-content/plugins/tweeple/tweeple.php:30
- > 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 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
10 plugin tags: status, twitter, tweets, theme blvd, tmhoauth...
tweeple/tweeple.php Passed 13 tests
The main file in "Tweeple" v. 0.9.5 serves as a complement to information provided in readme.txt and as the entry point to the plugin
128 characters long description:
Setup Twitter feeds to pull a user's public timeline, public list, favorite tweets, or a custom search term, phrase, or hashtag.
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
Success! There were no dangerous files found in this plugin2,713 lines of code in 14 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 9 | 660 | 950 | 2,180 |
PO File | 1 | 125 | 139 | 271 |
CSS | 1 | 5 | 6 | 136 |
JavaScript | 1 | 24 | 19 | 50 |
Markdown | 1 | 23 | 0 | 50 |
JSON | 1 | 0 | 0 | 26 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 41.43 |
▷ Minimum class complexity | 8.00 |
▷ Maximum class complexity | 93.00 |
Average method complexity | 4.49 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 24.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 81 | |
▷ Static methods | 11 | 13.58% |
▷ Public methods | 58 | 71.60% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 23 | 28.40% |
Functions | 20 | |
▷ Named functions | 20 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 4 | 66.67% |
▷ Class constants | 2 | 33.33% |
▷ Public constants | 2 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
6 PNG files occupy 0.01MB with 0.01MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/images/icon-refresh_2x.png | 2.61KB | 1.50KB | ▼ 42.51% |
assets/images/icon-refresh.png | 1.67KB | 0.98KB | ▼ 41.39% |
assets/images/icon_2x.png | 3.88KB | 2.24KB | ▼ 42.11% |
assets/images/icon-delete_2x.png | 2.92KB | 1.73KB | ▼ 40.92% |
assets/images/icon.png | 2.38KB | 1.51KB | ▼ 36.65% |