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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.20MB] [CPU: ▼0.94ms] Passed 4 tests
A check of server-side resources used by FV Swiftype
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.67 ▲0.21 | 38.93 ▼3.56 |
| Dashboard /wp-admin | 3.50 ▲0.20 | 46.92 ▼4.98 |
| Posts /wp-admin/edit.php | 3.62 ▲0.26 | 49.65 ▲0.40 |
| Add New Post /wp-admin/post-new.php | 6.08 ▲0.20 | 95.72 ▲4.37 |
| Media Library /wp-admin/upload.php | 3.42 ▲0.20 | 39.39 ▲5.24 |
| FV Swiftype /wp-admin/options-general.php?page=fv_swiftype | 3.36 | 32.54 |
Server storage [IO: ▲0.14MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 6 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_recent-comments |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
FV Swiftype: an overview of browser usage
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,819 ▲62 | 13.19 ▼1.16 | 1.57 ▼0.72 | 40.89 ▼4.42 |
| Dashboard /wp-admin | 2,219 ▲31 | 4.85 ▼1.05 | 109.42 ▲4.33 | 42.91 ▼4.72 |
| Posts /wp-admin/edit.php | 2,101 ▲12 | 2.04 ▲0.04 | 39.67 ▲6.28 | 36.24 ▼1.50 |
| Add New Post /wp-admin/post-new.php | 1,526 ▲6 | 17.78 ▼5.23 | 667.23 ▼9.51 | 65.71 ▲8.70 |
| Media Library /wp-admin/upload.php | 1,401 ▲10 | 4.21 ▲0.02 | 97.63 ▼8.67 | 42.41 ▼0.01 |
| FV Swiftype /wp-admin/options-general.php?page=fv_swiftype | 914 | 2.16 | 23.00 | 31.20 |
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
The following items require your attention
- Zombie WordPress options detected upon uninstall: 6 options
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
These server-side errors were triggered
- > GET request to /wp-admin/options-general.php?page=fv_swiftype
- > Notice in wp-content/plugins/fv-swiftype/fv-swiftype.php+512
Undefined index: api_key
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/fv-swiftype/fv-swiftype.php:26
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Please fix the following attributes:
- Screenshots: Screenshot #1 (FV Switftype settings) image missing
fv-swiftype/fv-swiftype.php Passed 13 tests
The main file in "FV Swiftype" v. 0.3.8 serves as a complement to information provided in readme.txt and as the entry point to the plugin
36 characters long description:
Use Swiftype engine for your search.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Success! There were no dangerous files found in this plugin1,236 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 4 | 399 | 261 | 1,236 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 52.50 |
| ▷ Minimum class complexity | 10.00 |
| ▷ Maximum class complexity | 127.00 |
| Average method complexity | 3.17 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 24.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 4 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 4 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 87 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 72 | 82.76% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 15 | 17.24% |
| Functions | 0 | |
| ▷ Named functions | 0 | 0.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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.08MB with 0.05MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-1.png | 78.17KB | 27.83KB | ▼ 64.40% |