But do you use everything on every single page? The full frameworks load all that whether you use it or not. Then again, what about caching for subsequent pages? How much needs to be reloaded from the server? How much will come from browser cache? Do any of these frameworks full or mini cache more or less?
Another test to add would be the use of a stack in Source that the others donât have, compare to their native stacks, then also compare all frameworks using the same 3rd party stack.
Would be interesting to look at to see how much using native v 3rd party stack affects things. Admittedly might be a bit of a task picking which 3rd party stacks to use
Guys, I really like this discussion.
What I am missing here is that the browser is caching content, either JS or CSS files.
So when saying âthe framework loads Petabytes of dataâ please also see that on the second load, this should be cached.
Cheers đ»
1 Like
I asked that same question.
But, If the initial page a user clicks on is too heavy and loads too slow, will they ever see the second page? Probably not as theyâll have moved on.
And what about CDNâs? If you can use them (GDPR?), common libraries like jQuery or popular Google fonts might very well be already in the browserâs cache.
Yes I agree. Itâs the loading of the first page, for the first that will potentially put off a visitor it it load too slowly, with a slow connection or poor mobile signal, waiting to visit other pages.
1 Like
And you never know what page will be their âfirst pageâ. Theyâll hopefully be coming off a SERP or another link that can be deep inside your site.
âEvery Page is a Landing Pageâ.
2 Likes
A very nice summary of why progressive enhancement is important even in non 3rd world situation. Remember I only ever asked for progressive enhancement not zero JS.