mastodon.uno è uno dei tanti server Mastodon indipendenti che puoi usare per partecipare al fediverso.
Mastodon.Uno è la principale comunità mastodon italiana. Con 77.000 iscritti è il più grande nodo Mastodon italiano: anima ambientalista a supporto della privacy e del mondo Open Source.

Statistiche del server:

6,3K
utenti attivi

#webperf

13 post11 partecipanti0 post oggi

There are so many things I love about SpeedCurve's Vitals dashboard...

😀 Key metrics – Backend, FCP, TBT – alongside Core Web Vitals (because #CoreWebVitals are not enough!)
😀 Defines each metric, including browser support
😀 13 months of data!
😀 Explore INP and LCP subparts
😀 Detailed diagnostics for each metric

Believe it or not, there's more. Sign up (for free) and check it out for yourself: speedcurve.com/signup/

Let me know if you have any questions or feedback!

Few things frustrate me more than feeling like I've done everything right, but nothing got better.

Say you've done all the right things. You've lazy-loaded and compressed and minified. You've seen improvements to Start Render or LCP or INP. But bounce rate didn't improve. Neither did conversion rate or any other business metric you care about. WHY???

The answer might lie on the performance plateau.

speedcurve.com/blog/web-perfor

SpeedCurveSpeedCurve | Why you need to know your site's performance plateau (and how to find it)Have you ever wondered why your site got faster, but your business and user engagement metrics didn't change? Here's why.
#ux#webperf#sitespeed

"I made my pages faster, but my business and user engagement metrics didn't change. WHY???"

speedcurve.com/blog/web-perfor

(I just realized my original post about why – and how – to measure the performance plateau for your site was a couple of years old, so I've refreshed it with new info!)

SpeedCurveSpeedCurve | Why you need to know your site's performance plateau (and how to find it)Have you ever wondered why your site got faster, but your business and user engagement metrics didn't change? Here's why.
#webperf#ux#pagespeed

I am in an old city with thick walls, narrow streets, and tall buildings. Mobile data signals don’t travel well. So every restaurant and shop has their own WiFi network. It’s like going back in time a few decades. Web performance is important here. #webPerf

After I shared the latest results from SpeedCurve's Industry Page Speed Benchmarks, a number of folks asked me how to create their own competitive benchmarking leaderboards. The good news: you can do that very easily in @speedcurve!

Here's a quick demo: support.speedcurve.com/docs/co

SpeedCurveHow to Benchmark Your Site Speed Against CompetitorsKnowing which of your competitors are faster than you is a great way to get web performance buy-in throughout your organization.
#webperf#ux#sitespeed

New features in #Shopify Theme Vitals (plus March data is live):

NEW: All themes with any data points in the latest data show up. You still need at least 50 data points to see #webperf data, but you can see current URL counts, market rank, AND…

NEW: Theme versions. Shows the context behind performance numbers (e.g. the latest version has a perf improvement, but shops haven’t updated yet so the numbers don't reflect it).

Here’s the theme list so you can check it out:
themevitals.com/themes/

Theme VitalsAll Themes Performance Data | Theme Vitals
Altro da Sia Karamalegos

Why did The Guardian take top spot in our Media Page Speed Benchmarks? Because the main image was the fifth request on the page.

Calling the LCP element early seems like a no-brainer, right? Yet too often, I see it called MUCH too late.

Page Speed Benchmarks: app.speedcurve.com/benchmarks/

The Guardian's test details: app.speedcurve.com/benchmark/m