Slashdot Mirror
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.
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!
Jesus died for your sins. The least you can do is die for a TV. /sarc.
For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
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.
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.
Those Onion articles always crack me up. It's hilarious how close their satire comes to reality ... it's ... erh ... oh.
Someone flopped a steamer in the gene pool.