Blog

Tag: Performance

7 articles

The hero image should stay where we put it

Pages that jump while loading lose people. Reserve the hero’s space, trace each shift to its real cause, steady fonts and late content, then test again.

#CLS

.NET 9 is here. The upgrade still needs to earn its place.

.NET 9 brings runtime and tooling improvements. Separate the runtime decision from feature experiments and weigh support windows and testing effort.

#.NET 9

The page can wait a second. The customer should not have to.

Laravel’s deferred functions, Cache::flexible and queues change when work happens. Choose which kind of later a task can safely tolerate.

#Caching

Before buying a bigger server, check what the app keeps doing twice

Sometimes an app keeps asking the same expensive question. Decide what deserves caching and agree how old is too old before you buy more capacity.

#Caching

Your website loads. Why does it still feel slow?

A fast speed-test score doesn’t mean filters, bookings or checkouts feel fast. Find the delays people feel and measure the journeys they complain about.

#Core Web Vitals

Your Laravel app needs a dashboard before it needs more horsepower

Before paying for a bigger server, follow one delayed task through your Laravel app. Slow jobs, endpoints and queue pressure show where customers get stuck.

#Laravel

.NET 8 is here. Will your customers notice?

A faster .NET 8 runtime only matters when customers feel it. How to baseline real journeys, check correctness and decide when an upgrade earns its cost.

#.NET 8

Turn reading into results

Like what you’re reading? Let’s put it to work on your brand.