Skip to Content
ChangelogThe embedded lead form stays fast under a flood of junk traffic

The embedded lead form stays fast under a flood of junk traffic

The form vendors embed on their own site refuses obvious rubbish cheaply — a bot that fills the hidden field, a malformed submission, a failed CAPTCHA — and keeps a record of every attempt so a vendor can see what has been arriving.

Its rate limits are counted from that record. Until now the count worked through the whole record to find the submissions that actually count, which meant the busier a form got with junk, the longer the check took — for every genuine visitor as well. The count now reads only the submissions it counts, so the form’s speed no longer depends on how much noise it has received.

Nothing about the limits themselves has changed: the same submissions count towards them, at the same allowances, and a visitor who was let through before is let through now.

Last updated on