The comments are more or less correct; caching applies to the /events endpoint just like every other method.
This is by design for now. We have looked at differing caching policies for /events and /inbox/* routes, as the minute lag on those methods is a bit heavy handed; though we still need to protect ourselves from abusive requests.
There seem to be 2 or 3 effects, the biggest is that the Tags page also shows Synonyms.
There may also be a small cache effect, but there seems to be another discrepancy as well, possibly an error/bug.
You can see that the Tags page also shows Synonyms by:
Go to the Tags page.
Enter userscr in the Type to find tags: box.
You will see something like: