Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.84MB] [CPU: ▲6.50ms] Passed 4 tests
Server-side resources used by SpiderFAQ
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.30 ▲0.83 | 52.77 ▲10.41 |
Dashboard /wp-admin | 4.15 ▲0.84 | 57.50 ▲4.75 |
Posts /wp-admin/edit.php | 4.26 ▲0.90 | 56.87 ▲2.99 |
Add New Post /wp-admin/post-new.php | 6.73 ▲0.84 | 99.43 ▲7.85 |
Media Library /wp-admin/upload.php | 4.07 ▲0.84 | 48.93 ▲10.59 |
Uninstall Spider FAQ /wp-admin/admin.php?page=Uninstall_Spider_FAQ | 4.03 | 36.74 |
Featured Plugins /wp-admin/admin.php?page=Spider_Faq_featured_plugins | 4.03 | 34.95 |
Licensing /wp-admin/admin.php?page=Spider_FAQ_Licensing | 4.03 | 37.68 |
Questions /wp-admin/admin.php?page=Spider_Faq_Questions | 4.21 | 39.41 |
Themes /wp-admin/admin.php?page=Spider_Faq_Themes | 4.55 | 40.37 |
Categories /wp-admin/admin.php?page=Spider_Faq_Categories | 4.10 | 38.63 |
FAQs /wp-admin/admin.php?page=Spider_Faq | 4.23 | 38.42 |
Server storage [IO: ▲2.62MB] [DB: ▲0.03MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 192 new files
Database: 5 new tables, 6 new options
New tables |
---|
wp_spider_faq_faq |
wp_spider_faq_theme |
wp_spider_faq_question |
wp_spider_faq_category |
wp_post_right_content |
New WordPress options |
---|
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
Checking browser requirements for SpiderFAQ
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,953 ▲192 | 13.69 ▼0.96 | 11.02 ▲9.33 | 37.87 ▼6.06 |
Dashboard /wp-admin | 2,234 ▲60 | 5.69 ▲0.10 | 86.95 ▼12.95 | 78.63 ▲36.11 |
Posts /wp-admin/edit.php | 2,174 ▲77 | 2.28 ▲0.31 | 42.94 ▲4.04 | 37.41 ▲1.15 |
Add New Post /wp-admin/post-new.php | 6,373 ▲4,841 | 24.99 ▲1.93 | 913.36 ▲200.70 | 86.74 ▲30.37 |
Media Library /wp-admin/upload.php | 1,461 ▲61 | 4.39 ▲0.15 | 115.49 ▼2.31 | 78.09 ▲29.06 |
Uninstall Spider FAQ /wp-admin/admin.php?page=Uninstall_Spider_FAQ | 927 | 1.92 | 27.21 | 27.57 |
Featured Plugins /wp-admin/admin.php?page=Spider_Faq_featured_plugins | 1,085 | 1.92 | 25.86 | 34.51 |
Licensing /wp-admin/admin.php?page=Spider_FAQ_Licensing | 888 | 1.92 | 27.33 | 26.25 |
Questions /wp-admin/admin.php?page=Spider_Faq_Questions | 1,008 | 1.89 | 29.34 | 38.26 |
Themes /wp-admin/admin.php?page=Spider_Faq_Themes | 895 | 1.92 | 26.94 | 29.72 |
Categories /wp-admin/admin.php?page=Spider_Faq_Categories | 1,015 | 1.94 | 25.71 | 27.85 |
FAQs /wp-admin/admin.php?page=Spider_Faq | 975 | 1.92 | 24.86 | 28.97 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.03MB] 50% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- The uninstall procedure failed, leaving 5 tables in the database
- wp_spider_faq_faq
- wp_spider_faq_question
- wp_post_right_content
- wp_spider_faq_category
- wp_spider_faq_theme
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though no errors were found, this is by no means an exhaustive test
SRP 0% 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
- 4× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/spider-faq/spider_faq_category_functions.html.php
- > /wp-content/plugins/spider-faq/spider_faq_question_functions.html.php
- > /wp-content/plugins/spider-faq/spider_faq_theme_functions.html.php
- > /wp-content/plugins/spider-faq/spider_faq_functions.html.php
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/spider-faq/faq.php:11
- > 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 96% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
No tags were found
spider-faq/faq.php 92% from 13 tests
The main PHP file in "SpiderFAQ" ver. 1.3.2 adds more information about the plugin and also serves as the entry point for this plugin
You should first fix the following items:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("spider-faq.php" instead of "faq.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin18,818 lines of code in 77 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 2,047 | 126 | 9,610 |
JavaScript | 10 | 442 | 388 | 4,940 |
CSS | 7 | 649 | 149 | 3,083 |
PO File | 47 | 235 | 329 | 1,175 |
HTML | 2 | 3 | 0 | 10 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.49 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 78 | |
▷ Named functions | 78 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.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
51 PNG files occupy 0.52MB with 0.25MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/search-faq.png | 1.70KB | 0.88KB | ▼ 48.42% |
upload/ikon/unlike_black.png | 1.40KB | 0.56KB | ▼ 60.33% |
upload/ikon/+.png | 1.26KB | 0.31KB | ▼ 75.52% |
images/filesave.png | 0.52KB | 0.38KB | ▼ 27.31% |
images/folder_sm.png | 0.69KB | 0.51KB | ▼ 25.04% |