Mastodon

Intuitively, these charts might tempt you to compare these hosts, making assumptions about the investment each of these services put into their server infrastructure — but that wouldn’t be the whole story.

Knowing that TTFB is both server AND client-dependent (including times for Service Worker init, DNS, TLS), this graph might instead represent how wealthy each service’s audience is.

Looks like the above was last updated in November 2024 but links to the HTTP Archive Tech Report for newer data: https://httparchive.org/reports/techreport/tech?good-cwv-over-time=TTFB&tech=Hostinger,SiteGround,WP+Engine,Shopify,GoDaddy+Website+Builder,Framer+Sites,GitHub+Pages,Squarespace,Vercel,Netlify,Seravo,Weebly,Pantheon,Fly.io,Kinsta&geo=ALL&rank=ALL#comparison-good-cwvs

Here’s a screenshot from 01 July 2025:

Screenshot of the HTTP Archive Tech Report showing Shopify and Squarespace still occupying the top two spots in TTFB Core Web Vitals performance at 85% and 81% respectively

if you’re going to paste multiple paragraphs of AI slop at least have the decency to make AI summarize it down to two words or less first (preferably zero words if possible)

One more entry in my epic date parsing adventure. I’ve shipped a breaking change to this library to ensure that all valid date strings supported in Eleventy v4 will be RFC 9557-compatible, ensuring friendliness with the standardized Temporal APIs coming to a JavaScript runtime near you. Our full test suite runs against both!

Read (a little) more: https://github.com/11ty/parse-date-strings/releases/tag/v2.0.0

is it too much to ask that a software dependency be:

1. fast
2. permissive open-source licensed
3. lightweight in bundle cost
4. lightweight in installation size
5. well-maintained
6. accurate
7. able to run in all of the marginally different JavaScript runtimes
8. human sourced to avoid ethical and future copyright issues with AI
9. use modern APIs and without vestigial polyfill bloat
10. use best progressive enhancement and accessibility practices

(what would you add?)

In my 19 full-time professional years in this business there have been many eras in which very prominent web developers have argued “don’t worry about it” in discussions of web performance and time has *never* proven those arguments to have merit, even with continually improving network connections and hardware.

The web is diverse. Let’s keep it that way!

Saw some wild messaging from Apple in the Software Update app on an old MacBook — in fact the system was *not* up-to-date. Surfaced via a Google Chrome EOL message.

Got them switched over to the latest version of Firefox just fine 👀

The web should be for everyone (and not just on new hardware)

Your Mac is up to date — macOS Cataline 10.15.7 Google Chrome: To get future Google Chrome updates, you’ll need macOS 11 or later. This computer is using macOS 10.15.