Menu
Inclusion of Google's 'invisible recaptcha' seems to be massively increasing the 'First interactive' (and subsequently 'consistently interactive') times as measured by Lighthouse.
I set up two empty webpages using an HTML5 boilerplate template. These sites differ only by the inclusion of the recaptcha API script; namely, this line:
<script src='https://www.google.com/recaptcha/api.js'></script>
The first (non-recaptcha) site receives a first interactive time equivalent to the first meaningful paint time.
The second (recaptcha) site gets a first interactive time of ~14 seconds, and an estimated input latency time of ~1.6 seconds:
I included the script at the bottom of the <head> section as indicated in Google's instructions, however I've also tried including the script at the bottom of the <body> (as well as with async and defer) with no noticeable improvements.
Is this a problem with the way Lighthouse is measuring first interactive (especially considering it's still marked as 'beta') or Recaptcha? If the latter case, is this something to be worried about, and if so are there ways to mitigate the impact?
650
This was bothering me for some time too and this is the best solution I come up with:
You can find more information and explanation with some code examples here: https://tehnoblog.org/google-invisible-recaptcha-how-to-boost-lighthouse-performance-score/
111
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
