Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.00MB] [CPU: ▼4.33ms] Passed 4 tests
This is a short check of server-side resources used by Freshsales Integration for WordPress
No issues were detected with server-side resource usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.48 ▲0.02 | 41.07 ▲3.32 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 58.51 ▼1.75 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.28 ▼3.84 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 81.55 ▼13.78 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 35.48 ▲2.06 |
Server storage [IO: ▲0.33MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 11 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-comments |
| can_compress_scripts |
| WpLeadBuilderProActivatedPlugin |
| widget_theysaidso_widget |
| widget_recent-posts |
Browser metrics Passed 4 tests
An overview of browser requirements for Freshsales Integration for WordPress
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲3 | 14.16 ▼0.37 | 1.81 ▲0.07 | 42.20 ▲6.40 |
| Dashboard /wp-admin | 2,195 ▲23 | 5.52 ▼0.22 | 83.50 ▼20.03 | 38.45 ▼6.63 |
| Posts /wp-admin/edit.php | 2,100 ▲3 | 2.00 ▼0.00 | 35.33 ▲0.35 | 32.98 ▼2.37 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.48 ▲0.36 | 680.19 ▼8.39 | 60.37 ▲3.53 |
| Media Library /wp-admin/upload.php | 1,400 ▼3 | 4.18 ▼0.05 | 92.23 ▼16.68 | 42.46 ▲0.01 |
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
- Zombie WordPress options were found after uninstall: 7 options
- db_upgraded
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- widget_recent-posts
- WpLeadBuilderProActivatedPlugin
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Everything seems fine, however this is by no means an exhaustive test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
These attributes need your attention:
- Screenshots: Screenshot #1 (Wp Freshsales configuratios.) image required
- Tags: Please delete some tags, you are using 14 tag instead of maximum 10
wp-freshsales/index.php 85% from 13 tests
The principal PHP file in "Freshsales Integration for WordPress" v. 2.1 is loaded by WordPress automatically on each request
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wp-freshsales.php" instead of "index.php")
- Domain Path: The domain path folder was not found ("/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
Good job! No executable or dangerous file extensions detected733 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 118 | 167 | 733 |
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.20 |
| Average class complexity | 9.50 |
| ▷ Minimum class complexity | 2.00 |
| ▷ Maximum class complexity | 37.00 |
| Average method complexity | 2.14 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 13.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 6 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 6 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 45 | |
| ▷ Static methods | 8 | 17.78% |
| ▷ Public methods | 40 | 88.89% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 5 | 11.11% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 11 | |
| ▷ Global constants | 11 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.28MB with 0.17MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/wordpress-to-freshsale-banner.png | 184.45KB | 81.12KB | ▼ 56.02% |
| screenshot-01.png | 99.49KB | 32.17KB | ▼ 67.67% |