A 2x Faster Web

Post by dkubb » Thu, Nov 12, 2009, 11:59 PM UTC

ryanwaggoner wrote: post #25

dkubb wrote: post #12

I love that Google is focusing on how to speed up the web, but they are missing the most obvious thing they could do that would have a dramatic impact on the speed of the web: Update their PageRank algorithm to take into account website speed, and then publish this as a fact. The idea would be that they would have GoogleBot measure the latency, and overall page load time and rank sites higher that respond faster, and…

This is a horrible idea. Yes, it would result in increased focus by some people on speed, but probably the same people who focus on "SEO". So now content relevancy has yet another adversary in the battle for SERPs. There's a LOT of really incredible, original content out there written by amazing people who do it in their spare time and don't give two shits about their SEO or the speed of their server, and now that co…

Post by MikeCapone » Fri, Nov 13, 2009, 12:24 AM UTC

EugeneG wrote: post #42

Wouldn't faster internet connections make this whole effort moot?

Post by Xichekolas » Fri, Nov 13, 2009, 1:42 AM UTC

neilc wrote: post #31

swombat wrote: post #7

Impressive, how Google are taking on challenges that pretty much no other company could possibly address... replacing email... enhancing HTTP, etc... They're the only company with the means to take on such massive, unprofitable projects, and at the same time enough street cred that everyone won't immediately assume they're trying to make the web proprietary. The fact that they tend to open up these things from the ge…

They're the only company with the means to take on such massive, unprofitable projects, and at the same time enough street cred that everyone won't immediately assume they're trying to make the web proprietary. They are hardly the only company doing this. Microsoft Research do a ton of pretty visionary / far-reaching work, much of which has nothing to do with MS-proprietary platforms. For example, the VL2 architectur…

Post by drusenko » Fri, Nov 13, 2009, 1:52 AM UTC

shykes wrote: post #11

shimon wrote: post #8

Am I missing their explanation of how a SPDY-capable client and server discover and make use of SPDY instead of HTTP? For this to take hold in the wild, it has to be possible for me to run a combined HTTP+SPDY server, and for a client connecting to it to automatically make use of SPDY if it is capable. This must happen without user intervention (i.e. we don't expect people to type spdy:// instead of http:// ). It see…

You could browse to the page the regular way, then load a Javascript or Flash library which would use SPDY for all further communications. In your typical web app the user experience could be visibly improved. You can already do this with Flash today, and it would be much easier for Google to push it into the DOM than to touch the transport protocol.

Post by ams6110 » Fri, Nov 13, 2009, 4:42 AM UTC

drusenko wrote: post #46

agl wrote: post #29

Earlier quoted context omitted.

We will.

Even so, the current certificate issuing process is lengthy and expensive. Requiring SSL would be a major hit to the mom-and-pop type websites that just want a simple webpage on their own domain for their business. They'd now have to pony up for an SSL cert, which at least doubles the website ownership cost, as well as potentially go through a very complex process to get the certificate issued. It also completely eli…