Monthly Shaarli

All links of one month in a single page.

October, 2017

"Why AMP?", Jeremy Wagner (@malchata) #AMP

"Google has all the ability in the world to reward and punish sites based on their performance without fracturing the web in the process."

"Netflix functions without client-side React, and it's a good thing", Jake Archibald (@jaffathecake)
thumbnail

"Netflix uses React on the client and server, but they identified that the client-side portion wasn't needed for the first interaction, so they leaned on what the browser can already do, and deferred client-side React. The story isn't that they're abandoning React, it's that they're able to defer it on the client until it's was needed. React folks should be championing this as a feature."

Seven into seven", Ethan Marcotte (@beep) #AMP #Governance
thumbnail

"When we’re evaluating technology, or discussing a particular strategy, we can’t give a project a pass because anyone can open a pull request. Instead, it’s worth asking ourselves Franklin’s questions: when a site adopts AMP, who benefits? And who, or what, assumes the risks in using AMP?"

"Quick Wins For Improving Performance And Security Of Your Website", Jonas Krummenacher (@jkrummenacher)
thumbnail

Let’s Encrypt (SSL)
HTTP/2
Brotli compression
WebP images
Content delivery network

"E-commerce : les sites leaders en France loin d’être performants", LSA Commerce Connecté #webperf #france
thumbnail

"C’est Amazon qui mène assez nettement les débats en étant la seule enseigne du panel à obtenir un Speed Index inférieur à 2 secondes (1895ms), suivi par Cdiscount (2375ms) et Booking.com (2599ms). À l’autre bout du classement, les 5 dernières enseignes (Castorama, Airbnb, Voyages-sncf, Carrefour et E.Leclerc) dépassent quant à elles les 6 secondes et E.Leclerc ferme la marche au-delà des 11 secondes… Soit une page plus de cinq fois plus lente à l’affichage qu’Amazon."

"We’re making accessibility clearer and easier", Alistair Duggin (@dugboticus) #a11y
thumbnail
"Bootstrapping Inclusion", Jason Wong (@attackgecko) #diversity

"A workplace where people of all identities and experiences are understood, appreciated, and fully included in the community and where equitable treatment and outcomes prevail."

"`appearance`, au service de nos formulaires", Raphael Goetter (@goetter)
thumbnail

"La propriété CSS appearance permet de modifier la mise en forme native du système d'exploitation, et notamment d'annuler tous les styles de base pour pouvoir les re-styler tranquillement comme souhaité."

"Can You Afford It?: Real-world Web Performance Budgets", Alex Russell (@slightlylate) #Budget
"ACME Support in Apache HTTP Server Project", Josh Aas (@0xjosh) #HTTPS
thumbnail

"We created Let’s Encrypt in order to make getting and managing TLS certificates as simple as possible. For Let’s Encrypt subscribers, this usually means obtaining an ACME client and executing some simple commands. Ultimately though, we’d like for most Let’s Encrypt subscribers to have ACME clients built in to their server software so that obtaining an additional piece of software is not necessary. The less work people have to do to deploy HTTPS the better!"

"Akamai Edge: Tracking the Performance of the Web with HTTP Archive", @rick_viscomi & @paulcalvano

Akamai Edge: Tracking the Performance of the Web with HTTP Archive

RFC 8246 - HTTP Immutable Responses
thumbnail
"How 3rd Party Scripts can be performant citizens on the web", Ryan Townsend (@RyanTownsend)
thumbnail
"Modern JavaScript Explained For Dinosaurs", Peter Jang

"We went from plain HTML and JS to using a package manager to automatically download 3rd party packages, a module bundler to create a single script file, a transpiler to use future JavaScript features, and a task runner to automate different parts of the build process."

"Web performance — A PoC by example", Pablo Henrique P. Silva (@pablohpsilva)

"After creating it I used it to learn some more about Webpack and Web performance in general. In this article I’ll show you everything I did to make the app load from 2690ms down to 170ms."

"The Web began dying in 2014, here's how", André Staltz (@andrestaltz)
"HEAD: a free guide to head elements.", Josh Buchea (@joshbuchea)
"Say “yes” to HTTPS: Chrome secures the web, one site at a time", Emily Schechter (@emschec) #HTTPS
thumbnail

"HTTPS is easier and cheaper than ever before, and it enables both the best performance the web offers and powerful new features that are too sensitive for HTTP. There’s never been a better time to migrate! Developers, check out our set-up guides to get started."

"Transpiled for-of Loops are Bad for the Client", Dave Rupert (@davatron5000) #JS #Babel
"#Webperf Choreography", Harald Kirschner (@digitarald)
"Améliorer l’experience utilisateur grâce à la perception de la performance", Stéphanie Walter 🦊 (@WalterStephanie) #UX

"You have optimized every line of code of your site / mobile application, used all the techniques at your disposal to have the fastest loading time possible. Yet, users still complain about the slowness. Let’s learn to use different design techniques and UX to work performance also at the level of user perception."

"Chromium Blog: Introducing the Chrome User Experience Report", Bryan McQuade (@bryanmcquade) and Ilya Grigorik (@igrigorik) #data
thumbnail

"The report is a public dataset of key user experience metrics for top origins on the web. All performance data included in the report is from real-world conditions, aggregated from Chrome users who have opted-in to syncing their browsing history and have usage statistic reporting enabled."

"Third parties are probably the fastest way to guarantee a slow site…" @csswizardry in a post by @oliverlindberg
thumbnail
"Cognitive Biases in Programming", Yash Ranadive (@evidanary)
thumbnail

"We can never completely eliminate our biases, by being aware of how it is affecting us, we can somewhat mitigate the problems it causes."

"The newest version of JavaScript only has 2 new features. Here’s how they work.", Tiago Lopes Ferreira (@ferreiratiago_)
thumbnail

Array.prototype.include() and ** operator.

"realprogress.js: Lightweight JavaScript library for accurate web loading progress.", Hristiyan Dodov (@hristiyandodov)
thumbnail

Lightweight JavaScript library for accurate web loading progress.

"lozad.js: 🔥 Highly performant, light ~0.7kb and configurable lazy loader in pure JS with no dependencies for responsive images, iframes and more", by Apoorv_Saxena
"Frontend Web Performance - better, faster, stronger", Stefan Judis (@stefanjufis) #slides
thumbnail
"Cache Busting Front-end Resources: Is File Name Revving Still Necessary?", Louis Lazaris (@ImpressiveWebs)
thumbnail
FOIT vs. FOUT demonstration, by @zachleat #fonts
Vanilla Framework, a simple extensible CSS framework written by the Ubuntu Web Team.
Tanaguru intègre le RGAA 3 2017 \o/ #a11y
thumbnail
Early Birds Tickets for SmashingConf 2018, dedicated to everything front-end performance.
thumbnail

"Performance matters. Next year, we’re thrilled to venture to London for our brand new conference fully dedicated to everything front-end performance. Dealing with ads, third-party scripts, A/B testing, HTTP/2, debugging, JAM stack, PWA, web fonts loading, memory/CPU perf, service workers. Plus lightning community talks."

"19 technical SEO facts for beginners", John E Lincoln (@sengineland). 1st? "Page speed matters".
"The meaning of AMP", Jeremy Keith (@adactio) #Governance
thumbnail

"That’s a particularly low blow, because it’s such a bait’n’switch. One of the reasons why AMP first appeared to be different to Facebook Instant Articles or Apple News was the promise that you could host your AMP pages yourself. That’s the very reason I first got interested in AMP. But if you actually want the benefits of AMP—appearing in the not-search-results carousel, pre-rendered performance, etc.—then your pages must be hosted by Google."

"Google's mobile-first index has rolled out for some sites…", Barry Schwartz (@rustybrick) #SEO

"It is unclear how many sites have already switched over to the mobile-first indexing process, but, when I asked Illyes to clarify what he meant by “a few sites,” he said a few relative to the Google index. So that could be quite a large number of websites."

"Vicissitudes", Ch. Raynaud (@chraynaud). Sommes-nous ou non dans une bulle de l'investissement #FrenchTech
"Fast By Default: Modern Loading Best Practices #ChromeDevSummit", Addy Osmani (@addyosmani) and friends
thumbnail
"Introducing Browsershot v3: the best way to convert html to PDFs and images" - Freek Van der Herten (@freekmurze)
thumbnail
"30+ diversity and inclusion activists and organisations I look up to", Karoline Szczur (@fox) #diversity
thumbnail

"I wanted to talk about a few individuals and organisations I look up to on a daily basis in the space of diversity and inclusion. The content they share can often be challenging, which is why it’s so important to expose yourself to different viewpoints promoting our growth."

"Why the Email Confirmation Field Must Die", Anthony (@uxmovement)
thumbnail

"It’s time to take a new approach on how you design the email field. The solution is not another field to fill out, but to give clarity to the existing field. Prominent placement, larger input size and a specific label are what you need. Make this change and kill the email confirmation field once and for all."

"Performing & Preventing SSL Stripping: A Plain-English Primer", Junade Ali (@IcyApril) #HSTS #Security
"Onload, Speed Index, Paint timings, TTI and custom metrics explained", @theystolemynick
"RTMP - Real Time Messaging Protocol Explained", Goran Čandrlić (@Chande)
"Wildcard Certificates Coming January 2018 [on Let's Encrypt]", Josh Aas (@0xjosh)
thumbnail
"Improving Performance with the Paint Timing API", Umar Hansa (@umaar) #UX

"The paint timing API enables website creators to track and monitor the important metrics which affects perceived performance. Consider that 53% of users will abandon a site if it takes longer than 3 seconds to load (source). Being able to keep your paint times low is likely to keep your users happy and improve the perceived performance of your site."

"Performance and Resilience: Stress-Testing Third Parties", Harry Roberts (@csswizardry)
thumbnail
"6 myths of Progressive Web Apps", Peter O'Shaughnessy
thumbnail