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.04MB] [CPU: ▼1.32ms] Passed 4 tests
An overview of server-side resources used by Google Trends for WP
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.04 | 38.94 ▲2.64 |
Dashboard /wp-admin | 3.34 ▼0.00 | 43.85 ▼15.03 |
Posts /wp-admin/edit.php | 3.40 ▲0.04 | 48.42 ▲3.39 |
Add New Post /wp-admin/post-new.php | 5.94 ▲0.06 | 85.78 ▲3.71 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 36.28 ▲5.29 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 20 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Google Trends for WP: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,866 ▲119 | 16.27 ▲1.93 | 1.86 ▲0.15 | 38.36 ▼1.75 |
Dashboard /wp-admin | 2,249 ▲68 | 7.57 ▲1.86 | 210.99 ▲98.60 | 40.65 ▼3.17 |
Posts /wp-admin/edit.php | 2,163 ▲60 | 6.26 ▲4.33 | 57.68 ▲16.05 | 37.47 ▲2.48 |
Add New Post /wp-admin/post-new.php | 7,447 ▲5,918 | 23.94 ▲0.93 | 1,078.40 ▲469.06 | 110.32 ▲54.41 |
Media Library /wp-admin/upload.php | 1,467 ▲70 | 8.10 ▲3.94 | 135.93 ▲36.31 | 43.12 ▲0.99 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
- db_upgraded
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/codedeyo-google-trends-for-bloggers/includes/google-trends.php
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)
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need to be fixed:
- Screenshots: Please add descriptions for these screenshots #1, #2 in codedeyo-google-trends-for-bloggers/assets to your readme.txt
- Tags: You are using too many tags: 27 tag instead of maximum 10
codedeyo-google-trends-for-bloggers/codedeyo-google-trends-for-bloggers.php 92% from 13 tests
The main file in "Google Trends for WP" v. 3.2.4 serves as a complement to information provided in readme.txt and as the entry point to the plugin
The following require your attention:
- 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 a short overview of programming languages used in this plugin, detecting executable files
There were no executable files found in this plugin1,607 lines of code in 9 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 2 | 96 | 286 | 1,279 |
CSS | 2 | 3 | 8 | 140 |
PHP | 4 | 17 | 71 | 113 |
Markdown | 1 | 52 | 0 | 75 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.12 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.12 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 2.00 |
Code structure | ||
---|---|---|
Namespaces | 1 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
2 PNG files occupy 0.01MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
img/us.png | 4.54KB | 4.41KB | ▼ 2.80% |
img/ng.png | 6.83KB | 1.48KB | ▼ 78.38% |