Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.35MB] [CPU: ▲2.58ms] Passed 4 tests
A check of server-side resources used by Algolia for WordPress
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.80 ▲0.34 | 41.07 ▲5.09 |
Dashboard /wp-admin | 3.69 ▲0.39 | 47.31 ▼1.79 |
Posts /wp-admin/edit.php | 3.74 ▲0.39 | 48.73 ▲3.42 |
Add New Post /wp-admin/post-new.php | 6.23 ▲0.34 | 89.91 ▲3.60 |
Media Library /wp-admin/upload.php | 3.55 ▲0.32 | 37.15 ▲5.74 |
Algolia /wp-admin/options-general.php?page=algolia | 3.52 | 32.92 |
Server storage [IO: ▲1.54MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 253 new files
Database: no new tables, 13 new options
New WordPress options |
---|
widget_recent-posts |
theysaidso_admin_options |
can_compress_scripts |
algolia_synced_indices_ids |
algolia_override_native_search |
algolia_api_is_reachable |
algolia_api_key |
db_upgraded |
algolia_search_api_key |
widget_theysaidso_widget |
... |
Browser metrics Passed 4 tests
Algolia for WordPress: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,806 ▲71 | 13.28 ▼1.09 | 4.58 ▲2.99 | 42.10 ▲0.82 |
Dashboard /wp-admin | 2,212 ▲24 | 4.89 ▼1.02 | 104.26 ▲0.81 | 38.74 ▼6.69 |
Posts /wp-admin/edit.php | 2,098 ▲9 | 2.04 ▼0.08 | 39.60 ▼2.76 | 35.07 ▼1.26 |
Add New Post /wp-admin/post-new.php | 1,536 ▼6 | 23.26 ▲5.29 | 676.47 ▲46.64 | 53.79 ▲3.48 |
Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.21 ▲0.01 | 97.90 ▼4.76 | 41.14 ▼2.86 |
Algolia /wp-admin/options-general.php?page=algolia | 878 | 2.07 | 22.89 | 27.29 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Zombie WordPress options detected upon uninstall: 13 options
- algolia_api_key
- widget_recent-posts
- widget_theysaidso_widget
- algolia_search_api_key
- algolia_application_id
- can_compress_scripts
- algolia_api_is_reachable
- algolia_index_name_prefix
- db_upgraded
- theysaidso_admin_options
- ...
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Good news, no errors were detected
SRP 50% 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
- 103× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/wp-algolia/vendor/guzzlehttp/psr7/src/Stream.php:12
- > PHP Fatal error
Uncaught Error: Class 'WP_CLI_Command' not found in wp-content/plugins/wp-algolia/src/class-algolia-cli.php:3
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/wp-algolia/vendor/guzzlehttp/psr7/src/BufferStream.php:17
- > PHP Fatal error
Uncaught Error: Class 'GuzzleHttp\\Exception\\RequestException' not found in wp-content/plugins/wp-algolia/vendor/guzzlehttp/guzzle/src/Exception/BadResponseException.php:11
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/wp-algolia/vendor/guzzlehttp/guzzle/src/Pool.php:24
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\MessageInterface' not found in wp-content/plugins/wp-algolia/vendor/psr/http-message/src/ResponseInterface.php:20
- > PHP Fatal error
Uncaught Error: Class 'Algolia\\AlgoliaSearch\\Response\\AbstractResponse' not found in wp-content/plugins/wp-algolia/vendor/algolia/algoliasearch-client-php/src/Response/RestoreApiKeyResponse.php:9
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/wp-algolia/vendor/guzzlehttp/promises/src/EachPromise.php:9
- > PHP Fatal error
Uncaught Error: Interface 'Algolia\\AlgoliaSearch\\Http\\HttpClientInterface' not found in wp-content/plugins/wp-algolia/vendor/algolia/algoliasearch-client-php/src/Http/CurlHttpClient.php:8
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/wp-algolia/vendor/guzzlehttp/psr7/src/InflateStream.php:20
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
5 plugin tags: search, relevant search, better search, algolia, custom search
wp-algolia/wp-algolia.php Passed 13 tests
The principal PHP file in "Algolia for WordPress" v. 3.1.2 is loaded by WordPress automatically on each request
66 characters long description:
A (unofficial) WordPress plugin to use Algolia as a search engine.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
There were no executable files found in this plugin19,320 lines of code in 232 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 222 | 3,882 | 8,957 | 17,256 |
Markdown | 3 | 247 | 0 | 1,030 |
JSON | 1 | 0 | 0 | 793 |
YAML | 2 | 18 | 14 | 131 |
JavaScript | 1 | 16 | 0 | 75 |
XML | 1 | 8 | 6 | 14 |
Dockerfile | 1 | 4 | 2 | 12 |
make | 1 | 4 | 0 | 9 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 10.59 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 88.00 |
Average method complexity | 2.35 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 26.00 |
Code structure | ||
---|---|---|
Namespaces | 26 | |
Interfaces | 34 | |
Traits | 5 | |
Classes | 168 | |
▷ Abstract classes | 7 | 4.17% |
▷ Concrete classes | 161 | 95.83% |
▷ Final classes | 86 | 53.42% |
Methods | 1,485 | |
▷ Static methods | 211 | 14.21% |
▷ Public methods | 1,253 | 84.38% |
▷ Protected methods | 63 | 4.24% |
▷ Private methods | 169 | 11.38% |
Functions | 152 | |
▷ Named functions | 37 | 24.34% |
▷ Anonymous functions | 115 | 75.66% |
Constants | 81 | |
▷ Global constants | 1 | 1.23% |
▷ Class constants | 80 | 98.77% |
▷ Public constants | 69 | 86.25% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
5 PNG files occupy 0.54MB with 0.34MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
.wordpress-org/banner-1544x500.png | 304.90KB | 66.00KB | ▼ 78.35% |
.wordpress-org/banner-772x250.png | 90.15KB | 22.05KB | ▼ 75.54% |
.wordpress-org/icon-128x128.png | 17.04KB | 8.35KB | ▼ 51.01% |
.wordpress-org/screenshot-1.png | 78.05KB | 44.21KB | ▼ 43.36% |
.wordpress-org/icon-256x256.png | 59.78KB | 20.49KB | ▼ 65.73% |