ПІДТРИМАЙ УКРАЇНУ ПІДТРИМАТИ АРМІЮ
Uk Uk

Navigating Routing Challenges: Why Traditional MPAs May Outshine SPAs

Navigating Routing Challenges: Why Traditional MPAs May Outshine SPAs

Explore the intricacies of routing in Single-Page Applications and discover why Multi-Page Applications might provide more dependable navigation solutions

In part 2, I glossed over a lot when I wrote…

I decided this called for an MPA. (aka a traditional web app. Site. Thang. Not-SPA. Whatever.)

Okay, but why did I decide that? To demo the fastest possible Kroger.com, I should consider all options — why not a Single-Page App?

Alright, let’s try a SPA

While React was ≈2× too big , surely I could fit a SPA of some kind in my 20kB budget. I’ve seen it done: the PROXX game’s initial load fits in 20kB , and it’s smooth on wimpier phones than the Poblano.

So, rough estimate off the top of my head…

Source Parse size gzip size
preact 10.6.6 10.2kB 4kB
preact-router 4.0.1 4.5kB 1.9kB
react-redux 7.2.6 15.4kB 5kB
redux 4.1.2 4.3kB 1.6kB
My components1 5.9kB 2.1kB
Total 40.3kB ≈14.6kB

  • The HTML is little else than
    Scroll to Top