Site loading too slow? PafCore spots which file drags you down. Get a private report with fixes in under a minute. Find the culprit now at pafcore.site
We go again today ☕️
Wrangling... Simmering... Mulling... Brewing... Marinating... Combobulating... Flibbertigibbeting... Clauding...
what else did i miss 👀
List it. 📢 That was the whole advice.
So I did. 🙃 This is what came back. 📋 My referrers for @PafCore in the last 30 days.
Which one would you do more of 👀 and which one would you drop? 🗑️
WEEK #15 of listing startups on @afro_launch - a platform that helps African startups get discovered.
These startups are already on the leaderboard for this week:
• @pafcore
• @asusuoma
🌍 Only 07h 29m 27s left to vote for your favourite African startups!
Cast your vote now on Afrolaunch → afrolaunch.com
One thing I’ve really improved on recently since I started working on @PafCore is how I look at web app performance.
My domain knowledge in that area has grown a lot 🚀📈💻
The Indie Hackers thread has been enough fuel for now.
Good feedback. Real sites. Clear asks.
That is all I need to keep building @PafCore .
indiehackers.com/post/i-buil…
That’s the gap. @pafcore names the actual slow file and shows how far the score moves on its own, so you can tell a real fix from noise, plus it watches the page for outages.
Building @PafCore which finds what is slowing your site, down to the file, and proves the fix worked.
It also watches the site and alerts you if it goes down.
Most sites feel slow for one reason. Images. Not your framework. Not your hosting.
Unoptimized pictures eat bandwidth and delay first paint.
Serve the right size. A 4000px photo in a 400px card wastes data.
Use srcset and sizes so the browser picks a smaller file. Compress with WebP or AVIF.
Lazy load images below the fold. Do not download what the user cannot see yet.
The native loading lazy attribute does this with almost no extra code.
After you ship measure it. Check Largest Contentful Paint.
If it sits above 2.5 seconds people feel the wait. Fix the hero image first.
It’s the weekend.
Are you shipping or are you resting? 😌
If your site is also taking a break, drop the URL.
PafCore will tell you which file is slowing it down.
Free. No signup.
I’m shipping a little. What about you? 🚀
Shipped this week in @PafCore .
1. You can now measure the page behind your login. The dashboard, the account page, the one that's actually slow and that nobody ever tests.
One session, encrypted, sent only to that host, deleted the second you revoke it.
Builders on Indie Hackers tried the free report on real sites.
“H1 finding was accurate. Fixed all three.”
“Quiet gap is the best feature on the page.”
“Clients stop chasing the number and ask about the file.”
Free. Names the slow file.
pafcore.site
Pro Watch is live.
Catch the drop before your client does.
Daily or hourly checks. Score history. Alerts when the number moves.
Same quiet engine that names the slow file.
→ pafcore.site/pro
Decided to make a product video for @PafCore today 👨🍳
Tried remotion for the first time. took me way longer than i thought.
26 seconds, wide, vertical and square, with sound.
Rate my cooking 🔥 or 💀
Numbers in it are real. Pagespeed said 71. I ran it six times and got 50.
pafcore.site