Back to @laravel's profile

Laravel engagement report

@laravel - 178K followers on X

Measured over 14 original posts from a 30-day window, last computed on October 17, 2026.

Engagement

Middle of its size range
Per follower
0.026%
of 178K followers
Per impression
0.668%
6.8K views on a typical post
Reach
3.83%
of its followers see a post
Typical post
46
interactions (median)
Saved
0.125%
8 bookmarks on a typical post
Posting rate
0.73/day
active 37% of days
Peak time
18:00 UTC
Tuesday

A typical post picks up 46 interactions against 178K followers, an engagement rate of 0.026%. Measured over 14 original posts, its engagement rate beats 36% of 20,444 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 6.8K times each, and 0.668% of those impressions turn into an interaction. That is about 3.82% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.73 post a day over the last 30 days, though only 37% of days saw any activity at all. Most posts go out around 18:00 UTC, and Tuesday is the busiest day of the week. Of the 14 posts sampled, 50% carry an image or video, 7% are part of a thread and 93% link out. The account's strongest tracked post pulled 681 interactions, about 15x its own typical post.

Measured over 14 original posts from a 30-day window, last computed on October 17, 2026.

Compared with accounts its own size

Laravel's engagement rate beats 36% of the tracked X accounts closest to it in follower count (20,444 accounts, accounts of similar size (decile 9 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.

On engagement per impression rather than per follower it beats 32% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.

Where this sits in the catalog

At 0.026%, Laravel sits above the 25th percentile of the 205,991 accounts in this comparison. That places it in the below the median band, which runs 0.024% to 0.143%.

p100.004%
p250.024%
p50 (median)0.143%
p750.68%
p902.56%
p9982.4%
Engagement rate as a share of followers, across the 205,991 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 22,893 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.024%
50th percentile0.143%
75th percentile0.68%
90th percentile2.56%
99th percentile82.4%

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 18: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: 18:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 18: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 video50% of posts+111%+108% to +115%34K
Outbound link93% of posts-41%-42% to -40%32K
Typical length-no effect-2% to -1%42K
  • 50% 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.
  • 93% 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 244 characters, which falls in the 180 - 280 characters band. Across the catalog, posts of 180 to 280 characters match the same accounts' other posts almost exactly.

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

  • Sep 15, 202615x their median

    Laravel MCP 1.0 is here 🎉 This is a big protocol upgrade with support for MCP version 2026-07-28. Stateless servers, searchable tool catalogs, caching, improved OAuth, MCP Apps updates, and a lot more. Quick thread 🧵 https://t.co/fPvr5rYoET

    58464201352K viewsView on X
  • Sep 14, 20268.7x their median

    Laravel Cloud is now ISO 27001 certified! 🎉 That's on top of SOC 2 Type II, GDPR, and HIPAA. Need our compliance certificates? Request them directly from our Trust Center → https://t.co/GFKRDrCaah https://t.co/JIlQuy4i5M

    32739211472K viewsView on X
  • Oct 15, 20264.8x their median

    Setting up transactional emails for your app is now easier than ever! Add email sending to any Laravel Cloud environment with our first-party @resend integration. Here’s how you get set up 🧵 https://t.co/Oh7tzCUUUp

    17817131217K viewsView on X
  • Jul 20, 20264.6x their median

    A few weeks ago, we launched scale-to-zero compute on Laravel Cloud. Now your MySQL database can do the same. Flex databases sleep when nothing's connected, so compute stops billing while storage stays online and your data stays exactly where you left it. Pair it with compute and Valkey caches that also scale to zero, and an idle project can sit almost free until real traffic shows up. Enable scale-to-zero on your MySQL database by choosing a Flex compute size. It kicks in automatically, and you can tune the idle timeout anywhere from 1 minute to 1 hour. Learn more → https://t.co/PAvZXZMZvw

    180199338K viewsView on X
  • Sep 21, 20262.7x their median

    This week @taylorotwell is going to deploy five backends to Laravel Cloud in about 30 minutes. Rails, Laravel, Go, Node, and Python. Databases attached, workers running. Join us this Thursday, 11:30 a.m. ET for our w̶e̶b̶i̶n̶a̶r̶ live session and bring your questions for the end! https://t.co/HBFnXVslu6

    104114529K viewsView on X
  • Aug 26, 20262.7x their median

    Let's put @xkieranbrown to work! https://t.co/yTiQayBXy7

    90524519K viewsView on X
  • Sep 25, 20262.6x their median

    Every pull request now gets a running version of your app at its own URL. Cloud builds it, sleeps it between requests, and cleans it up on merge. Fresh resources each time, so previews never point at production data. Read the docs → https://t.co/pSVTcg17Vk https://t.co/RzT80xEGuG

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

    new blog just dropped 🫡 wrote about how we’re making Laravel Boost figure those conventions out automatically and teach them to your AI agents. https://t.co/5Mzq1jCZqG

    92173417K viewsView on X
  • Aug 10, 20262.1x their median

    How do you run background jobs that scale to zero, wake in under a second, and stop paying for idle compute? Laravel Solutions Engineer @dgarbs51_ and Senior Software Engineer Kieran Brown break down the architecture behind Laravel Cloud's managed queues. Aug 18, 11 a.m. ET. Register here → https://t.co/Jf7AtGp01t

    82103111K viewsView on X
  • Jul 29, 20262.1x their median

    Your Laravel app and its Next or Nuxt frontend can now share one home. Deploy both on Laravel Cloud with one platform, one deploy workflow, and one simple bill. https://t.co/icRugqL2Wy https://t.co/97ElyEtrpT

    838229.0K 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 46 interactions against 178K followers, an engagement rate of 0.026%. Measured over 14 original posts, its engagement rate beats 36% of 20,444 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 6.8K times each, and 0.668% of those impressions turn into an interaction. That is about 3.82% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.73 post a day over the last 30 days, though only 37% of days saw any activity at all. Most posts go out around 18:00 UTC, and Tuesday is the busiest day of the week. Of the 14 posts sampled, 50% carry an image or video, 7% are part of a thread and 93% link out. The account's strongest tracked post pulled 681 interactions, about 15x its own typical post.

What is Laravel's engagement rate on X?
Laravel (@laravel) has an engagement rate of 0.026%, based on the median interactions across 14 original posts from the last 30 days against 178,449 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.026%, Laravel sits above the 25th percentile of the 205,991 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 @laravel have real engagement?
Its engagement rate beats 36% of the tracked X accounts closest to it in follower count (20,444 accounts), which puts it in the middle of its size range group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
When does @laravel post?
Most posts go out around 18:00 UTC, and Tuesday is its busiest day, at roughly 0.73 posts per day across the measured window.

Keep going