Cite official js-framework-benchmark in FAQ

Author: dy

index.md

@@ -301,7 +301,7 @@ document.querySelectorAll('.ref-list pre').forEach(p => p.innerHTML = hl(p.textC
 ## FAQ
 
 **How does it compare?**
-: Sprae is ~1.5× smaller over the wire, ~2.3× faster, and uses ~3× less runtime memory than Alpine in [this benchmark](./compare). See the [Alpine migration guide](./alpine).
+: Sprae is ~1.5× smaller, ~2.3× faster, and uses ~3× less runtime memory than Alpine in [this benchmark](./compare). In the official [js-framework-benchmark](https://krausest.github.io/js-framework-benchmark/current.html) (Chrome 150) it places ahead of Vue, Preact and React in CPU speed. See the [Alpine migration guide](./alpine).
 
 **Strict CSP? Browser extension?**
 : The [CSP build](./csp) interprets JavaScript expressions without `eval` or `new Function`. Bundle it locally for Chrome MV3 extensions. It supports arrow functions, unlike Alpine's CSP build.

readme.md

@@ -516,10 +516,10 @@ Works with [define-element](https://github.com/dy/define-element), Lit, or any C
 ## FAQ
 
 **How does it compare to Alpine?**<br>
-Sprae is ~1.5× smaller over the wire, ~2.3× faster, and uses ~3× less runtime memory in [this comparison](https://dy.github.io/sprae/compare). It has pluggable signals, built-in modifiers, event chains, and a full-JS [CSP build](https://dy.github.io/sprae/csp).
+Sprae is ~1.5× smaller, ~2.3× faster, and uses ~3× less runtime memory in [this comparison](https://dy.github.io/sprae/compare). It has pluggable signals, built-in modifiers, event chains, and a full-JS [CSP build](https://dy.github.io/sprae/csp).
 
 **How does it compare to React/Vue?**<br>
-Sprae needs no build step or virtual DOM. In [JSX](#jsx--nextjs), it adds client-side interactivity without `'use client'`.
+In the official [js-framework-benchmark](https://krausest.github.io/js-framework-benchmark/current.html) (Chrome 150), sprae places ahead of Vue, Preact and React in CPU speed, at 10kb compressed, with no build step or virtual DOM. In [JSX](#jsx--nextjs), it adds client-side interactivity without `'use client'`.
 
 **Why signals?**<br>
 Signals have a [TC39 proposal](https://github.com/tc39/proposal-signals), and sprae accepts any Preact Signals-compatible implementation.