Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼2.12ms] Passed 4 tests
Analyzing server-side resources used by TFL Widgets
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.02 | 39.03 ▼1.32 |
| Dashboard /wp-admin | 3.32 ▲0.02 | 48.93 ▼0.15 |
| Posts /wp-admin/edit.php | 3.37 ▲0.02 | 52.56 ▲0.22 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.02 | 87.22 ▼5.55 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.02 | 36.25 ▼1.46 |
Server storage [IO: ▲0.05MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_jel_tfl_wp_widget |
| widget_theysaidso_widget |
| widget_recent-posts |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
This is an overview of browser requirements for TFL Widgets
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.35 ▼0.27 | 1.82 ▲0.25 | 37.41 ▼6.13 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.62 ▼0.02 | 87.81 ▲3.91 | 44.15 ▲1.20 |
| Posts /wp-admin/edit.php | 2,103 ▲3 | 1.94 ▼0.05 | 34.81 ▼10.08 | 36.57 ▼1.96 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 22.99 ▼0.26 | 655.90 ▼24.47 | 68.14 ▲14.65 |
| Media Library /wp-admin/upload.php | 1,403 ▲6 | 4.20 ▲0.00 | 96.68 ▼14.27 | 43.20 ▼1.99 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Zombie WordPress options were found after uninstall: 7 options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
- widget_jel_tfl_wp_widget
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though no errors were found, this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/tfl-widgets/public/partials/jel-tfl-widgets-public-display.php
- > /wp-content/plugins/tfl-widgets/admin/partials/jel-tfl-widgets-admin-display.php
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Class 'WP_Widget' not found in wp-content/plugins/tfl-widgets/includes/class-jel-tfl-widgets-wp-widget.php:26
- > 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)
No browser errors were detected
Optimizations
Plugin configuration 96% from 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
9 plugin tags: transport for london, london underground, tube, tube map, tfl widgets...
tfl-widgets/jel-tfl-widgets.php 92% from 13 tests
Analyzing the main PHP file in "TFL Widgets" version 1.2
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("tfl-widgets.php" instead of "jel-tfl-widgets.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 plugin248 lines of code in 17 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 13 | 154 | 574 | 242 |
| JavaScript | 2 | 4 | 54 | 6 |
| CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.17 |
| Average class complexity | 2.88 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 12.00 |
| Average method complexity | 1.47 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 6.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 8 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 8 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 32 | |
| ▷ Static methods | 2 | 6.25% |
| ▷ Public methods | 27 | 84.38% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 15.62% |
| Functions | 3 | |
| ▷ Named functions | 3 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| 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
No PNG files were detected