We Know Performance Is Lagging — Here’s What We’re Doing

By Adam
We Know Performance Is Lagging — Here’s What We’re Doing

You’ve seen the performance scores. 20s. 30s. 40s.

You’ve run PageSpeed tests. You’ve seen content load slowly.

You’re wondering: “Is this thing broken?”

Yeah — right now, it kind of is.

And that’s on us.

We’re building EazySites in public. That means we own the wins, and we take full responsibility when we drop the ball. This is one of those moments.


What’s Happening?

This isn’t a rebranded clone. We built EazySites from the ground up to serve creators, not designers, not agencies. That gives us power and focus — but right now, we’re paying the price in speed.

Simplicity on the surface takes real complexity underneath. We chose that trade-off — now we’re tuning the engine to deliver the seamless experience you signed up for.

Right now, here’s what’s slowing things down:

  • Content jumping around during page load

  • Delays in showing first content

  • Blocking resources and heavy scripts

  • Missing compression and unoptimized images

  • Inefficient loading of page assets

You’ve seen it. We’ve seen it. Now we’re fixing it.


The Plan

This is now our #1 engineering focus.

Here’s what’s happening — and when.

Weeks 1–2: Quick Wins

  • Enable file compression (text + image)

  • Resize + compress all image assets

  • Remove unused CSS and JavaScript

  • Improve browser caching

Weeks 3–4: Major Fixes

  • Eliminate layout shifts (no more content jumping)

  • Prioritise visible content first

  • Remove blocking render resources

Weeks 4–6: Full Overhaul

  • Smarter, async component loading

  • Faster frontend delivery across devices

  • Streamlined architecture for cleaner rendering

We’re also investigating the occasional ERR_TIMED_OUT in Lighthouse. Your site still loads — this appears to be an issue with how Google’s testing tool interacts with our setup. If you see that error, retest, and know it’s already on our radar.


What You Can Expect

  • ✅ Week 1–2: Faster load, compression, image optimisation

  • ✅ Week 3–4: Layout stability and visible speed gains

  • ✅ Week 4–6: Full system upgrade

  • ✅ Ongoing: Transparent updates and changelogs

Our Performance Targets:

  • 95+ scores across mobile and desktop

  • Under 1.5s time to first visible content

  • No layout shifts

  • Immediate interaction response

We’re not aiming for “better.” We’re building toward elite, fast, focused, and built for creators.


If You’re Seeing Errors…

  • Yes, the scores are low — we know.

  • No, your visitors aren’t seeing blank pages.

  • Yes, testing tools fluctuate. It’s normal to see big swings from test to test.

If you see ERR_TIMED_OUT in Lighthouse, just rerun the test. The site’s still live. The results will stabilise as we optimise the system.


Final Word: No Excuses

We built something ambitious — and we’re not hiding behind that.

The performance dip ends here. The rebuild is already underway.

This isn’t a nice-to-have. It’s a non-negotiable.

We’re committed to making EazySites feel as fast as it is focused, because if we’re building in public, we have to be accountable in public too.

Thanks for your patience. Updates coming soon.

Adam Martelletti & The Eazysite Team