Back to @FirefoxWebDevs's profile

Firefox for Web Developers engagement report

@FirefoxWebDevs - 90K followers on X

Measured over 6 original posts from a 30-day window, last computed on September 23, 2026.

Engagement

Per follower
0.159%
of 90K followers
Per impression
1.94%
7.4K views on a typical post
Reach
8.21%
of its followers see a post
Typical post
144
interactions (median)
Saved
0.121%
9 bookmarks on a typical post
Posting rate
0.33/day
active 23% of days
Peak time
13:00 UTC
Tuesday

Early reading. We have captured 6 original posts for this account, below the 8 we require before treating a median as settled. The numbers above describe what we have seen so far, not a finished profile of the account.

A typical post picks up 144 interactions against 90K followers, an engagement rate of 0.159%. Posts are seen about 7.4K times each, and 1.94% of those impressions turn into an interaction. That is about 8.21% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.33 posts a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 13:00 UTC, and Tuesday is the busiest day of the week. Of the 6 posts sampled, 33% carry an image or video, 33% are part of a thread and 67% link out. The account's strongest tracked post pulled 413 interactions, about 2.9x its own typical post. Only 6 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.

Measured over 6 original posts from a 30-day window, last computed on September 23, 2026.

Where this sits in the catalog

At 0.159%, Firefox for Web Developers sits above the 50th percentile of the 212,656 accounts in this comparison. That places it in the above the median band, which runs 0.146% to 0.697%.

p100.004%
p250.025%
p50 (median)0.146%
p750.697%
p902.61%
p9982.9%
Engagement rate as a share of followers, across the 212,656 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 22,418 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.004%
25th percentile0.025%
50th percentile0.146%
75th percentile0.697%
90th percentile2.61%
99th percentile82.9%

This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built

Posting timing

This account posts most often around 13:00 UTC, and Tuesday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 13:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 13:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
00:00 UTC-1%89K
01:00 UTC-2%90K
02:00 UTC-3%88K
03:00 UTC-4%94K
04:00 UTC-5%76K
05:00 UTC-4%75K
06:00 UTC-5%86K
07:00 UTC-5%93K
08:00 UTC-4%108K
09:00 UTC-4%124K
10:00 UTC-3%129K
11:00 UTC-3%141K
12:00 UTC-3%154K
13:00 UTC-3%167K
14:00 UTC-4%173K
15:00 UTC-2%176K
16:00 UTC-3%171K
17:00 UTC-3%159K
18:00 UTC-2%149K
19:00 UTC-2%141K
20:00 UTC-1%131K
21:00 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Tuesday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Tuesday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

Formats this account uses

Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video33% of posts+111%+108% to +115%34K
Outbound link67% of posts-41%-42% to -40%32K
Typical length--3%-3% to -2%54K
  • 33% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
  • 67% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
  • Its average post runs 151 characters, which falls in the 80 - 180 characters band. Across the catalog, posts of 80 to 180 characters run 3% below the same accounts' other posts.

These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.

Best tweets

  • Aug 24, 20262.9x their median

    Intent to ship: JPEG XL! This will be on-by-default in Firefox 157, which should become the main release version at the end of September. This includes key JPEG XL features like progressive rendering. https://t.co/pLqTFFVVnf

    354457719K viewsView on X
  • Sep 1, 20262.5x their median

    Major versions of Firefox now land every two weeks, so Firefox 155 dropped today with web platform features including: 🎉 Fully typed CSS attr() 🎉 CSS progress() 🎉 Promise.allKeyed() and allSettledKeyed() 🎉 Lots of new WebTransport stuff …And more! https://t.co/zGtRtYX1uk

    294537424K viewsView on X
  • Apr 1, 20264.0x their median

    Can you tell CSS from BS? Can you beat my score? https://t.co/du1ZwdzEYM https://t.co/lcdl1MwbAI

    315254137K viewsView on X
  • Apr 23, 20262.1x their median

    sizes="auto" landed in Firefox 150, making responsive images simpler and more reliable. Here's when you can use it, and how… https://t.co/5tSvSovsD1

    244429222K viewsView on X
  • Dec 15, 20252.0x their median

    JavaScript declarations in conditionals was discussed at TC39 recently, but consensus broke down over one key detail. How do you think it should behave? https://t.co/F5JGG0Kgmb

    2282130234K viewsView on X
  • Apr 21, 20261.9x their median

    Firefox 150 just landed & includes new web platform features like: 🎉 sizes="auto" on images 🎉 light-dark() image support 🎉 CSS revert-rule 🎉 ariaNotify() 🎉 Media pseudo-classes like :playing None of these are baseline yet, so check MDN for support https://t.co/pQ04X68nrY

    220497225K viewsView on X
  • Sep 8, 20261.7x their median

    The CSS progress() function is now in all major engines! Here's how it works: https://t.co/6xyHedRo2F

    226156310K viewsView on X
  • Apr 30, 20261.6x their median

    Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API. We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent. Full details: https://t.co/fAmHANzAjU

    1833610721K viewsView on X
  • Aug 24, 2026

    JPEG XL is slated to ship in Firefox 157 next month! Here's how we're shipping it safely… https://t.co/WwOkRf5cUP

    152343713K viewsView on X
  • Apr 27, 2026

    CSS's light-dark() now accepts images, making it simpler to define alternate values for a dark color scheme. Here's how it works: https://t.co/lGibGHAiN6

    136173320K viewsView on X

Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.

Buy or sell Twitter (X) accounts - escrow-protected

PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.

Reading these numbers

A typical post picks up 144 interactions against 90K followers, an engagement rate of 0.159%. Posts are seen about 7.4K times each, and 1.94% of those impressions turn into an interaction. That is about 8.21% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.33 posts a day over the last 30 days, though only 23% of days saw any activity at all. Most posts go out around 13:00 UTC, and Tuesday is the busiest day of the week. Of the 6 posts sampled, 33% carry an image or video, 33% are part of a thread and 67% link out. The account's strongest tracked post pulled 413 interactions, about 2.9x its own typical post. Only 6 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.

What is Firefox for Web Developers's engagement rate on X?
Firefox for Web Developers (@FirefoxWebDevs) has an engagement rate of 0.159%, based on the median interactions across 6 original posts from the last 30 days against 90,198 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.159%, Firefox for Web Developers sits above the 50th percentile of the 212,656 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
Does @FirefoxWebDevs have real engagement?
There is not yet enough sample to rank this account against others of its size.
When does @FirefoxWebDevs post?
Most posts go out around 13:00 UTC, and Tuesday is its busiest day, at roughly 0.33 posts per day across the measured window.

Keep going