Live data from Hacker News

I am a fast webpage

varvy.com

181–190 of 292 posts

Re: I am a fast webpage

#181
post #168

Earlier quoted context omitted.

the guy says he's not an idiot then brags about spending $30 per month on a VPS (idiot), for a single-page static HTML website with all inline-code (idiot+1). It's not being negative to point out the glaring flaws in a person's statements. My assumption is the entire thing is an advertisement for that hosting service.

Where does it say that the VPS is used only for that one page?

It doesn't. It isn't. It appears that there are other projects hosted on the same site. Btw, the pages load quickly.

Re: I am a fast webpage

#182

OP has certainly nailed Hacker News psychology. My old coworker called the technique "inferiority porn." Titles like "the secretly terrible developer" or the closing statement of this particular article: "Go away from me, I am too far beyond your ability to comprehend." As many people have pointed out there are faster methods of static hosting through a CDN, and many of the techniques of this site are inapplicable fo…

I probably sound like I'm tooting my own horn but it definitely felt really contrived to me. I upvoted it because of the comments containing better tips or caveats provided for the good ones.

Re: I am a fast webpage

#183
post #127

Earlier quoted context omitted.

> This benefit is lost very quickly so there's only an advantage > for large numbers of very tiny individual images. In which case maybe it would be better to use sprites?

I don't know, I hate dealing with sprites, it just not worth it in my opinion, the time you spent on every edit...

If you're using photoshop you can create a PSD that sources other PSDs and if I remember right create an action that generates the exported image so you could automate things quite a bit if not entirely.

Re: I am a fast webpage

#185
post #102

> I make no external calls, everything needed to load this page is contained in the HTML. Wont that make your webpage load slower?

That one file, but presumably it's loading assets that would be the same total size if they were split. Loading 100k from one source is faster than the same aggregate size from multiple connections.

Re: I am a fast webpage

#186

I hate to be negative, but what really is the point of this? That a simple webpage without any content can be fast? Of course it can. Is it desirable to inline your CSS, "like a boss?" Maybe if you have one single web page. What if you have dynamic content and your users intend to browse more than one page? With externalized CSS, that is all cached. Same with images. If I'm building a web application, I certainly do…

With the affiliate link to the VPS host, it's essentially just a marketing page.

Re: I am a fast webpage

#188
post #102

> I make no external calls, everything needed to load this page is contained in the HTML. Wont that make your webpage load slower?

That one file, but presumably it's loading assets that would be the same total size if they were split. Loading 100k from one source is faster than the same aggregate size from multiple connections.

Except if you only need the first 50k to render the page, and can wait for 50k of Javascript to come later, your page is going to display a lot faster. Standard technique.

> Loading 100k from one source is faster than the same aggregate size from multiple connections.

Usually doing things in parallel is faster than doing them serial. That's why HTTP2 loads slower than HTTP1 - you are sucking everything through single TCP pipe, even though it is multiplexing within.

Re: I am a fast webpage

#189

A good sequel to http://motherfuckingwebsite.com/ , which is probably too understyled for most people.

I prefer http://bettermotherfuckingwebsite.com/

For some reason, I'm a fan of this one: http://codepen.io/dredmorbius/full/KpMqqB/

Re: I am a fast webpage

#190
post #33

Earlier quoted context omitted.

> Is this image inlining thing something new? No, it's been around since forever. Just not used terribly often. > Am I reading it correctly that the images are encoded in base64 and delivered as html? Surely this is a bad idea... no? It depends. Making a new request to fetch the image always has overhead. Whether that overhead is bigger or smaller than the overhead of base64-encoding the image depends on: • file size…

Completely offtopic, but how do you type •? I like it.

• is Option-8 on a Mac.
Post reply on HN