13 replies

1. Private reply 4 min later
   1. Zach Leatherman 14 min later

      *arms wave wildly*

   2. Duffeh 2 days later

      They do a lot of rubbish like this as a part of their new framework sadly.

      The initial html the LCP image likely has loading='lazy' and in JavaScript they will change it to loading eager to make lighthouse "happy".

      Adobe is just a perfect example of what not to do.n

      1. Michael 2 days later

         For as long as we've had web technology some people have been desperate to use something, anything else

2. Charity Gamble 4 min later

   I mean, it *is* Adobe. Everything they do is slightly awkward, kinda weird...

3. Álvaro Martín Crespo 15 min later

   Correcto, el script inserta dinámicamente un `<link rel="icon">`. Si solo necesitas un favicon estático, usar la etiqueta en el HTML evita esa carga extra. Para cambiarlo en runtime, crea o actualiza el `<link>` con un nuevo href (añadiendo un cache‑bust). #frontend

4. Private reply 1 hr later
   1. Zach Leatherman 1 day later

      objection!! 😅

5. thunk.morphism.id 23 hr later

   All I can think of is that it allows for a unit test

   1. Zach Leatherman 1 day later

      what are we testing there

6. Zach Leatherman 2 days later

   ah, so I hadn’t realized that adobe.com was client-rendered www.speedlify.dev/site/www-ado...

   I added a warning in speedlify2 for that.

   1. Duffeh 2 days later

      Yeah it looks to be what Adobe claim is the "future of frontend" called EDS, which is a client side render, for pages that could be static generated.

      They talk a lot about perfect lighthouse score, at what seems like a cost to real users. The header is a tell they load that last for some reason.

      1. Zach Leatherman 2 days later

         Huh. 😬