Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▼0.11MB] [CPU: ▼12.40ms] Passed 4 tests
Analyzing server-side resources used by LottieFiles - Lottie block for Gutenberg
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▼0.01 | 32.62 ▼22.78 |
Dashboard /wp-admin | 3.32 ▲0.02 | 45.84 ▼5.95 |
Posts /wp-admin/edit.php | 3.38 ▼0.47 | 47.25 ▼11.86 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 88.95 ▼9.00 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 33.89 ▲1.66 |
Server storage [IO: ▲17.39MB] [DB: ▲0.07MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 194 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
Checking browser requirements for LottieFiles - Lottie block for Gutenberg
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,847 ▲85 | 14.07 ▼0.09 | 3.76 ▲2.11 | 38.78 ▼10.35 |
Dashboard /wp-admin | 2,237 ▲60 | 5.24 ▼0.35 | 100.59 ▲2.05 | 42.62 ▼1.46 |
Posts /wp-admin/edit.php | 2,142 ▲42 | 2.53 ▲0.50 | 44.72 ▲3.17 | 35.53 ▲0.50 |
Add New Post /wp-admin/post-new.php | 6,326 ▲4,795 | 30.34 ▲7.44 | 1,081.34 ▲460.71 | 43.63 ▼5.73 |
Media Library /wp-admin/upload.php | 1,442 ▲42 | 4.83 ▲0.64 | 98.25 ▼11.66 | 41.45 ▼7.68 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- widget_recent-posts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Even though everything seems fine, this is not an exhaustive test
SRP 50% 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
- 2× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/lottiefiles/src/common.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/lottiefiles/src/admin/settings/init.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
5 plugin tags: animations, lottie, animation, bodymovin, gutenberg
lottiefiles/host.php 92% from 13 tests
The main PHP script in "LottieFiles - Lottie block for Gutenberg" version 2.7.0 is automatically included on every request by WordPress
It is important to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("lottiefiles.php" instead of "host.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected139,513 lines of code in 186 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 8 | 31,253 | 10 | 108,483 |
YAML | 1 | 1,921 | 0 | 13,717 |
TypeScript | 145 | 1,004 | 735 | 12,110 |
JSON | 4 | 0 | 0 | 3,593 |
JavaScript | 11 | 61 | 27 | 1,052 |
PHP | 12 | 54 | 82 | 292 |
Sass | 3 | 17 | 0 | 180 |
Markdown | 2 | 61 | 0 | 86 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.24 |
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 | 19 | |
▷ Named functions | 14 | 73.68% |
▷ Anonymous functions | 5 | 26.32% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.15MB with 0.09MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
src/assets/images/update.png | 13.89KB | 6.05KB | ▼ 56.43% |
src/assets/images/upsell.png | 70.69KB | 27.72KB | ▼ 60.79% |
build/images/upsell.18ec1514.png | 70.69KB | 27.72KB | ▼ 60.79% |