rgadellaa’s avatarrgadellaa’s Twitter Archive—№ 8,459

                    1. Apple Music vs Youtube Music on the web. I ran Lighthouse in Chrome twice for each site in desktop mode. Scores: AM: 23 and 22 / 100 YTM: 60 and 53 / 100
                      oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
                  1. …in reply to @RGadellaa
                    On mobile, AM gets a higher score than YTM: AM: 9, 17 and 16 / 100 YTM: 11, 10 and 10 / 100
                    oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
                1. …in reply to @RGadellaa
                  Let's look at desktop first. AM is pretty fast getting a First Contentful Paint onto the screen: 0.7 seconds. YTM is slower: 1.6 s. AM takes longer for the Largest Contentful Paint: 6.8 vs 2.8 seconds. AM also takes a lot longer to become interactive: 7.1 for AM, 3.1 for YTM.
              1. …in reply to @RGadellaa
                AM seems to have a very slow responding server: almost 4 seconds. This is the browser just waiting for something to happen. Preloading some of the requests (fonts, javascript) would probably also help a lot.
                oh my god twitter doesn’t include alt text from images in their API
            1. …in reply to @RGadellaa
              I also noticed that the site has a lot of resources that need better cache policies. Many of the javascript files have a TTL of under 1 minute. They seem to have a hash in the name so this seems to be a waste.
              oh my god twitter doesn’t include alt text from images in their API
          1. …in reply to @RGadellaa
            Over at YTM: they have render blocking assets. I see a font and some javascript files. One of those is over 700 kb - and render blocking at that. Ooof. Do they really need that entire script in place before loading the html? Can they split it and defer the non-essential?
            oh my god twitter doesn’t include alt text from images in their API
        1. …in reply to @RGadellaa
          Ah. The body of the page is pretty much empty. Looks like that 700 kb javascript file is responsible for the content. Makes some sense, as the content is dynamic, unique for each user.
      1. …in reply to @RGadellaa
        But why make it render blocking? It should be possible to have a splash screen - something! - and wait for that script to finish loading.
    1. …in reply to @RGadellaa
      Anyway. I see one request that is marked for preload, looks like the main css file. The request is initiated that 700 kb script. My guess is that they detect webp support and load the appropriate css file; that makes preloading difficult.
  1. …in reply to @RGadellaa
    I think I may know why YTM performs okay on desktop but tanks on mobile while AM performs roughly the same on both platforms (which is badly, but on mobile it's better than YTM, at least).
    1. …in reply to @RGadellaa
      AM has a FCP at 3.2 seconds which is ok. YTM takes 7.5 seconds - and that's probably because it needs to load that 700 kb file, parse and execute it before it can do so. On a mobile connection and processor.
      1. …in reply to @RGadellaa
        Funny thing is, YTM does manage rendering the page and being interactive way before AM does; 13.6 seconds, where AM takes pretty much double: 26.6 seconds.
        1. …in reply to @RGadellaa
          Well. This has been fun. Note: I was logged in on both services and tested the main entry point ('home' screen). I did have some extensions that were influencing the results.