-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Performance] Load reCaptcha on focus to input to improve page load times #38303
Comments
Hi @Bashev. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
@magento i am working on this |
Fixed in magento/security-package#334 |
Re invisible reCaptcha v3 - the way this technology works is it tracks the user behaviour through the website to establish if it is real user or a bot. It is supposed to be included on all pages, not loaded after a form is interacted with, see documentation - https://developers.google.com/recaptcha/docs/v3 |
@engcom-Hotel you move it to feature request backlog, but it's already fixed with this PR (in security package) magento/security-package#334 How can be moved forward? |
Hello @Bashev, I think it is due to the migration of the project from the classic to the new one. Don't worry whenever your PR will merged we will close this issue. Thanks |
Description
If reCaptcha is enabled, this few additional JS files are loaded automatically with the page loading. This reflects to the page speed of the site and of course, increase time to complete loading.
These files are external for the system and this also reflects to pagesspeed. They cannot be merged or bundled. This are 26 additional requests which comes with recaptcha loading.
Expected behavior
Load recaptcha related files (and entire library) to be loaded only if is required and have forms to which need to be applied.
Benefits
Reduce loading time, increase page speed of the site (Google Page Speed).
Additional information
No response
Release note
No response
The text was updated successfully, but these errors were encountered: