#WebPerformance

Neil CraigA *single* Jira (cloud/SaaS) ticket page inc. assets is 53.3MB. There's not even any images or attachments and only 4 very short comments. <a href="https://mastodon.social/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a>

WebPerformance Report🔔 Don’t have your report yet? You’re just in time to get this week’s <a href="https://webperf.social/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a> Report. Used by experts at Google, Mozilla, Chanel, Airbnb, and more. Get your own report now 👉 <a href="https://webperformancereport.com" rel="nofollow noopener" translate="no" target="_blank">https://webperformancereport.com</a> <a href="https://webperf.social/tags/webperf" class="mention hashtag" rel="nofollow noopener" target="_blank">#webperf</a> <a href="https://webperf.social/tags/ux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ux</a> <a href="https://webperf.social/tags/seo" class="mention hashtag" rel="nofollow noopener" target="_blank">#seo</a> <a href="https://webperf.social/tags/websecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#websecurity</a> <a href="https://webperf.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://webperf.social/tags/martech" class="mention hashtag" rel="nofollow noopener" target="_blank">#martech</a> <a href="https://webperf.social/tags/digitalmarketing" class="mention hashtag" rel="nofollow noopener" target="_blank">#digitalmarketing</a>

WinbuzzerGoogle Analyst Warns: AI Bots Risk Internet Gridlock By Server Overload<a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <a href="https://mastodon.social/tags/AICrawlers" class="mention hashtag" rel="nofollow noopener" target="_blank">#AICrawlers</a> <a href="https://mastodon.social/tags/InternetCongestion" class="mention hashtag" rel="nofollow noopener" target="_blank">#InternetCongestion</a> <a href="https://mastodon.social/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a> <a href="https://mastodon.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> <a href="https://mastodon.social/tags/AIethics" class="mention hashtag" rel="nofollow noopener" target="_blank">#AIethics</a> <a href="https://mastodon.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://mastodon.social/tags/FutureOfWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#FutureOfWeb</a> <a href="https://mastodon.social/tags/AISafety" class="mention hashtag" rel="nofollow noopener" target="_blank">#AISafety</a> <a href="https://mastodon.social/tags/DataPrivacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataPrivacy</a><a href="https://winbuzzer.com/2025/05/31/google-analyst-warns-ai-bots-risk-internet-gridlock-by-server-overload-xcxwbn/" rel="nofollow noopener" translate="no" target="_blank">https://winbuzzer.com/2025/05/31/google-analyst-warns-ai-bots-risk-internet-gridlock-by-server-overload-xcxwbn/</a>

Boris Schapira (Pro)Comme je sais que mon audience est plutôt sensible à ces sujets, une autre démo où on voit que l'agent IA Sense est également capable de répondre aux questions sur la Web Performance et les Core Web Vitals.<a href="https://hachyderm.io/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a> <a href="https://hachyderm.io/tags/SpeedAnalysis" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpeedAnalysis</a> <a href="https://hachyderm.io/tags/CoreWebVitals" class="mention hashtag" rel="nofollow noopener" target="_blank">#CoreWebVitals</a> <a href="https://hachyderm.io/tags/RUM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RUM</a>

Tammy EvertsI recently published my annual dive into the HTTP Archive, focusing on page growth, web performance, and UX: <a href="https://www.speedcurve.com/blog/page-bloat-2025/" rel="nofollow noopener" translate="no" target="_blank">https://www.speedcurve.com/blog/page-bloat-2025/</a>A common question is "How big SHOULD my pages be?" According to analysis by <a href="https://toot.cafe/@slightlyoff" class="u-url mention" rel="nofollow noopener" target="_blank">@slightlyoff</a>, the ideal page should be <1.4 MB with <365 KB coming from JS.<a href="https://webperf.social/tags/ux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ux</a> <a href="https://webperf.social/tags/webperf" class="mention hashtag" rel="nofollow noopener" target="_blank">#webperf</a> <a href="https://webperf.social/tags/pagespeed" class="mention hashtag" rel="nofollow noopener" target="_blank">#pagespeed</a> <a href="https://webperf.social/tags/sitespeed" class="mention hashtag" rel="nofollow noopener" target="_blank">#sitespeed</a> <a href="https://webperf.social/tags/webperformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#webperformance</a>

Boris Schapira (Pro)Is your bounce rate within the norm? And how much is your traffic costing you? Is your conversion rate up to industry standards?The Contentsquare Digital Experience Benchmark is here to answer all these questions and much more.With an in-depth analysis of 90 billion sessions (389 billion page views), this report, available as a document or an interactive web application, offers valuable insights into acquisition channels, mobile versus desktop engagement, retention, and revenue.It also includes an analysis of the most common UX and technical frustrations (and, as you might suspect if you follow me, it also comments on the impact of Web Performance).Optimize your digital strategy: check it out now!<a href="https://go.contentsquare.com/en/digital-experience-benchmark?utm_source=mastodon&utm_medium=social" rel="nofollow noopener" translate="no" target="_blank">https://go.contentsquare.com/en/digital-experience-benchmark?utm_source=mastodon&utm_medium=social</a><a href="https://hachyderm.io/tags/Boostmarks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Boostmarks</a> <a href="https://hachyderm.io/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UX</a> <a href="https://hachyderm.io/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a> <a href="https://hachyderm.io/tags/Performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Performance</a>

Ayo AycoThere’s a fediverse community for <a href="https://social.ayco.io/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a>👉 <a href="https://webperf.social/about" rel="nofollow noopener" translate="no" target="_blank">https://webperf.social/about</a><a href="https://social.ayco.io/tags/til" class="mention hashtag" rel="nofollow noopener" target="_blank">#til</a> <a href="https://social.ayco.io/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://social.ayco.io/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a> <a href="https://social.ayco.io/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a>

Neil CraigAfter nearly 6.5 years since the bug/feature request was filed, it looks like Chromium are going to implement `cache-control: immutable`!The bug has been assigned to someone at Microsoft so maybe they want it in Edge. Good news, IMO!<a href="https://issues.chromium.org/issues/41253661" rel="nofollow noopener" translate="no" target="_blank">https://issues.chromium.org/issues/41253661</a><a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/CacheControl" class="mention hashtag" rel="nofollow noopener" target="_blank">#CacheControl</a> <a href="https://mastodon.social/tags/Immutable" class="mention hashtag" rel="nofollow noopener" target="_blank">#Immutable</a> <a href="https://mastodon.social/tags/WebPerf" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerf</a> <a href="https://mastodon.social/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a>

Neil CraigLatest p75 Time To First Byte (TTFB) for www.bbc.com across the world.I've probably shared it before but it illustrates the diversity of global, regional and local internet connectivity quality.We see variation (for the same content) from 100-200ms in Europe, USA, Canada, Aus, NZ etc. right through to almost 6s for Central African Republic.Clearly a lot of improvements to be made in Africa, South America and parts of Asia still.<a href="https://mastodon.social/tags/webPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#webPerformance</a> <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webDev</a> <a href="https://mastodon.social/tags/BBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBC</a> <a href="https://mastodon.social/tags/internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#internet</a>

Neil CraigMy pals in BBC World Service have been doing some awesome work on "lite" versions of their news articles (other page types to follow). They essentially skip the Server-Side React hydration which means you end up with a simpler HTML+CSS page, no JS. Page sizes drop significantly: * Transferred: ~600KB -> 30KB * Total: 1.65MB -> 135KB Just append `.lite` on a URL e.g. <a href="https://www.bbc.com/mundo/articles/crgyyvdz1dro.lite" rel="nofollow noopener" translate="no" target="_blank">https://www.bbc.com/mundo/articles/crgyyvdz1dro.lite</a> There's no on/off UX at the moment but they're working on that too. <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/WebPerf" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerf</a> <a href="https://mastodon.social/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a> <a href="https://mastodon.social/tags/BBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBC</a>

piefedadminFediverse traffic is pretty bursty and sometimes there will be a large backlog of Activities to send to your server, each of which involves a POST. This can hammer your instance and overwhelm the backend’s ability to keep up. Nginx provides a rate-limiting function which can accept POSTs at full speed and proxy them slowly through to your backend at whatever rate you specify.For example, PieFed has a backend which listens on port 5000. Nginx listens on port 443 for POSTs from outside and sends them through to port 5000:<pre><code>upstream app_server {   server 127.0.0.1:5000 fail_timeout=0;}</code></pre><pre><code>server {   listen 443 ssl;   listen [::]:443 ssl;   server_name piefed.social www.piefed.social;   root /var/www/whatever;   location / {       # Proxy all requests to Gunicorn       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;       proxy_set_header X-Forwarded-Proto $scheme;       proxy_set_header Host $http_host;       proxy_redirect off;       proxy_http_version 1.1;       proxy_set_header Connection "";       proxy_pass http://app_server;       ssi off;   }</code></pre>To this basic config we need to add rate limiting, using the ‘limit_req_zone’ directive. Google that for further details.<pre><code>limit_req_zone $binary_remote_addr zone=one:100m rate=10r/s;</code></pre>This will use up to 100 MB of RAM as a buffer and limit POSTs to 10 per second, per IP address. Adjust as needed. If the sender is using multiple IP addresses the rate limit will not be as effective. Put this directive outside your server {} block.Then after our first location / {} block, add a second one that is a copy of the first except with one additional line (and change it to apply to location /inbox or whatever the inbox URL is for your instance):<pre><code>location /inbox {       limit_req zone=one burst=300;#       limit_req_dry_run on;       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;       proxy_set_header X-Forwarded-Proto $scheme;       proxy_set_header Host $http_host;       proxy_redirect off;       proxy_http_version 1.1;       proxy_set_header Connection "";       proxy_pass http://app_server;       ssi off;  }</code></pre>300 is the maximum number of POSTs it will have in the queue. You can use limit_req_dry_run to test the rate limiting without actually doing any limiting – watch the nginx logs for messages while doing a dry run.It’s been a while since I set this up so please let me know if I mixed anything crucial out or said something misleading.<a href="https://join.piefed.social/2024/04/17/handling-large-bursts-of-post-requests-to-your-activitypub-inbox-using-a-buffer-in-nginx/" class="" rel="nofollow noopener" target="_blank">https://join.piefed.social/2024/04/17/handling-large-bursts-of-post-requests-to-your-activitypub-inbox-using-a-buffer-in-nginx/</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://join.piefed.social/tag/nginx/" target="_blank">#nginx</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://join.piefed.social/tag/web-performance/" target="_blank">#webPerformance</a>

Tammy EvertsEvery year I revisit the topic of web performance budgets. Here's my updated guide, including:✅ What are performance budgets? ✅ Why are they a crucial tool in fighting page speed regression? ✅ Best metrics to track ✅ Determining thresholds ✅ Pro tips<a href="https://www.speedcurve.com/blog/performance-budgets/" rel="nofollow noopener" translate="no" target="_blank">https://www.speedcurve.com/blog/performance-budgets/</a> <a href="https://webperf.social/tags/ux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ux</a> <a href="https://webperf.social/tags/pagespeed" class="mention hashtag" rel="nofollow noopener" target="_blank">#pagespeed</a> <a href="https://webperf.social/tags/corewebvitals" class="mention hashtag" rel="nofollow noopener" target="_blank">#corewebvitals</a> <a href="https://webperf.social/tags/webperf" class="mention hashtag" rel="nofollow noopener" target="_blank">#webperf</a> <a href="https://webperf.social/tags/webperformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#webperformance</a>

Liminal witch 🧙‍♀️ Sarah🆕 blog post about browsing the web on 2GFor the past couple of months I've been taking a rural bus to the city about once a week. After years of living in cities it's safe to say that mobile connection in cities and rural areas is not the same experience<a href="https://www.sarahgebauer.com/post/lesson-from-a-rural-bus-for-web-developers" rel="nofollow noopener" translate="no" target="_blank">https://www.sarahgebauer.com/post/lesson-from-a-rural-bus-for-web-developers</a><a href="https://hachyderm.io/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a>

Addy OsmaniThe <img> element now supports lazy-loading, async decoding, Priority Hints and more. I wrote about some of them for the StackOverflow blog: <a href="https://bit.ly/soimgs" rel="nofollow noopener" translate="no" target="_blank">https://bit.ly/soimgs</a> Helpful if optimizing UX & performance.<a href="https://indieweb.social/tags/webperformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#webperformance</a>

Nick FSeems like Mastodon might actually be taking off this time, so... here's an <a href="https://mastodon.social/tags/introduction" class="mention hashtag" rel="nofollow noopener" target="_blank">#introduction</a>!👋 I'm a web developer with a particular interest in <a href="https://mastodon.social/tags/DesignSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#DesignSystems</a>, <a href="https://mastodon.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a>, and <a href="https://mastodon.social/tags/WebPerformance" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPerformance</a>. I love <a href="https://mastodon.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> and <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a> but I'm not averse to a bit of <a href="https://mastodon.social/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a>I've also worked as a researcher in experimental <a href="https://mastodon.social/tags/psychology" class="mention hashtag" rel="nofollow noopener" target="_blank">#psychology</a>, studying perception and attention.In my spare time I like to read, watch films, and make <a href="https://mastodon.social/tags/ElectronicMusic" class="mention hashtag" rel="nofollow noopener" target="_blank">#ElectronicMusic</a>.I lived in Japan for a few years, so <a href="https://mastodon.social/tags/%E6%97%A5%E6%9C%AC%E8%AA%9E" class="mention hashtag" rel="nofollow noopener" target="_blank">#日本語</a> もOKです。よろしくね！

Recent searches

Search options

Administered by:

Server stats: