#speedcurve

Live, measured metrics for the hashtag #speedcurve from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #speedcurve

This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.

$23.52/ year · 10-character #name
Claim #speedcurve$23.52/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
10
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 10
0
Avg reactions / post
Mastodon · last 10

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 14:25 UTC
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 14:25 UTC

No related tags with measured usage found for #speedcurve.

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 14:25 UTC

Everything below is measured over the latest 10 public posts (spanning ~24908 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: French (6) · English (4)

Avg boosts / post: 0.8

Top of the latest posts

  • I would use @speedcurve if I could. My client allowed #WebPageTest IPs, much easier for them is seems, than checking HTTP headers from SpeedCurve. #SpeedCurve

    Nicolas Hoizey@[email protected]002025-11-21 11:46 UTCView post →
  • Real User Monitoring (RUM) lets you see how users experience your site This @speedcurve snapshot shows how perf impacts UX — only 43% of users were happy! 😬 Better perf = better UX = better results Are you tracking RUM yet? #WebPerf #UX #R

    Joan León@[email protected]022025-04-11 15:53 UTCView post →
  • Fellow @speedcurve users, is there a way to get the value of the document request’s “Request Start” somewhere in charts? Or even values for DNS Lookup, Initial Connection, TLS Negotiation? Or a way to flush network “stack” in the browser in

    Nicolas Hoizey@[email protected]002024-10-10 15:10 UTCView post →

Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/speedcurve