Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
These installer errors require your attention
- Install procedure validation failed for this plugin
- > Warning in wp-content/plugins/redisearch/vendor/predis/predis/src/Connection/StreamConnection.php+127
stream_socket_client(): unable to connect to tcp://127.0.0.1:6379 (Connection refused)
Server metrics [RAM: ▼1.53MB] [CPU: ▼49.00ms] Passed 4 tests
An overview of server-side resources used by RediSearch
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.46 ▼1.01 | 11.31 ▼31.36 |
Dashboard /wp-admin | 2.48 ▼0.83 | 20.04 ▼33.45 |
Posts /wp-admin/edit.php | 2.48 ▼0.88 | 12.13 ▼38.43 |
Add New Post /wp-admin/post-new.php | 2.48 ▼3.41 | 12.71 ▼92.76 |
Media Library /wp-admin/upload.php | 2.48 ▼0.75 | 12.66 ▼22.66 |
Indexing options /wp-admin/admin.php?page=indexing-options | 2.48 | 12.22 |
Redis server /wp-admin/admin.php?page=redis-server | 2.48 | 13.73 |
Redisearch /wp-admin/admin.php?page=redisearch | 2.48 | 13.33 |
Server storage [IO: ▲1.30MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 414 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for RediSearch
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,841 ▲80 | 14.29 ▲0.06 | 1.95 ▲0.27 | 46.05 ▲0.20 |
Dashboard /wp-admin | 2,247 ▲70 | 5.68 ▲0.11 | 93.22 ▲7.23 | 45.77 ▲2.21 |
Posts /wp-admin/edit.php | 2,153 ▲56 | 2.19 ▲0.15 | 37.63 ▼1.27 | 41.49 ▲9.46 |
Add New Post /wp-admin/post-new.php | 1,568 ▲28 | 23.59 ▲0.45 | 683.80 ▼4.37 | 53.98 ▼2.85 |
Media Library /wp-admin/upload.php | 1,455 ▲52 | 4.28 ▲0.00 | 100.46 ▼1.80 | 43.81 ▼1.77 |
Indexing options /wp-admin/admin.php?page=indexing-options | 1,143 | 2.21 | 27.76 | 43.33 |
Redis server /wp-admin/admin.php?page=redis-server | 966 | 2.21 | 23.81 | 30.61 |
Redisearch /wp-admin/admin.php?page=redisearch | 892 | 2.06 | 27.40 | 29.67 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- Uninstall procedure validation failed for this plugin
- > Warning in wp-content/plugins/redisearch/vendor/predis/predis/src/Connection/StreamConnection.php+127
stream_socket_client(): unable to connect to tcp://127.0.0.1:6379 (Connection refused)
- Zombie WordPress options detected upon uninstall: 6 options
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Smoke test failed, please fix the following
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=redisearch
- > Warning in wp-content/plugins/redisearch/vendor/predis/predis/src/Connection/StreamConnection.php+127
stream_socket_client(): unable to connect to tcp://127.0.0.1:6379 (Connection refused)
- > GET request to /wp-admin/admin.php?page=indexing-options
- > Deprecated in wp-content/plugins/redisearch/src/Admin/Admin.php+169
Non-static method WpRediSearch\Admin::supportedLanguages() should not be called statically
SRP 0% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following
- 16× PHP files output text when accessed directly (only 10 are shown):
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/session_handler.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/key_prefixing.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/lua_scripting_abstraction.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/custom_cluster_distributor.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/redis_collections_iterators.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/dispatcher_loop.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/replication_sentinel.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/monitor_consumer.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/replication_simple.php
- > /wp-content/plugins/redisearch/vendor/predis/predis/examples/executing_redis_commands.php
- 280× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Predis\\Command\\Command' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Command/StringBitCount.php:19
- > PHP Fatal error
Uncaught Error: Interface 'Predis\\Configuration\\OptionsInterface' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Configuration/Options.php:22
- > PHP Fatal error
Uncaught Error: Class 'Predis\\Command\\Command' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Command/ListPopFirst.php:19
- > PHP Fatal error
Uncaught Error: Class 'Predis\\Command\\Command' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Command/SetMembers.php:19
- > PHP Fatal error
Uncaught Error: Class 'Predis\\Command\\Command' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Command/ServerCommand.php:19
- > PHP Fatal error
Uncaught Error: Interface 'Predis\\Cluster\\StrategyInterface' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Cluster/ClusterStrategy.php:22
- > PHP Fatal error
Uncaught Error: Class 'Predis\\Command\\Command' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Command/ZSetScore.php:19
- > PHP Fatal error
Uncaught Error: Class 'Predis\\Command\\Command' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Command/StringDecrement.php:19
- > PHP Fatal error
Uncaught Error: Class 'Predis\\Command\\Command' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Command/StringSetRange.php:19
- > PHP Fatal error
Uncaught Error: Interface 'Predis\\Connection\\ConnectionInterface' not found in wp-content/plugins/redisearch/vendor/predis/predis/src/Connection/AggregateConnectionInterface.php:22
- > 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 errors were detected
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
10 plugin tags: searching, advanced search, fuzzy, suggest, aggregation...
redisearch/wp-redisearch.php 92% from 13 tests
The primary PHP file in "RediSearch" version 0.3.4 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("redisearch.php" instead of "wp-redisearch.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
No dangerous file extensions were detected20,895 lines of code in 398 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 367 | 4,762 | 12,994 | 17,619 |
Markdown | 10 | 782 | 0 | 2,308 |
JSON | 7 | 1 | 0 | 503 |
CSS | 3 | 10 | 4 | 155 |
XML | 4 | 13 | 12 | 109 |
JavaScript | 3 | 3 | 1 | 91 |
YAML | 1 | 0 | 0 | 48 |
Bourne Shell | 2 | 9 | 0 | 38 |
INI | 1 | 6 | 6 | 24 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.33 |
Average class complexity | 5.88 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 100.00 |
Average method complexity | 2.16 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 26.00 |
Code structure | ||
---|---|---|
Namespaces | 41 | |
Interfaces | 29 | |
Traits | 2 | |
Classes | 308 | |
▷ Abstract classes | 16 | 5.19% |
▷ Concrete classes | 292 | 94.81% |
▷ Final classes | 1 | 0.34% |
Methods | 1,491 | |
▷ Static methods | 99 | 6.64% |
▷ Public methods | 1,219 | 81.76% |
▷ Protected methods | 214 | 14.35% |
▷ Private methods | 58 | 3.89% |
Functions | 39 | |
▷ Named functions | 3 | 7.69% |
▷ Anonymous functions | 36 | 92.31% |
Constants | 36 | |
▷ Global constants | 12 | 33.33% |
▷ Class constants | 24 | 66.67% |
▷ Public constants | 21 | 87.50% |
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
No PNG images were found in this plugin