Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.02MB] [CPU: ▼4.07ms] Passed 4 tests
Server-side resources used by Tabsy
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.50 ▲0.04 | 38.84 ▼3.42 |
| Dashboard /wp-admin | 3.33 ▲0.03 | 49.26 ▲0.82 |
| Posts /wp-admin/edit.php | 3.38 ▲0.02 | 46.91 ▼3.44 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 83.46 ▼6.35 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.75 ▼3.08 |
Server storage [IO: ▲0.78MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 20 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| widget_theysaidso_widget |
| widget_recent-posts |
| can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Tabsy
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,887 ▲141 | 13.65 ▼0.65 | 5.25 ▲3.45 | 38.37 ▼8.69 |
| Dashboard /wp-admin | 2,206 ▲27 | 5.78 ▲0.90 | 114.57 ▲2.91 | 51.21 ▲6.94 |
| Posts /wp-admin/edit.php | 2,089 ▼3 | 2.01 ▲0.00 | 33.20 ▼6.56 | 33.12 ▼3.08 |
| Add New Post /wp-admin/post-new.php | 1,534 ▲15 | 23.27 ▲0.12 | 694.99 ▲45.84 | 63.37 ▼0.04 |
| Media Library /wp-admin/upload.php | 1,382 ▼3 | 4.23 ▲0.05 | 102.38 ▼6.37 | 45.05 ▲0.26 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
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 take a closer look at the following
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/tabsy/core/functions.enqueue.php:26
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/tabsy/core/functions.shortcode.php:23
- > 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 issues were found
Optimizations
Plugin configuration 86% 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:
- Tags: Please reduce the number of tags, currently 20 tag instead of maximum 10
tabsy/wp-tabsy.php 77% from 13 tests
"Tabsy" version 1.4's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("tabsy.php" instead of "wp-tabsy.php")
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Description: Please keep the plugin description shorter than 140 characters (currently 170 characters long)
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
No dangerous file extensions were detected2,752 lines of code in 11 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 3 | 0 | 12 | 1,794 |
| SVG | 2 | 0 | 0 | 577 |
| JavaScript | 3 | 30 | 36 | 256 |
| PHP | 3 | 27 | 49 | 125 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 13.00 |
| ▷ Minimum class complexity | 13.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 3.40 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 7.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 5 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 5 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 1 | |
| ▷ Named functions | 1 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin