Loading video...
Video Failed to Load
Just launched an autoresearch loop for speeding up your frontend. I spent ~$10k in fable api credits speeding up the top 200 github repos, took the learnings and tracked the most common wins. The loop iterates through them to find speedups.
54,527 views • 10 days ago •via X (Twitter)
15 Comments

Oh also, it ties into your current claude/codex/cursor subs, so it's free to use. Give it a shot: npx makefaster

The interesting part is turning a pile of one-off frontend wins into a repeatable search loop. The benchmark matters too. Speedups that survive across 200 repos are a much better signal than a polished demo.

Also I made a Show HN for this:

@sheherenow_ Legend!!! Ty for your service sir

@sheherenow_ Only a legend if it works - give it a shot and report back 🙏

Great info to know.

Love this idea. We thank you for your credit burn. Is it looped over Core Web Vitals?

Lighthouse score was the metric I was using. Core web vitals are user-submitted scores, which can't really be automated easily. They measure roughly the same thing though - LCP/TTI/etc, so this should have a measurable impact on your CWV score.

Ohhh, I'm not sure I realized that CWV was only live users.

he’s at it again 😮💨

I'm just out here makin' shit I want to use :)

THANK u!! I will use this!!!

The real product here might be that common wins dataset you built along the way, not the tool.

It 100% is. It's why I also let you optionally submit your own stats/thinking traces - ideally building up the db over time will continue to make this better.

$10k testing real repos is a much better moat than another performance checklist

