There are actually two interpretations of N/A:
N/A(not available): There is lost media so it can’t be evaluated.N/A(not applicable): The show is in sign language so evaluating that is outside the scope of this string-matching program.
Meanwhile, undefined seems to mean the value has not yet been evaluated. Maybe null is really the best.




















It’s 18 MB because it’s GIFs, about 16 frames each… at least the palette of is optimized by panel. There is some charm to the dithering as opposed to DCT (JPG/WebP block) artifacts. Also, she only started using WebP in 2021, it wasn’t viable much earlier. Technically, the static background and low-color foreground could be separated (JPG + GIF with very small palette, maybe rotated to compress streaks horizontally; too early for APNG) and overlaid with CSS to achieve about the same signal-to-noise ratio at about one half to one third the size. However, the noise would be different…
The falling drops that indicate loading of each image are very cool but I wonder if something similar, plus the fade-in of all images at once, could have been done with just HTML and CSS, broadening accessibility to noscript users.