Black Friday '14: E-commerce Pages Far Slower Than They Were in 2013
An anonymous reader writes Black Friday news kicked off this weekend quite early when Best Buy was hit with a massive outage, but it turns out that was only half the story. The top 50 e-commerce websites were slower overall this year compared to last, suggesting customers were frustrated even if they could get to their favorite shopping site. Web performance monitoring company Catchpoint Systems looked at aggregate performance this weekend and compared it to the same timeframe in 2013. The results are notable: desktop web pages were 19.85 percent slower, while mobile web pages were a whopping 57.21 percent slower.
I don't think a big screen is worth dying for.
I think it's because FIOS, U-Verse, and Google Fiber all had good years worth of picking up subscribers, so customers want their pages faster and the server-side people didn't upgrade.
Or maybe its because the ecommerce sites didn't pony up protection money to AT&T, Comcast, et al, so they all ended up stuck in the slow lane.
Perhaps if those webpages were not laden down with masses of Javascript, doing who knows what, the pages would be faster to load. All that Javascript has to be downloaded from a server somewhere and executed in the browser. It all takes resources.
Many website developers today seem to think that his/her web pages only need to load on the fastest computers as the sole page open in the browser. I think of them as "greedy" websites, because they are greedy with the end-users' compute resources.
The real "Libtards" are the Libertarians!
Instead, we need database technology that is new hat. This database technology already exists, and they're called array databases.
Array databases are web scale!.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
More of the coding needs to be server side or not exist at all.
The worst is the ads. I turned on NoScript and so many pages just fly now because the stupid javascript isn't allowed to run.
I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
FTFA:
Median webpage response times for desktop websites for the entire group (aggregate) was 3.991 seconds, compared to 3.330 seconds in 2013.
Do people even notice that? I mean, if I'm getting what I think is a great deal and it takes literally a fraction of a second more for the page to load I don't think I'm going to care.
what would you store this array on?
A key-value filesystem such as ANY DISK BASED FILESYSTEM??
Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
Page load times are down because pages are loading so many more tracking options and some of them are very abusive on the javascript engines. If you turn on the status line (even if you can as it is gone in some modern browsers), you will often see it saying "loading 159 out of 162" and those last ones never load. There is also something that is related to a compounding latency problem that many developers don't think about it because they don't see it when they are developing the platforms and modern tool kits help to hide it from developers too.
I guess people don't like IBM's old work on the subject that showed dropping a 3 second response to just 2 seconds resulted in substantial improved efficiency. Maybe marketing groups need to understand that a customer stuck on a slow site is a bad consumer.
All of the ISP's have NOT upgraded their backbone for years, they are now overselling it by never before seen levels making even 500Gb Cable Internet feel like DSL.
The problem is people are not screaming about it to their congress critter forcing ISP's to deliver what they sell. They need to pay a $1000 per user per month fine for not delivering what they promise or advertise.
That would get the lazy executives at Comcast moving.
Do not look at laser with remaining good eye.
If the data is in cache, it is faster to open a file, read the data in as a text file, do a linear search, process the data, close the file than it is to just do a connection to an sql server. Most online stores are selling so few products that their entire product database should fit in L1 cache. If you want fast, make sure everything that has to be run can live in L1/L2 cache except what has to be be written out. Modern file systems are very good at writing out small files quickly without making the person in front of a screen wait.
No we havent. ISP's still heavily oversell.
at 8pm on a friday, I can not get more than 13mbps. I pay for 25mbps. Friends pay for 50mpbs and they cant get more than 13.
ISP's are still dramatically oversold.
Do not look at laser with remaining good eye.
This is part of it, yes.
The fundamental problem is you have loads of ecommerce sites that were built as turn-key solutions and handed over to an "admin" for the company. They can start creating their own content to add to the site, so they start searching for things to add to their site. They find snake-oil dealers that offer them everything in exchange for a small script element inserted into the DOM.
Additionally, the admins haven't taken the time to learn how to save images for the web properly, and they serve a 900x600 image that's a handful of MBs (x6 for a simple slideshow).
Between the excess of HTTP requests added by the tracking scripts and the excess of MBs being downloaded for images / video, it is not a surprise that ecommerce sites are getting slower. I would expect this trend to continue to some degree.
Someone flopped a steamer in the gene pool.
I can vouch. I had an eshop in 2000 which carried over 3,000 products (RPG merch), I fit the lot, including images, onto a zip disk. The text portion (basically all that was in the database, the images were stored on the filesystem) fit on a floppy. Or, in the case such as mine that I had my own server on a colo backbone, loaded onto a RAM disk. Holy shit, that was one (relatively speaking) quick server.
Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
or its because so many e-commerce sites are now hosted on the "cloud" rather than their own servers in a datacentre.
Amazon created their cloud as they had lots of spare capacity in the off-peak so thought it'd be a good idea to sell it to businesses that would use it when the holidays were not on, and Amazon would use it for consumer ecommerce when the holidays were on.
But now, both Amazon has sold its capacity to ecommerce places who need it when Amazon needs it... hence slower sites. I'm sure the same could go for Azure, too little capacity oversold.
except you don't need even that much to surf a web site. virtualization is the problem. all the servers are oversubscribed to use every little bit of RAM and CPU so the bean counters can cream their shorts with higher return on asset ratios
i could surf netflix and youtube just fine over the weekend. amazon was as fast as usual. but toys r us and best buy were like watching trees grow and toys r us store inventory checker was broken
I've noticed a number of sites are hosted on some kind of content management platform, presumably aloft in the Cloud. Sometimes there's a noticable delay in getting the page to load.
That's just DBA 101, "always buy more RAM".
putting the 'B' in LGBTQ+
I am glad you posted that. I am putting together a little project I call Distributed Integrated Scalable Array Database, DISArray. It will be a shardable web scale instantly consistent DB engine which will have kick ass performance and a Heisenberg query engine support by a look ahead design I have code named "Schroedinger".
Now all I need a is cool mascot and I will be well on my way to becoming a bazillionaire. Zuckerberg better watch out! Look for it on GitHub.
putting the 'B' in LGBTQ+
The real issue is uninformed cloud bashing comments. They are so numerous nowadays that they clog the internet pipes and prevent ecommerce traffic to go thru.
lucm, indeed.
I am glad you posted that. I am putting together a little project I call Distributed Integrated Scalable Array Database, DISArray. It will be a shardable web scale instantly consistent DB engine which will have kick ass performance and a Heisenberg query engine support by a look ahead design I have code named "Schroedinger".
This is going into my next system proposal to management.
'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
The fact that slashdot on it's own requires 10.5mb in freaking Javascript is the other part of the problem.
Low quality web designers that cant figure out how to do something without 600 pounds of "libraries"
Do not look at laser with remaining good eye.
I think it's because FIOS, U-Verse, and Google Fiber all had good years worth of picking up subscribers, so customers want their pages faster and the server-side people didn't upgrade.
It's because every web page wants to load a metric fuck-ton of third-party Javascript and Ajax code from 10 different sources - just to display their banner and navigation panels ...
It must have been something you assimilated. . . .
"Black Friday" has been happening and advertised since 1 Nov. Friday Nov 28 just happened to be one day in the stream of pseudo sales between 1 Nov and 15 Jan.
You sound like a guy I work with.He turned isolation level down to dirty reads and believes it will have no effect on relational integrity. It is already causing problems with programs picking up items to work on that are not in the correct status. He believes we can solve all these problems by rearranging code. However, if A and B both must happen for a transaction to occur, I don't see how doing B first instead of A but not doing it as a transaction is somehow going to fix the problem. What if you do B first and A blows up? Now you have data that is out of synch.
If you are not allowed to question your government then the government has answered your question.
I gave up browsing at some point, it was so bad. Amazon was a bit slow but worked OK.
thegodmovie.com - watch it
I don't know how this got moded up, it is nonsense. Most tracking happens post load/post interactive, and someone saying, "looking at your status line" is a telltale for this person not having a clue about website performance opt. I get this from JS devs and PM's all of the time, and I really do have to prove that the 1M of badly optimized images is more the problem.
hey there APK... :-)
I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
It's because every web page wants to load a metric fuck-ton of third-party Javascript and Ajax code from 10 different sources - just to display their banner and navigation panels ...
Sounds right to me. All I know for sure is that today's web has managed the rather remarkable feat of mostly being slower in use than Compuserve was in the early 1990s with a 1200 baud modem. And that's AFTER blocking about 16000 nuisances in /etc/hosts. Our EEE PC's where I don't currently have a hosts file, have become pretty much unusable in Firefox. My esteemed spouse has come to blame Firefox for the situation and would probably advocate execution of the Firefox programmers.
Personally, I think the basic problem is that web site designers are often incompetent and almost universally nuts
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
Nope. As has been pointed out elsewhere, the loading of tracking code usually happens after the page has been rendered. This is because the tracking/analytics code doesn't want to affect the loading or delivery of the page, as they are used to measure that (amongst other things).
You appear to just be guessing...
That would make sense if Amazon only offered their Christmas-peak infrastructure, and no more. As that's not the case, your argument is nonsensical.
It's quite likely the cloud is helping, as now companies can fire up new servers and load balancers to deal with increased traffic in seconds, instead of quickly reaching the limit of their limited in-house, geographically-constrained infrastructure. These servers are located around the world, in places best suited to serve the increased load, giving a real benefit to the hosted sites and the users of said sites.
Or you can just keep on shouting "durrr durrr cloud! durr!" and show everyone you really don't understand how the internet works these days. That'll really help.
It's quite likely the cloud is helping, as now companies can fire up new servers and load balancers to deal with increased traffic in seconds
then why didn't they?
The cloud is just as resource-constrained as the old datacentres used to be, only shared across many customers. Its like all those customers joined together and put all their old servers into one big datacentre. "The cloud" doesn't magically increase the number of servers present, it just shares the load. Normally that's fine. But when everyone wants to use it all, all at once, even the cloud goes slow.
Isn't the index used to access the array a key value?
(disclaimer: opinions expressed do not necessarily represent my own...)
There's a whole new generation of JS devs who are complete slobs about dependencies. They will attach the entire Bootstrap library for one plug-in. I've seen libraries that embedded and minified it such that it wasn't even obvious they were using it and they weren't using it for much. 20 megabytes for a !@#$ing restful documentation widget whose own proprietary code was 20,000 lines long. It's just ridiculous. IMO, every client-side web dev should be forced to support IE6, then mobile, then write for the desktop browser. But people want the latest buzzwords, they want them fast and cheap and they want them now. This is what you get. A bunch of jr-level slobs writing e-commerce apps who knew what to say about how much they love these new frameworks at the interview.
Perhaps if you have real hardware for your data, and your data is static. But once you escape into the real world, you shouldn't be designing web applications that depend on L1 (or L2) cache.
I'd blame the Cloud
Casteism
If the network is hitting capacity, why would a network company want to invest in higher speeds, if the gov't is going to tell them how to run their network?
Those developers may very will need those fancy machines.
But whoever is doing usability testing should be testing on fast machines, slow machines, new machines, old machines, mobile devices, etc. If they're not, then they aren't doing the job properly.
Clearly you missed the twenty minute period on Friday in which amazon.co.uk was returning HTTP 502 error codes.
I guess they should've used some cloud servers to cope with the increased load or something, huh?