Email or username:

Password:

Forgot your password?
Simon Willison

Everyone who builds web applications should read the Reckoning series by @slightlyoff infrequently.org/series/reckon

My own notes here, but you should work through the entire thing: simonwillison.net/2024/Aug/18/

Seriously, take a look at the case-study in which the California food stamps signup site takes 29.5s to become interactive on a slow rural mobile connection, and tell me we don't urgently need to do better! infrequently.org/2024/08/objec

5 comments
Steve Freeman

@simon @slightlyoff one of the good things that uk Government Digital Service did was to develop a standard designed (as far as i can tell) for low end devices and connections.

Assaf πŸ₯₯🌴

@simon websites from CA gov are exceptionally bad … it's like there's a lack of tech talent in CA … but it's not only slow rural mobile connections, it's painfully bad even on iPhone 15 Pro with super-fast 5G connection (not to mention endless bugs, broken links, etc)

Bob πŸ‡ΊπŸ‡²β™’πŸ§πŸͺ–

@simon @slightlyoff

Killing all the tracking code to Google and all corporates makes our services on MPAQ, very fast. We are even working on self hosting a hit counter 😜 outsourcing is a major draw on performance.

Bill Zaumen

@simon @slightlyoff It is not just javascript. In spite of a high-bandwidth connection, I've been getting very bad response loading web pages recently. After diagnosing the problem, I found that there was 76% to 91% packet loss on DNS requests to the servers my ISP configures! I'm about to file a service request, but in the meantime, I changed DNS servers to publicly available ones.

What made it worse was the number of DNS requests now needed to load a web page.

razze

@simon @slightlyoff I don't think saying Javascript is the cause of this is honest or helpful.

Go Up