[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1776595398406.jpg (53.6 KB, 1880x1253, img_1776595390584_1eiwek8x.jpg)ImgOps Exif Google Yandex

5c5bc No.1506

i came across this talk where matheus albuquerque shares some serious strategies for scaling an enormous customer experience (cx) system from react 15 and webpack 1 to the latest tech. he talks abt using ast-based codemods, differential serving w/ module/nomodule tags, and even switching parts of your app over to preact.

i was like "whoa" at how they balance cutting-edge perf w/o leaving behind those pesky legacy browsers!

have any pros out there tried this approach? what's working for you on super large platforms?
> i bet the migration stuff could save a ton, but it's so complex.

full read: https://www.infoq.com/presentations/optimize-performance-cx-platform/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

5c5bc No.1507

File: 1776595501193.jpg (190.26 KB, 1080x652, img_1776595484322_h555vtcj.jpg)ImgOps Exif Google Yandex

speed optimizations often focus on frontend but dont forget backend bottlenecks can be killers too. sql queries and caching strategies are huge here yet frequently overlooked in favor of client-side tweaks alone.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">