512KB Club
512kb.club
The 512KB Club is an exclusive list of web pages weighing less than 512 kilobytes.
  • htrayl@lemmy.worldEnglish
    421·
    4 hours ago

    A small critique of that project - a large portion of the websites included are simply personal sites for developers - nothing barely more technical than a business card or CV. I would exclude those or categorize them differently, as to me their “usefulness” seems relatively edge case.

    • Taldan@lemmy.worldEnglish
      7·
      2 hours ago

      I clicked on 6 sites

      • 4 were personal portfolio sites

      • 1 was a personal blog

      • 1 was a web design company

      Pretty disappointing, and I’m not going to keep clicking on more in the hopes I find something interesting

    • unexposedhazard@discuss.tchncs.deEnglish
      23·
      3 hours ago

      They are useful for those people though. You can put a QR code or URL on your business card and it will give people all the information they need for your businessor something.

      • ripcord@lemmy.worldEnglish
        1·
        1 hour ago

        I don’t think anyone is arguing that having, like, websites are useful. But if they’re not particularly interesting then it doesn’t really fit here.

        The point of something like this is generally to come up with interesting/creative/useful things within arbitrary resource limits. Not just a bunch of really really limited boring stuff.

  • tedd_deireadh@lemmy.worldEnglish
    7·
    5 hours ago

    That’s a pretty cool site. I always wanted to set up my own simple, html page for a personal blog. Lots of inspiration in these pages. Crazy there’s functional web pages less than 2.03KB in size.

    • cmnybo@discuss.tchncs.deEnglish
      13·
      4 hours ago

      It’s not hard to make a useful website that’s small. You just have to avoid using javascript libraries and keep images to a minimum. There are a number of static web page generators if you don’t want to write HTML yourself.

      Keep in mind that a 50 kB page is about a 15 second load on a typical dial-up connection. Before high speed internet, almost everyone kept their web pages small.

  • dual_sport_dork 🐧🗡️@lemmy.worldEnglish
    44·
    2 hours ago

    First of all, I take a bit of umbrage at the author’s constant reference to “website size” without defining what this means until you dig into the FAQ. Just blithely referring to everything as “size” is a bit misleading, since I imagine most people would immediately assume size on disk which obviously makes no sense from a web browsing perspective. And indeed, they actually mean total data transferred on a page load.

    Also, basically all this does is punish sites that use images. I run an ecommerce website (and no, I’m not telling you lunatics which one) and mine absolutely would qualify handily, except… I have to provide product images. If I didn’t, my site would technically still “work” in a broad and objective sense, but my customers would stage a riot.

    A home page load on our site is just a shade over 2 megabytes transferred, the vast majority of which is product images. You can go ahead and run an online store that actually doesn’t present your customers any products on the landing page if you want to, and let me know how that works out for you.

    I don’t use any frameworks or external libraries or jQuery or any of that kind of bullshit that has to be pulled down on page load. Everything else is a paltry (these days) 115.33 kB. I’mna go ahead and point out that this is actually less to transfer than jabroni has got on his own landing page, which is 199.31 kB. That’s code and content only for both metrics, also not including his sole image — which is his favicon, and that is for some inexplicable reason given the circumstances a 512x512 .png. (I used the Firefox network profiler to generate these numbers.)

    • JustAnotherKay@lemmy.worldEnglish
      1·
      43 minutes ago

      Do you actually have to provide the image? Couldn’t you provide a pointer to the image? Like those thumbnails that are just links on the backends but appear as images when loaded

      • dual_sport_dork 🐧🗡️@lemmy.worldEnglish
        1·
        3 minutes ago

        If you’re going to display pixels on the user’s screen, you have to send those pixels to the user. Magic still doesn’t exist. HTML img tags are indeed a “pointer,” but once the user’s browser has the path to that image file it will download the entire thing.

        That said, there’s no reason to send an image that’s any bigger than it needs to be. Sending a scaled down thumbnail if you know it will be displayed small is sensible. Sending the entire 1200px wide or whatever image it is and just squashing it into a 100px wide box in the user’s browser is not.