Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you struggle with bandwidth, why not serving gzipped content? By response headers it looks like you are serving plain html.


Actually, it looks to me like the HTML response is the only thing that's gzip'd. It doesn't make sense to waste time gzip'ing the PNGs, but the CSS and JS files should definitely be compressed. (And maybe the fonts? Not sure.) The default `gzip_types` setting in the nginx config shipped by Debian/Ubuntu does include `text/css` and `application/javascript`, but not `text/html`. Could be that OP is using a non-distro config that only enables gzip for `text/html`, or that OP accidentally disabled gzip'ing for the other MIME types while enabling it for HTML.


Self-hosting and service 300kb for font files also seems excessive. Especially for a Helvetica clone.


Yep, that's why I am planning on getting rid of them completely. I did a quick test this morning, seems like removing references to the fonts from the theme and adjusting some font weights should do the trick.


I use type subsetting and only serve about 50kb worth of fonts (4 variants in total). 300kb seems excessive.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: