#webperf — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #webperf, aggregated by home.social.
-
There’s a special kind of satisfaction in updating servers and sites to the latest PHP 8.5 without a single hiccup. 🚀
That’s when you know you’re doing things the right way—the Webinoly way.
Stability and performance, no compromises.
-
#Development #Comparisons
CSS vs. JavaScript · Animation performance is more nuanced than expected https://ilo.im/16d8gb_____
#Animations #Transitions #Motion #GSAP #APIs #WebPerf #WebDev #Frontend #CSS #JavaScript -
Now, this is just the home page, I still have some work left on other parts of the site. And the performance overall has already been pretty decent.
The two things I mainly focused on were:
1. Color contrast. I've been a bit lazy about this, I will admit, relying on Bootstrap's own color theme. Finally cleaned this up.
2. Custom web fonts. And I think this is a big one. The only font I really wanted to keep is the Atkinson Hyperlegible Font from Braille Institute as the main font. Huge fan of this font.
https://www.brailleinstitute.org/freefont/
For the rest, using system fonts is very much "good enough" and I highly recommend checking out https://modernfontstacks.com for this.
-
Hey fediverse, happy Friday!
A small personal victory, but after a few days of tinkering with my website https://stefanbohacek.com, I finally achieved the mythical perfect PageSpeed score.
-
#Development #Introductions
Declarative partial updates · Chrome’s new proposals for the web platform https://ilo.im/16d23j_____
#HtmlStreaming #Chrome #Browser #APIs #Polyfills #WebPerf #WebDev #Frontend #HTML #JavaScript -
#Development #Introductions
Declarative partial updates · Chrome’s new proposals for the web platform https://ilo.im/16d23j_____
#HtmlStreaming #Chrome #Browser #APIs #Polyfills #WebPerf #WebDev #Frontend #HTML #JavaScript -
#Development #Introductions
Declarative partial updates · Chrome’s new proposals for the web platform https://ilo.im/16d23j_____
#HtmlStreaming #Chrome #Browser #APIs #Polyfills #WebPerf #WebDev #Frontend #HTML #JavaScript -
#Development #Introductions
Declarative partial updates · Chrome’s new proposals for the web platform https://ilo.im/16d23j_____
#HtmlStreaming #Chrome #Browser #APIs #Polyfills #WebPerf #WebDev #Frontend #HTML #JavaScript -
An extremely meta summary of recent micro-optimizations for fellow #IndieWeb, #WebPerf and #Eleventy nerds 🫶 https://tylersticka.com/journal/dependency-spring-cleaning-2026/
-
An extremely meta summary of recent micro-optimizations for fellow #IndieWeb, #WebPerf and #Eleventy nerds 🫶 https://tylersticka.com/journal/dependency-spring-cleaning-2026/
-
An extremely meta summary of recent micro-optimizations for fellow #IndieWeb, #WebPerf and #Eleventy nerds 🫶 https://tylersticka.com/journal/dependency-spring-cleaning-2026/
-
An extremely meta summary of recent micro-optimizations for fellow #IndieWeb, #WebPerf and #Eleventy nerds 🫶 https://tylersticka.com/journal/dependency-spring-cleaning-2026/
-
An extremely meta summary of recent micro-optimizations for fellow #IndieWeb, #WebPerf and #Eleventy nerds 🫶 https://tylersticka.com/journal/dependency-spring-cleaning-2026/
-
Speeding up oxlint and oxfmt
Another excellent blog post in the "Speeding up the JavaScript ecosystem" series by Marvin
Hagemeister @marvinhhttps://marvinh.dev/blog/speeding-up-javascript-ecosystem-part-13/
-
This timeline tab on npmx.dev shows good & bad changes to the package over time. :)
https://npmx.dev/package-timeline/@ayo-run/status-indicator/v/2.1.1
-
This timeline tab on npmx.dev shows good & bad changes to the package over time. :)
https://npmx.dev/package-timeline/@ayo-run/status-indicator/v/2.1.1
-
This timeline tab on npmx.dev shows good & bad changes to the package over time. :)
https://npmx.dev/package-timeline/@ayo-run/status-indicator/v/2.1.1
-
This timeline tab on npmx.dev shows good & bad changes to the package over time. :)
https://npmx.dev/package-timeline/@ayo-run/status-indicator/v/2.1.1
-
This timeline tab on npmx.dev shows good & bad changes to the package over time. :)
https://npmx.dev/package-timeline/@ayo-run/status-indicator/v/2.1.1
-
The April web performance data for Shopify themes is now live - check out the newsletter with all updates and the site for the full data at:
https://themevitals.com/newsletter/2026-05/ -
The April web performance data for Shopify themes is now live - check out the newsletter with all updates and the site for the full data at:
https://themevitals.com/newsletter/2026-05/ -
The April web performance data for Shopify themes is now live - check out the newsletter with all updates and the site for the full data at:
https://themevitals.com/newsletter/2026-05/ -
The April web performance data for Shopify themes is now live - check out the newsletter with all updates and the site for the full data at:
https://themevitals.com/newsletter/2026-05/ -
The April web performance data for Shopify themes is now live - check out the newsletter with all updates and the site for the full data at:
https://themevitals.com/newsletter/2026-05/ -
RE: https://mamot.fr/@ParisWeb/116555672262079036
#parisweb, ma conférence de cœur, a accepté que je vienne vous présenter un atelier pour se mettre à jour sur les outils de la #webperf
-
A bit inside baseball -- how I made my blog faster: cut CI per push from ~6 min to ~2 min, and kept every home/archive page O(1) in corpus size. Principles: compute once at input-change time, put the result under a stable URL, let everything downstream pull it from cache.
https://benjaminhan.net/posts/20260511-site-efficiency/?utm_source=mastodon&utm_medium=social
-
A bit inside baseball -- how I made my blog faster: cut CI per push from ~6 min to ~2 min, and kept every home/archive page O(1) in corpus size. Principles: compute once at input-change time, put the result under a stable URL, let everything downstream pull it from cache.
https://benjaminhan.net/posts/20260511-site-efficiency/?utm_source=mastodon&utm_medium=social
-
A bit inside baseball -- how I made my blog faster: cut CI per push from ~6 min to ~2 min, and kept every home/archive page O(1) in corpus size. Principles: compute once at input-change time, put the result under a stable URL, let everything downstream pull it from cache.
https://benjaminhan.net/posts/20260511-site-efficiency/?utm_source=mastodon&utm_medium=social
-
A bit inside baseball -- how I made my blog faster: cut CI per push from ~6 min to ~2 min, and kept every home/archive page O(1) in corpus size. Principles: compute once at input-change time, put the result under a stable URL, let everything downstream pull it from cache.
https://benjaminhan.net/posts/20260511-site-efficiency/?utm_source=mastodon&utm_medium=social
-
A bit inside baseball -- how I made my blog faster: cut CI per push from ~6 min to ~2 min, and kept every home/archive page O(1) in corpus size. Principles: compute once at input-change time, put the result under a stable URL, let everything downstream pull it from cache.
https://benjaminhan.net/posts/20260511-site-efficiency/?utm_source=mastodon&utm_medium=social
-
RE: https://fosstodon.org/@webinoly/116489229798729785
Still tracking the Ubuntu 26.04 rollout.
This release introduced several critical low-level changes and improvements that are causing a slower-than-usual turnaround for some upstream packages. While developers work through these complexities, we remain in "stability first" mode.
We’ll pull the trigger on full support as soon as the core stack meets production standards. Thanks for your patience!
-
RE: https://fosstodon.org/@webinoly/116489229798729785
Still tracking the Ubuntu 26.04 rollout.
This release introduced several critical low-level changes and improvements that are causing a slower-than-usual turnaround for some upstream packages. While developers work through these complexities, we remain in "stability first" mode.
We’ll pull the trigger on full support as soon as the core stack meets production standards. Thanks for your patience!
-
Most cache misconfiguration is not carelessness, it's a missing handshake.
Your build encodes assumptions: hashed filenames mean the URL changes whenever the content changes. The web server has to know that, or the assumption stays unused.
If the config doesn't reflect what the build produces, the framework's work gets quietly undone at the last layer of the chain.
-
Most cache misconfiguration is not carelessness, it's a missing handshake.
Your build encodes assumptions: hashed filenames mean the URL changes whenever the content changes. The web server has to know that, or the assumption stays unused.
If the config doesn't reflect what the build produces, the framework's work gets quietly undone at the last layer of the chain.
-
Most cache misconfiguration is not carelessness, it's a missing handshake.
Your build encodes assumptions: hashed filenames mean the URL changes whenever the content changes. The web server has to know that, or the assumption stays unused.
If the config doesn't reflect what the build produces, the framework's work gets quietly undone at the last layer of the chain.
-
Your site loads. From the outside it works. But: do returning visitors re-download everything on every click? Can the connection be downgraded from HTTPS to HTTP on public WiFi? Does your homepage count as one site in Google's eyes, or two?
For most static sites: no, yes, and yes. The web server config is the last layer most setups never touch.
-
Your site loads. From the outside it works. But: do returning visitors re-download everything on every click? Can the connection be downgraded from HTTPS to HTTP on public WiFi? Does your homepage count as one site in Google's eyes, or two?
For most static sites: no, yes, and yes. The web server config is the last layer most setups never touch.
-
Your site loads. From the outside it works. But: do returning visitors re-download everything on every click? Can the connection be downgraded from HTTPS to HTTP on public WiFi? Does your homepage count as one site in Google's eyes, or two?
For most static sites: no, yes, and yes. The web server config is the last layer most setups never touch.
-
Your site loads. From the outside it works. But: do returning visitors re-download everything on every click? Can the connection be downgraded from HTTPS to HTTP on public WiFi? Does your homepage count as one site in Google's eyes, or two?
For most static sites: no, yes, and yes. The web server config is the last layer most setups never touch.
-
#Development #Launches
Moop · A desktop app for batch image optimization https://ilo.im/16cof4_____
#OpenSource #MacOS #Optimization #Images #Content #Design #WebDesign #WebPerf #WebDev #Frontend -
#Development #Launches
Moop · A desktop app for batch image optimization https://ilo.im/16cof4_____
#OpenSource #MacOS #Optimization #Images #Content #Design #WebDesign #WebPerf #WebDev #Frontend -
#Development #Launches
Moop · A desktop app for batch image optimization https://ilo.im/16cof4_____
#OpenSource #MacOS #Optimization #Images #Content #Design #WebDesign #WebPerf #WebDev #Frontend -
#Development #Launches
Moop · A desktop app for batch image optimization https://ilo.im/16cof4_____
#OpenSource #MacOS #Optimization #Images #Content #Design #WebDesign #WebPerf #WebDev #Frontend -
#Development #Guides
Browser caching with No-Vary-Search · Better HTTP caching by ignoring irrelevant query parameters https://ilo.im/16crk2_____
#Caching #URL #UrlParameters #HTTP #HttpCache #HttpHeaders #Browsers #WebPerf #WebDev #Frontend -
#Development #Guides
Browser caching with No-Vary-Search · Better HTTP caching by ignoring irrelevant query parameters https://ilo.im/16crk2_____
#Caching #URL #UrlParameters #HTTP #HttpCache #HttpHeaders #Browsers #WebPerf #WebDev #Frontend -
#Development #Guides
Browser caching with No-Vary-Search · Better HTTP caching by ignoring irrelevant query parameters https://ilo.im/16crk2_____
#Caching #URL #UrlParameters #HTTP #HttpCache #HttpHeaders #Browsers #WebPerf #WebDev #Frontend -
#Development #Guides
Browser caching with No-Vary-Search · Better HTTP caching by ignoring irrelevant query parameters https://ilo.im/16crk2_____
#Caching #URL #UrlParameters #HTTP #HttpCache #HttpHeaders #Browsers #WebPerf #WebDev #Frontend -
Single data point by the looks of it but dang, TCP RTT from North Korea to one of our CDNs is slow AF, 1.53 seconds.
For comparison, the mean values around Europe are in the order of 25-30ms.
-
#Development #Approaches
Architecture of local-first web development · How to build local-first web apps in 2026 https://ilo.im/16cq0b_____
#LocalFirst #WebApps #Websites #Git #JavaScript #Database #WebPerf #WebDev #Frontend #Backend -
#Development #Approaches
Architecture of local-first web development · How to build local-first web apps in 2026 https://ilo.im/16cq0b_____
#LocalFirst #WebApps #Websites #Git #JavaScript #Database #WebPerf #WebDev #Frontend #Backend