MIT Creates Algorithm That Speeds Up Page Load Time By 34% (softpedia.com)
An anonymous reader writes: MIT researchers have created an algorithm that analyzes web pages and creates dependency graphs for all network resources that need to be loaded (CSS, JS, images, etc.). The algorithm, called Polaris, will be presented this week at the USENIX Symposium on Networked Systems Design and Implementation conference, and is said to be able to cut down page load times by 34%, on average. The larger and more resources a web page contains, the better the algorithm's efficiency gets -- which should be useful on today's JavaScript-heavy sites.
I got first post!
Now, the next logical step is to have this algorithm analyze the actual scripts and figure out a way to convince the various malwares that they've been loaded satisfactorily even though they haven't. That way you could avoid downloading almost 99% of modern web pages.
I have something kinda like that its called No Script.
would still be cooler if there was no 'dependency graph' of dynamically loaded resources behind my every HTTP request.
CLI paste? paste.pr0.tips!
They would all load a lot freaking faster if they would stop designing them with multiple, stupid, scrolling, 20 megapixel background images and dozens of megabytes of irritating javascript "special effects". Just saying.
>> Algorithm That Speeds Up Page Load Time By 34%
It's called AdBlocker
disable javascript.
Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
Vulcanising and HTTP2 Push are the way to go.
Allthough I do wonder if this method then still has a chance of improving a sites performance.
Personally I'd say well and automatically curated HTTP2 Push and automated minifying and compression are probably the best method overall.
I do doubt that this method could improve much more if that were in place.
But I could be wrong.
Does anyone have experience with http-push and perhaps some insights to offer?
Please comment below. Thanks.
We suffer more in our imagination than in reality. - Seneca
Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
You forget -- those ads would be 34% faster, too ... so you could get 51% more ads in the same time it took to serve the original bloated page.
Build it, and they will come^Hplain.
Not having 14 scripts be needed to post a comment, not having 8 other scripts clogging the pipes for one advertisement, 6 scripts for tracking you, and multiple other scripts for whatever reason.
Nor having a giant, moving graphic as the base part of your page which can't be turned off, menus which bounce up or down when you hover your mouse over them, or needing to have the latest and greatest browser so you don't miss out on the latest and greatest "features" of a site.
But no, finding an algorithm to speed web page loading is what we should concentrate on.
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
What's your download speed? I can browse most of the web pretty painlessly
We are now only discovering the terrible price of web standardisation and brower stability.
Web design was a lot simpler when the lowest common speed was a 56K dial-up. Now that everyone is connected to the Internet with a fire hose on the last mile, most web designers don't even stop to optimize their pages.
http://www.wonder-tonic.com/ge...
http://hampsterdance.com/classics/originaldance.htm
Oh, that's already well in progress.
Seems like all those IE6-only intranet websites are finally fading from existence.
I went and actually read TFA. It seems all they've done is create a bastardized version of a less efficient SPDY/HTTP2 protocol fetching system. Essentially, they're trying to solve a problem that is already solved, but the existing solution is already faster, more efficient, and more well thought out in general.
Here is a good example: https://http2.akamai.com/demo
Identify the advertisements client side and don't load them. Speeds up loading and rendering pages a lot.
I guess the browser-side performance isn't so much what they're talking about (rather, reducing network round-trips), but still, I have always wondered why we're still sending xml and js, plain or gzipped, rather than sending compact binary formats.
EXI is a W3C standard; it's more compact than gzipped xml and it's more than a dozen times faster to parse.
Rather than coding in JS all the time, lots of people are using javascript as an intermediate representation or bytecode. This is tremendously inefficient.
Though the WebAssembly effort sounds like people are finally realizing they need to address the problem, it sure seems like they're approaching it from a rather odd angle. asm.js and pnacl don't necessarily seem like where one should start if one has the freedom to design a new IR.
Sweet, now I can bog down my sites with more eye candy, and the users won't notice a slowdown.
The download speed isn't the problem. The rendering speed isn't even the problem. The problem is multiple DNS lookups and TCP/IP setup/teardowns for craptons of, well, crap that add no value to the content in the first place.
Web "developers" need to stop fucking around with the latest framework and just build a http://motherfuckingwebsite.com/, and if that's not good enough, they can just build a http://bettermotherfuckingwebsite.com/.
In an effort to regain love of your brand, can we please link directly to the relevant news site and paper (when not paywalled), and not some third-party site that has no value-add?
- http://news.mit.edu/2016/system-loads-web%20pages-34-percent-faster-0309
- http://web.mit.edu/ravinet/www/polaris_nsdi16.pdf
The dependency graph for weather.com alone in the actual paper would lead to a much richer discussion upfront in the comment sections.
EDIT: captcha - euphoria
OK. http://codepen.io/anon/pen/yOO...
...which is exactly what every popular CMS does...
BeauHD. Worst editor since kdawson.
...which is exactly what every popular CMS does...
The Joomla! CMS took six seconds or longer to load itself before displaying a dynamically-generated page on one of my websites. After I converted the website to static pages, each page loaded in less than five seconds. More tweaking is needed to reduce the load times. The average Internet user has an attention span of a goldfish (i.e., six seconds or less).
Hey, Spartacus, put your name to this post, it's the most beautiful thing I've ever seen! Fuck scripting, just write the motherfucking content! I've only been saying that for the past twenty fucking YEARS!
Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
I still write for dialup because I want page loads to take 0.01s, not the what 15 SECONDS that Facebook takes on 200Meg wired fucking BROADBAND? It seriously takes the piss, and I'm still trying to figure out what takes fucking Wikipedia so long to load when I run a WM instance on a dual core netbook and with 380GB of content it's still INSTANT.
Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
But people don't like frames being used.
Frames are so 1990-ish.
One place I was at was looking at implementing a new CMS and at one meeting we were discussing the options for the architecture of the system. I was from the maintenance group and was there to provide feedback because we would be looking after it long term. I was in favour of having the system generate static HTML pages whenever a change happens (something the software supported and that we saw another department implement) because it would reduce the hardware required for serving the site. Well, we had the servers already so it would allow us greater capacity with what we had. Also if the CMS goes down the site still is live.
Anyway I promptly got told that I didn't know what I was doing because it was much harder to generate the static HTML than to create the pages dynamically. I've always wondered why that was because the static HTML was exactly the same as what was going to be sent to the user as what was dynamically generated. I didn't stick around to ask because the first question I would have asked the head software architect was how he would have known whether what I was doing was right or wrong because after a couple of years of cleaning up his messes he certainly was qualified to tell.
They may support it but not every site generates static pages and shows them. Many create their content dynamically even if it would be more efficient to use static pages.
Also if the CMS goes down the site still is live.
I got tired of hackers beating down the doors of the CMS and occasionally crashing the website. After I converted the website to static pages, the hackers went away because there was nothing to hack.
I may be missing the "satire" here but Line-Width, seriously? I shouldn't have to scroll vertically to read your text because you've made a stylistic decision to limit the viewable area to 60-80 characters.
Surely that's the responsibility of a window manager to adjust horizontal width?
*whoosh* ?
I agree that the first site is better. And what's with the second site being gzip-compressed; whether my browser (Links) supports it or not. I see the same thing with the Playstation 3's browser as well.
Daniel Klugh
Comment removed based on user account deletion
Mosaic?
Browsers don't have enough trouble properly dealing with all the JavaScript that web sites shove down out Internet connection now. How nice that you've found a way for web sites lard up their pages with even more of the stuff.
CUR ALLOC 20195.....5804M
We did we do that?
To be fair, those cat pictures were pretty distracting.
All I can say from my own experience as a web developer is that I'd much rather have a human readable format (JSON) than a binary format. It is invaluable when debugging problems.
I'm on your lawn, fuck you.
The OP really does have a very valid point.
I use FF with adblock, noscript and ghostery installed and my browsing is lighting fast. On my, currently unrooted nexus 6p, I have Chrome and no real means of blocking ads or scripts, bar disabling javascript entirely. The difference between browsing with no ad / script filters is appalling. I've come across many websites I'll just terminate because they load so much shit. Once I make my RMA claim I'm rooting and installing an adblocker.
Their next project should be an algorithm which converts pages with "scripting junk" to plain nice HTML which can be readable by any browser.
Sure they do. Designers now make their pages behave like "apps" with AJAX everywhere, loading content on demand to reduce overall traffic!
Of course, the actual effect is that the "Back" button and all other standard navigation breaks, URLs don't update, scroll bars get fucked up, direct links are impossible, and browser memory usage balloons, making the site feel more like a Flash-based page from the 1990's.
Not (apparently) having learned anything from the switch to digital tv broadcasting (where the higher bandwidth was not used for better quality, but was co opted to shovel more channels of low quality shit) this "34% faster" algorithm will simply result in web coders programming at least 34% more crap ads and scripts into web pages.
-Styopa
We'd need far less Javascript if they just implemented and tags in HTML. The need for them has been apparent for well over a dozen years.
Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
Google has been working on a new compression scheme where the dictionary is fixed and stored in the browser. It makes sense since a lot of HTML and Javascript is highly repetitive and would likely be selected for inclusion in the dictionary by gzip anyway. You can even optimize Javascript to be more compressible under this scheme.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
I only use chrome on PCs. On the phone where chrome doesn't support extensions (like adblockers) - I used FF with ABP instead.
Unicode killed the ASCII-art *
For binary XML, as well as for the various fledgling binary json or binary yaml formats, the binary representation can be quickly converted to a plaintext one that has basically only minor formatting differences from the original. (I was about to say "to a human-readable one that..." but that's a stretch for a lot of XML.)
An AST / IR / bytecode is decompilable; e.g. from what I understand LLVM can do a good job of translating its IR back to C. Obviously a lot more information that could help with human comprehensibility is lost in that process than in the cases above. But decompiled IR can be as readable as minified JS source code is.
Of course, even without using any of these, what's sent over the wire is usually not human readable anyways, it's just that the tools to translate these other formats back to plaintext are higher-level than gzip is.