The Crushing Weight of the Facepile
Update: Read the newest update to this approach: Back to the Facepile, Featherweight Addition.
I was cruising my own web site with DevTools open (as one does) and browsed to my latest blog post only to be slapped in the face with a 3.7MB web site. My web site (on a blog post page without content images) is normally about 400KB. What happened??
Astute readers of blog post titles may already be ahead of me here—the more successful the blog post got on social media, the more webmentions it got, and the cluster of avatars below the post (the facepile, as it is known) grew and grew.
What should I do?
- My first instinct was to make the images intrinsically smaller. Solve the problem at the root! Some of them came back from webmention.io’s avatar cache as 256×256—one was 135KB 😱. I filed an issue upstream for this. But I needed to solve this problem immediately, locally.
- Use Cloudinary or imgix or Netlify Image transformations or some other free-for-now or free-metered or fully paid service to resize these automatically. I started down this road and decided it was a little much for a personal site.
- “Zach, you’re just being vain—simply cap the list and only show a few of these images maximum.” I mean, yeah, I guess. But I also like investing in showcasing webmentions fairly prominently on my site because I’m trying to be an advocate for IndieWeb.
- Use
loading="lazy"to lazy load these images. I was already doing this but browser support is non-existent, currently. - Take control of it myself and use
IntersectionObserverto lazy load them only when they come into view.IntersectionObserverbrowser support is pretty good now. I decided to go with this low hanging fruit for now (at least as a short term solution).
Enter IntersectionObserver
HTML
<img src="/web/img/webmention-avatar-default.svg" data-src="https://webmention.io/avatar/…" alt="Author name" class="webmentions__face">JavaScript
if( typeof IntersectionObserver !== "undefined" && "forEach" in NodeList.prototype ) {
var observer = new IntersectionObserver(function(changes) {
if ("connection" in navigator && navigator.connection.saveData === true) {
return;
}
changes.forEach(function(change) {
if(change.isIntersecting) {
change.target.setAttribute("src", change.target.getAttribute("data-src"));
observer.unobserve(change.target);
}
});
});
document.querySelectorAll("img[data-src]").forEach(function(img) {
observer.observe(img);
});
}This means that if JavaScript hasn’t loaded yet or failed somewhere, these avatars would stick with the default image I’ve specified—I’m okay with that.
I also added a little check to skip the load if the Save-Data user preference was enabled.
Bonus: Details
The other great thing about using IntersectionObserver is that if the images aren’t visible they aren’t loaded. For example, I hide Replies and Mentions inside of closed <details> elements.
1 REPLY
-
TOTAlLy GOnNa STeAL THiS foR MY BLOg 😉#
If <details> is supported by the browser, the avatar images will only load on demand when the user expands <details> to show the content! I love it. And if <details> is not supported the avatars are lazy loaded just like any other content.
25 Comments
@zachleat
Ha! My mom tells me that all my posts are cool
@nystudio107
How are you doing the Twitter likes / etc. with the facepile to begin with? It appears that you're indirectly using webmentions.io?
@zachleat
Yeah—I wrote a little about it here: zachleat.com/web/snarky/
@kleinfreund
Should I webmentions?
@zachleat
I think they are ace, yes—but I have had a social hole on my website ever since I deprioritized and eventually removed disqus
@nhoizey
I had the same issue with 119 webmentions on nicolas-hoizey.com/2015/02/viewpo…, and tried multiple solutions already, but I think yours might be the best yet, I'll have to try it, thanks!
@nhoizey
Don’t you think we could move the saveData test outside the observer, to test only once per page load?
@zachleat
I thought about that, yeah. But I wanted it to work if the user opted in to Save-Data after page load but before scrolling down. An incredibly small detail 🤷♂️
@CodeFoodPixels
I just snooped the repos, the avatar-local-cache stuff is pretty neat! I'm already resizing stuff on the LeedsJS website, but doing the deciding between formats is pretty nice! Eleventy Open Collective Zach Leatherman Zach Leatherman
@zachleat
hey no peeking! 😎 Luke Bonaccorsi 🏳️🌈 Eleventy Open Collective
@CodeFoodPixels
🕵️ Eleventy Open Collective Zach Leatherman Zach Leatherman
@JeremieCarlson
Possible SEO impact?
@zachleat
of not loading the images?
@JeremieCarlson
Ah probably lack of context on my part. I thought you were hiding the webmentions by default and I had a thought that those links would be good for SEO and wondered what the impact might be
@briankardell
facepile facepalm 🤦♀️
@tomayac
I read this and immediately checked my Web mentions code. Past me actually was smart enough to stick `loading="lazy"` on the avatars (self high five); I had just missed the fallbacks. Fixed in github.com/tomayac/blogcc…. Thanks for sharing these stories (both Zach and Bri… Truncated
@zachleat
Excellent!
@darek_kay
Almost two years after Zach's post, loading="lazy" has now good browser support (73%). Best trade-off between effort (adding a single attribute) and gain. Bonus: no JS required.
@ambrwlsn90
True, although I think I'm more up for the default hiding of the images until the person decides they wanna see them 🙂
@fluffy
Oh dang I should add this to webmention.js (especially the save data pref)
@mxbck
did something similar on my site - show just 5 lazyloaded avatars and reveal the rest only when requested 👍
@AtilaFassina
yeah, I think that's the best approach. I removed mine for now because UI just got waaay too cluttered (and useless, tbh). But it's in my backlog to do something like that too!
@mxbck
yeah not sure what the DSGVO says about this. Technically I'm getting them from webmention.io, which does the caching of twitter avatars on their end... I do have some text in my privacy policy about it though. No idea if it holds up in court. 😅 mxb.dev/privacy/