Popular Posts

Showing posts with label mobile web performance. Show all posts
Showing posts with label mobile web performance. Show all posts

Friday, June 22, 2012

10 Tips to Improve User Experience of your site

Hi. My name is Ben, and I plan to visit your website a lot! I’m a casual user that likes to browse the Internet, and like everyone else I know, I hate to wait. Although your website is really cool, and I love your products and services, the Internet is full of interesting places and I’m easily distracted. Oh, and did I mention that I love using my Android smartphone and iPad to play, connect, shop, bank and book travel when I’m not at work? All I want for the holidays is a speedy web and mobile site.
Here are top 10 wishes of a user for you and your site in 2012:
  1. Please test your code/site on IE and not just Firefox before you launch it. I am one of the 50% that will continue using IE, even after they start auto-upgrades!
  2. Understand the difference between browser execution and network/back-end performance. Most pages have both and you need to know which is which to optimize the page/site. One way is to monitor using a real browser.
  3. Understand how your page renders. Focus on reducing upfront (pre-render) delay. It’s the one me and your other users feel the most!
  4. Please make sure your third party tags (analytics and others) are below your visual content. (Did I mention rendering delays and blocks are aggravating?)
  5. Please combine your external JS and CSS files. I’ve been saying this for years, but very few sites seem to follow this recommendation. Do it, and I’ll see a major improvement in the speed of your site.
  6. Understand the quality your Content Delivery Network is providing. Every website is unique, and not all CDN providers are created equal.
  7. Don’t worry so much about overall page size but instead focus on individual file/resource sizes. Keep them under 100K and you will limit the impact of slower connections. (Did I mention I love my smartphone?)
  8. Don’t just push your desktop website to mobile. You will fail.
  9. Test your mobile web site… please!
  10. Read Keynote’s Page Construction Guidelines. They’re chocked full of goodies to help you optimize the performance your Web pages and keep visitors like me happily clicking through them, instead of away to your competitor’s site.
What’s on your wish list for better web and mobile performance in 2012? Let us know in comments!


Relate Articles:

Wednesday, February 8, 2012

The Elephant In The Cloud: Performance

For all of its tremendous potential, there’s one thing that will make or break the SaaS model both for vendors and users: Web Performance. No longer is technology contained within the walls of the enterprise, running on its own proven network, controlled closely by its own IT department. Now, the nerve center of the enterprise, the productivity of workers, the integrity of information assets is controlled by an outside entity, flows through the various pipes from a remote data center over the Internet into the enterprise’s network and ultimately, into a browser. And that presents challenges both for performance and user experience.


The problem with the browser being the front-end for SaaS applications is that users have very clear expectations of a browser experience, based on their use of the Web. Users go to a site and expect it to load fast — in two seconds or less. They don’t like to wait, and won’t. Google says that for every additional 500ms of delay, the site loses 20 percent of its traffic. With fast broadband and wireless connections everywhere, users expect blazing speed when they fire up their browser.


Read More http://keynote.com/benchmark/SaaS/article_industry_focus_cloudy_applications.shtml

Tuesday, January 24, 2012

Mobile Web: Load Testing and Ongoing Performance Monitoring


Many retailers are making efforts to enable genuine mobile commerce, as opposed to trying to drive traffic from mobile to other channels to complete the transaction. And many are bringing their mobile development efforts in-house, after testing the waters with a third-party solution. Both of these scenarios involve significant risk, making it all the more imperative to perform robust load testing and ongoing performance monitoring.

The big challenge that mobile sites face that’s different than the desktop Web — in addition to the inherent slowness of over-the-air (OTA) signals — is the plethora of devices, operating systems, and carriers. A mobilesite or app has to be vetted in all the major configurations that ultimately control what is displayed in the user’s hands.

Any outage or excessive slowness during peak holiday periods can inflict serious pain on a retailer’s bottom line, whether the retailer is big or small, online-only or hybrid. The only way to make sure a website can handle an extraordinary rush of traffic is to thoroughly test it well in advance and every time changes are made. The most solid test regimens subject a site to traffic that’s multiples of the highest demand projected by the sales and marketing department.

Read More

Thursday, December 29, 2011

Performance Testing for Retail


In the broadest sense, testing falls into two categories: ongoing evaluation and tweaking to optimize daily performance, and peak load testing to determine overall site capacity and potential breakpoints.
In either case, the only way to quantify user experience is to measure what users are actually experiencing. Unless you’re the local bike shop serving only your immediate area, the testing needs to be done across a wide geography and multiple backbones. And it needs to use an actual Web browser, and go through the same type of page view sequences and transactions as a typical user would. There’s simply no other way to get a true perspective on what users are really experiencing.

GETTING A PERSPECTIVE ON EVERYDAY PERFORMANCE
Ongoing performance testing, done on a routine basis or following upgrades, patches, or redesigns, can be as simple or complex as the site itself. Assuming the back of the house is in order — that servers are performing up to speed and all of the infrastructure is optimized — the focus of the testing is on the front end. Individual pages are tested and analyzed, and those performing below par are deconstructed to identify the structural problems or elements that are causing the slowdowns.

A single element could be dragging down the page load, or it could be less-than-ideal placement of JavaScript on the page. The point is that testing and identifying the problem pages or transactions is only half the problem. The other half is being able to pinpoint the causes and correct them. A robust performance evaluation regimen accomplishes this.

RETAILERS SHOPPING FOR STRATEGIES
A few retailers are feeling upbeat about the coming holiday season. Best Buy is planning to do more holiday hiring than last year, partly because of strengthening demand for flat-screen TVs, smartphones, and netbook computers, and partly because of market share they captured following last year’s demise of Circuit City. Target plans to have 26 new stores open in time for the holidays, including five “Super Target” stores with full grocery departments; this, and more aggressive pricing, are moving Target closer to a head-to-head brawl with Wal-Mart.

Most retailers, however, are simply looking for ways to maximize their share of holiday revenue. Deep and earlier discounting is expected to be widespread. And in a throwback to an earlier era, and at least partly in response to a growing paucity of consumer credit, the layaway plan is making a comeback. K-Mart and its parent company, Sears, are both offering not only in-store layaway plans, but also online versions as well. Consumers can reserve their merchandise and make payments online, and when they are paid in full, pick up their merchandise in the store. Whatever it takes, even down to giving away free gift cards, retailers are doing to get consumers to buy, either in the store or online.

Source: http://keynote.com/benchmark/online_retail/christmas_article.shtml

Monday, November 7, 2011

Enhance Web Performance with Best practices: Methodology & Modeling

To really understand how your website performance will hold up—or not—under holiday stress, and to understand what the experience will be like for users, use an arrival rate methodology and factor in behavior models for the many, many types of users and tasks your site will serve.
Behavior modeling results in numerous permutations (often thousands) combining these variables:
  • Familiarity:  experienced users vs. newcomers
  • Connection speed:  super-fast FIOS vs. super-slow mobile device, and everything in between
  • Latency tolerance:  patience of users with slow site response
  • Interaction speed:  complexity of the page to navigate, and attention level of the user
  • Tenacity:  willingness of users to stick with a task through completion

Test in the real world—all of it.
To know how your site will perform for users dispersed across the country or the world, load testing must be done over the Internet, from the same geographic locations as your users, not from behind the firewall.  There’s simply no way to simulate the vagaries of Internet backbones, third-party content feeds, CDN performance, and signal transmission through the critical last mile—unless you are at the end of that mile, with a browser.

With testing agents dispersed where your users are, you get an accurate picture of variations in performance, and overcome the danger of looking at averages.  An average page-load time of three or four seconds may seem OK, but that kind of average could mean your page is loading in one second for someone in New York, but taking six or more seconds for someone in Chicago.  And that is not likely to be acceptable.  The solution is to test from multiple, geographically dispersed locations, look at the data, and address any local or regional bottlenecks.

The holiday shopping season is the culmination of many hard hours of work for the IT/Web department.  And no matter how well things are planned, no matter how rigorously everything is tested, there’s always the chance that the unexpected will happen and something will go wrong.  So it makes good sense to have technical personnel on hand and on call during all the critical shopping periods to handle any emergencies, and to have extra computing capacity standing by just in case it’s needed.

Read More at http://keynote.com/benchmark/new_media/article_streaming_for_primetime.shtml

Tuesday, October 25, 2011

A need for speed on mobile websites


While the majority of smartphone users want to shop with their phones, only a small minority of retailers offer either mobile apps or websites. One study puts the number of mobile-friendly retailers (app or site) at 32 percent; another counts less than 5 percent of retailers with a mobile-specific site.

Retailers need to catch up in a hurry. The smartphone tipping point was officially reached in spring of this year, according to Nielsen, with 55 percent of new cell phone purchases now being smartphones. Smartphone users express a strong preference to use their phones to shop, but a majority of them find the mobile shopping experience unsatisfactory — 54 percent say mobile apps and sites are “ineffective and difficult to use.”

A Harris Interactive study found that, of adults who conducted a mobile transaction in the past year, 4 out of 5 experienced a problem. And yet 85 percent of the same survey group expects the mobile experience to be equal to or better than using a computer.

It doesn’t have to be such an unsatisfying experience for users. It’s not rocket science to create a mobile site that loads with acceptable speed and delivers the features consumers want. What it requires is a change in mindset from desktop Web thinking to mobile Web thinking. Techniques that make for a rich, and yet still high-performing, experience on the desktop can render the mobile experience painfully slow or even unusable.

The good news is that on the mobile Web, user expectations of content are likely more modest. They are typically more focused on a task — finding an address, getting a price, seeing a product, buying a single item — rather than the more leisurely browsing or immersive experience they might be looking for on a desktop or laptop. So from the start, mobile content can be pared down without compromising likely use cases, so you can already be ahead of the game simply by selectively choosing content for mobile.


Monday, October 10, 2011

Retail and an Intro to Mobile Strategy


Mobile Performance management starts with how the pages are built, which often presents a dilemma for retailers. With more and more products approaching commodity status and available at multiple online outlets, site experience becomes a key differentiator.  Retailers want to create a rich experience for visitors with interactivity, dramatic product presentation, perhaps Flash, personalization or other features to set themselves off from the competition.  But a heavy load of features and functionality can drag site performance down, often because of third-party content, and, instead of making visitors sticky, can drive them to leaner, faster competitive sites.

The successful retailers this year will have built mobile into their strategy right from the start—not just as an afterthought to the “main” site, but side-by-side with it.  Shoppers carrying smart phones are using them to check prices, locate products, find deals, look at reviews and, more and more, to make purchases. 

Many retailers were surprised at the amount of mobile traffic they got during the 2009 holiday season.  And there will be millions more smart phones in the hands of shoppers this year.

With regards to mobile website availability, the inherent slowness of cellular networks and devices, mobile sites need to be even leaner and meaner than wired Web sites.  It takes some hard decision-making and analysis of what is essential for users when they are browsing on the go and what it takes to satisfy them, including their need for speed.  Search results can be confined to return four or five results, for example, instead of the 40 or 50 that might be delivered on the wired Web.  And perhaps tracking pixels are needed only on the landing page and cart page, instead of every page on the site.