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: ▲1.15MB] [CPU: ▲14.73ms] Passed 4 tests
A check of server-side resources used by Tracking Code Manager
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.63 ▲1.17 | 64.35 ▲27.20 |
| Dashboard /wp-admin | 4.45 ▲1.15 | 100.64 ▲58.06 |
| Posts /wp-admin/edit.php | 4.49 ▲1.13 | 53.00 ▲7.89 |
| Add New Post /wp-admin/post-new.php | 7.06 ▲1.17 | 104.03 ▲10.22 |
| Media Library /wp-admin/upload.php | 4.36 ▲1.13 | 45.96 ▲13.62 |
Server storage [IO: ▲10.95MB] [DB: ▲0.07MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 568 new files
Database: no new tables, 12 new options
| New WordPress options |
|---|
| db_upgraded |
| TCM_ShowWhatsNewSeenVersion |
| widget_recent-posts |
| TCM_PluginInstallDate[tracking-code-manager] |
| TCM_PluginUpdateDate[tracking-code-manager] |
| TCM_ShowActivationNotice |
| theysaidso_admin_options |
| TCM_PluginFirstInstall |
| can_compress_scripts |
| widget_theysaidso_widget |
| ... |
Browser metrics Passed 4 tests
An overview of browser requirements for Tracking Code Manager
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,804 ▲69 | 13.31 ▼0.98 | 1.83 ▼0.01 | 42.50 ▼0.73 |
| Dashboard /wp-admin | 2,213 ▲25 | 5.85 ▼0.06 | 101.28 ▼13.34 | 43.75 ▼2.44 |
| Posts /wp-admin/edit.php | 2,090 ▲1 | 2.02 ▼0.02 | 34.76 ▼0.57 | 32.13 ▼0.09 |
| Add New Post /wp-admin/post-new.php | 6,331 ▲4,817 | 19.24 ▲1.73 | 834.06 ▲196.75 | 60.75 ▲10.56 |
| Media Library /wp-admin/upload.php | 1,386 ▼5 | 4.24 ▼0.01 | 94.48 ▼4.66 | 41.97 ▼2.45 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
- Zombie WordPress options were found after uninstall: 12 options
- TCM_PluginInstallDate[tracking-code-manager]
- widget_recent-comments
- TCM_ShowWhatsNewSeenVersion
- theysaidso_admin_options
- db_upgraded
- TCM_ShowWhatsNew
- TCM_ShowActivationNotice
- TCM_PluginUpdateDate[tracking-code-manager]
- widget_theysaidso_widget
- TCM_PluginFirstInstall
- ...
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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 take a closer look at the following
- 5× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/tracking-code-manager/index.php:13
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/tracking-code-manager/includes/core.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/tracking-code-manager/includes/admin/metabox.php:74
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/tracking-code-manager/includes/install.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function register_uninstall_hook() in wp-content/plugins/tracking-code-manager/includes/uninstall.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% 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
Attributes that need to be fixed:
- Tags: Too many tags (39 tag instead of maximum 10); only the first 5 tags are used in your directory listing
- Screenshots: These screenshots do not have images: #1 (New tracking code scripts), #2 (Include tracking code in specific page), #3 (Choose easily by typing the page title), #4 (Include also [All] posts or pages without selecting all one-by-one), #5 (List your tracking codes defined), #6 (Tracking code manager is also as a metabox in your posts/pages (you can remove by settings))
tracking-code-manager/index.php 77% from 13 tests
"Tracking Code Manager" version 2.0.16's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 169 characters long)
- Requires at least: Required version does not match the one declared in readme.txt ("2.7" instead of "3.6.0")
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("tracking-code-manager.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 plugin18,707 lines of code in 543 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 507 | 1,867 | 463 | 8,979 |
| PHP | 29 | 663 | 841 | 6,442 |
| SVG | 1 | 0 | 0 | 2,671 |
| CSS | 6 | 65 | 6 | 615 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.42 |
| Average class complexity | 67.25 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 472.00 |
| Average method complexity | 3.67 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 77.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 16 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 16 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 397 | |
| ▷ Static methods | 9 | 2.27% |
| ▷ Public methods | 358 | 90.18% |
| ▷ Protected methods | 3 | 0.76% |
| ▷ Private methods | 36 | 9.07% |
| Functions | 33 | |
| ▷ Named functions | 32 | 96.97% |
| ▷ Anonymous functions | 1 | 3.03% |
| Constants | 86 | |
| ▷ Global constants | 70 | 81.40% |
| ▷ Class constants | 16 | 18.60% |
| ▷ Public constants | 16 | 100.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
16 PNG files occupy 0.65MB with 0.29MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-4.png | 35.08KB | 18.86KB | ▼ 46.24% |
| screenshot-3.png | 25.16KB | 15.49KB | ▼ 38.46% |
| assets/images/heart.png | 0.60KB | 0.50KB | ▼ 16.72% |
| assets/landing/mockup.png | 149.86KB | 39.76KB | ▼ 73.47% |
| screenshot-1.png | 65.47KB | 34.06KB | ▼ 47.98% |