Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.20MB] [CPU: ▲3.78ms] Passed 4 tests
Server-side resources used by Landingi Landing Pages
This plugin has minimal impact on server resources
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.67 ▲0.20 | 43.46 ▲3.47 |
| Dashboard /wp-admin | 3.50 ▲0.20 | 49.03 ▲1.85 |
| Posts /wp-admin/edit.php | 3.60 ▲0.25 | 52.20 ▲7.21 |
| Add New Post /wp-admin/post-new.php | 6.08 ▲0.20 | 92.59 ▲2.87 |
| Media Library /wp-admin/upload.php | 3.42 ▲0.20 | 39.72 ▲6.92 |
| Available Landings /wp-admin/admin.php?page=landingi | 4.27 | 495.84 |
| Imported Landings /wp-admin/edit.php?post_type=landing | 3.45 | 42.81 |
| Settings /wp-admin/admin.php?page=landingi_settings | 3.64 | 34.51 |
Server storage [IO: ▲3.21MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 776 new files
Database: no new tables, 7 new options
| New WordPress options |
|---|
| widget_recent-comments |
| landingi_plugin_token |
| widget_theysaidso_widget |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Landingi Landing Pages
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,830 ▲84 | 14.47 ▲0.10 | 1.89 ▲0.27 | 44.36 ▲0.31 |
| Dashboard /wp-admin | 2,239 ▲68 | 5.82 ▲0.01 | 96.75 ▼5.97 | 80.08 ▲27.29 |
| Posts /wp-admin/edit.php | 2,116 ▲27 | 2.02 ▲0.01 | 38.71 ▲3.37 | 39.43 ▲3.28 |
| Add New Post /wp-admin/post-new.php | 1,539 ▲25 | 17.49 ▲0.04 | 702.20 ▼7.65 | 53.11 ▼10.60 |
| Media Library /wp-admin/upload.php | 1,415 ▲27 | 4.23 ▲0.03 | 95.79 ▼12.43 | 80.13 ▲34.12 |
| Available Landings /wp-admin/admin.php?page=landingi | 808 | 2.01 | 24.76 | 25.65 |
| Imported Landings /wp-admin/edit.php?post_type=landing | 1,088 | 1.93 | 32.91 | 33.17 |
| Settings /wp-admin/admin.php?page=landingi_settings | 829 | 2.03 | 24.26 | 25.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- can_compress_scripts
- landingi_plugin_token
- theysaidso_admin_options
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
These errors were triggered by the plugin
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=landingi_settings
- > Warning in wp-content/plugins/landingi-landing-pages/src/Framework/Http/Response.php+45
Cannot modify header information - headers already sent by (output started at wp-includes/script-loader.php:2838)
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please take a closer look at the following
- 329× PHP files trigger errors when accessed directly with GET requests (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/landingi-landing-pages/vendor/composer/installers/src/Composer/Installers/MantisBTInstaller.php:6
- > PHP Fatal error
Uncaught Error: Class 'Twig\ode\ode' not found in wp-content/plugins/landingi-landing-pages/vendor/twig/twig/src/Node/SandboxNode.php:21
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Client\\ClientExceptionInterface' not found in wp-content/plugins/landingi-landing-pages/vendor/guzzlehttp/guzzle/src/Exception/GuzzleException.php:7
- > PHP Fatal error
Uncaught Error: Class 'Twig\odeVisitor\\AbstractNodeVisitor' not found in wp-content/plugins/landingi-landing-pages/vendor/twig/twig/src/Profiler/NodeVisitor/ProfilerNodeVisitor.php:30
- > PHP Fatal error
Uncaught Error: Interface 'Twig\\Loader\\LoaderInterface' not found in wp-content/plugins/landingi-landing-pages/vendor/twig/twig/src/Loader/FilesystemLoader.php:22
- > PHP Fatal error
Uncaught Error: Class 'Twig\ode\\Expression\\AbstractExpression' not found in wp-content/plugins/landingi-landing-pages/vendor/twig/twig/src/Node/Expression/ConstantExpression.php:17
- > PHP Fatal error
Uncaught Error: Class 'Twig\ode\ode' not found in wp-content/plugins/landingi-landing-pages/vendor/twig/twig/src/Node/BodyNode.php:19
- > PHP Fatal error
Uncaught Error: Class 'Composer\\Installers\\BaseInstaller' not found in wp-content/plugins/landingi-landing-pages/vendor/composer/installers/src/Composer/Installers/SilverStripeInstaller.php:6
- > PHP Fatal error
Uncaught Error: Class 'Twig\ode\\Expression\\Unary\\AbstractUnary' not found in wp-content/plugins/landingi-landing-pages/vendor/twig/twig/src/Node/Expression/Unary/PosUnary.php:17
- > PHP Fatal error
Uncaught Error: Class 'Twig\ode\\Expression\\CallExpression' not found in wp-content/plugins/landingi-landing-pages/vendor/twig/twig/src/Node/Expression/FilterExpression.php:18
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
8 plugin tags: landing page, a b testing, landing page import, conversion page, landing page platform...
landingi-landing-pages/landingi-plugin.php 77% from 13 tests
Analyzing the main PHP file in "Landingi Landing Pages" version 3.0.2
Please take the time to fix the following:
- Description: The description should be shorter than 140 characters (currently 328 characters long)
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: It is recommended to name the main PHP file as the plugin slug ("landingi-landing-pages.php" instead of "landingi-plugin.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
There were no executable files found in this plugin55,919 lines of code in 702 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 657 | 6,490 | 11,596 | 50,002 |
| Markdown | 19 | 1,282 | 0 | 3,708 |
| JSON | 15 | 0 | 0 | 1,812 |
| YAML | 7 | 72 | 3 | 277 |
| Twig | 3 | 2 | 0 | 107 |
| reStructuredText | 1 | 9 | 5 | 13 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.46 |
| Average class complexity | 6.04 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 166.00 |
| Average method complexity | 2.69 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 69.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 51 | |
| Interfaces | 54 | |
| Traits | 5 | |
| Classes | 566 | |
| ▷ Abstract classes | 21 | 3.71% |
| ▷ Concrete classes | 545 | 96.29% |
| ▷ Final classes | 43 | 7.89% |
| Methods | 1,946 | |
| ▷ Static methods | 212 | 10.89% |
| ▷ Public methods | 1,615 | 82.99% |
| ▷ Protected methods | 158 | 8.12% |
| ▷ Private methods | 173 | 8.89% |
| Functions | 341 | |
| ▷ Named functions | 222 | 65.10% |
| ▷ Anonymous functions | 119 | 34.90% |
| Constants | 159 | |
| ▷ Global constants | 14 | 8.81% |
| ▷ Class constants | 145 | 91.19% |
| ▷ Public constants | 133 | 91.72% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| resources/images/landingi_logo.png | 2.29KB | 0.25KB | ▼ 88.95% |