• 0 Posts
  • 2 Comments
Joined 2 months ago
cake
Cake day: September 12th, 2026

help-circle

  • As of right now, this is the response they serve. It’s 713 bytes (excluding HTTP headers):

    $ curl example.com
    <!doctype html><html lang=en><head><meta charset=utf-8><link rel=icon href=data:,><meta name=viewport content="width=device-width,initial-scale=1"><title>Example Domain</title><style>html{color-scheme:light dark;background:light-dark(#eee,#222)}body{font:16px/1.6 system-ui,sans-serif;max-width:30em;min-height:100vh;margin:auto;padding:4.75em 2em 20vh;box-sizing:border-box;display:grid;place-content:center;text-align:center}</style></head><body><p>This domain is for use in documentation examples without needing permission. This is not a service, avoid relying on it for testing and monitoring purposes.</p><a href=https://iana.org/help/example-domains>Learn more</a><script src=/s.js></script></body></html>
    $ curl -s example.com | wc -c
    713
    

    If their primary objective is cutting bandwidth, then I’d suggest something like this (274 bytes after removing unnecessary whitespace):

    <!doctype html>
    <html lang=en>
    
    <head>
        <meta charset=utf-8>
        <link rel=icon href=data:,>
        <meta name=viewport content="width=device-width,initial-scale=1">
        <title>Example Domain</title>
    </head>
    
    <body><a href=https://iana.org/help/example-domains>Understand this page</a></body>
    
    </html>
    

    The link is already part of the page now, and all real users can just click it to understand the page; the information is all there already.


    score 1 · canonical