Reading works standing still but not in passing
A read takes time. The tag powers up, is selected, and transfers its content, and a brush across it can end before that finishes. Larger content lengthens the window, which is why the fix is usually shorter content rather than a different tag.
What happens during a tap
The phone produces a field. The tag powers up from it. The phone selects the tag and asks where its content is. The tag answers. The phone reads the content.
Each step needs the two to stay coupled. Break the coupling partway and the exchange is abandoned, and the phone reports nothing rather than reporting a partial read.
So a failed brush is not a weak read, it is an interrupted one. That is why it produces silence rather than an error.
Content size sets the duration
Data crosses the interface at a fixed rate, so ten times the content takes roughly ten times as long.
A short web address is fast enough to feel instantaneous. A contact card written directly to the tag is noticeably longer, and long enough that the phone must be held rather than brushed.
The chip does not change this. Two compliant tags carrying the same message read in about the same time, so paying more does not shorten the window.
Why it fails in public and not in testing
Whoever tested the deployment knew where the antenna was and held the phone still. That is not the gesture a stranger uses.
People tap the way they tap a payment terminal, which is a brief touch, and payment exchanges are short by design.
So a tag holding a large message passes every internal test and fails a proportion of real attempts. The failure rate is invisible until the tags are in public.
Test by asking someone who has never seen the tag to use it, and watch how long they hold the phone there.
Shortening the window
Write a link rather than a payload. A short address reads fast enough that nobody needs to hold still, and it moves everything else to a page you control.
Trim what you do write. Every field of a contact card written directly adds time the phone must stay in place.
Use a larger tag, which forgives an approximate position and keeps the coupling through small movements.
And print an instruction if the content genuinely has to be large. "Hold for a second" is a cheap fix for a problem that otherwise looks like a broken tag.
Frequently asked questions
How long does a tap need?
A short address is close to instantaneous, and a large message needs a deliberate pause. If people are failing, the content is usually larger than it needs to be.
Would a better chip read faster?
No. The rate is set by the link rather than the chip, so the same message takes about the same time on any compliant tag.
Why do I get no error, just nothing?
Because an interrupted exchange is abandoned rather than reported. The phone has nothing complete to act on, so it stays silent.
Does a bigger tag make the read faster?
It does not change the rate, and it keeps the coupling through small movements, which makes a brief tap more likely to succeed.