Posts Tagged ‘website performance’

2010 Holiday Retail Performance and Uptime Report

Tuesday, November 23rd, 2010
With the holidays rapidly approaching, retailers are anxiously trying to think up of new ways to get the people to open up their wallets. And this situation is not surprising – the success of the entire year will be determined to a large extent on profits generated in the next two months. Although shoppers still remain a bit reluctant to loosen the stings of their wallets, market analysts and retailers alike are much more optimistic about the results than they were last year.

A recent report by Jefferey Grau, one of eMarketer‘s leading analysts, predicts a 14.3% rise in online sales over the same period last year. This growth is expected to boost season sales to $38.5 billion, up from $33.7 billion last year. Grau predicts that “This holiday season consumers will open their wallets more than they have the past two years, even though they will remain extremely price-focused. Online consumers have become savvy at finding coupons, comparing prices, locating cheaper product alternatives, and exchanging shopping tactics and information about bargains with peers through social media.”  The key to the hearts of the customers will be held by the retailers that manage to offer rich product information, easy return policies and friendly customer service representatives.

Here, at WebSitePulse, we are curious to find out how the online retailers will handle the holiday pressure and the high loads of traffic. That is why between November 22, 2010 and January 5, 2011 we will be monitoring ten of the most popular online shopping destinations for the 2010 Holiday Season. The detailed results will be available here and, if you are feeling lucky, you can venture a guess as to who will end up on the top of the uptime table this year.

May the holiday race begin!

Android Server Monitoring App

Friday, November 19th, 2010

In order to meet the demand for mobile monitoring solutions we are proud to present our Android Server Monitoring App! We believe this mobile application will significantly increase the overall value of our services and will fill the existing gap for such a tool on the Android front. With our app you will always have control on the performance of your website and/or server. You can enjoy all the features from our mobile website, but  in an interactive and more user friendly way.

Android applications are becoming more and more popular, partially because of the fact ~57% of them are free and mostly because a lot of people love Google products. By introducing our mobile server monitoring application we are now able to provide you with an easy way to keep track of your sites everywhere you go. Instant, on-demand uptime monitoring now fits in your pocket. The app is able to update the information on a preset interval and give you notifications for important events. As always, we are opened to any suggestions for additional features. Your feedback is valuable to us so if you experience any  difficulties or have idea for another Andoid application let us know.

To start using our app you just need to download it by reading the barcode with your mobile phone or other Android based device. You need to be an exiting user, or you have to create an account with WebSitePulse, because the application requires you to login to monitor your projects. API keys are provided to all of our users.

Choosing a Good Password

Thursday, November 11th, 2010

Often the only protection we have online are our passwords. Since passwords are used everywhere – from online banking to common blogs – they are an integral part from of our online presence. Private information is successfully becoming the most valuable resources to come by, so a lot of people are getting more and more paranoid about their privacy.

Each individual spending at least a couple of hours a week online has at least a handful of passwords to remember. It is, however, surprising how most people are still quite negligent when it comes to creating a good password. You will be surprised how people fall for cliches. Well, after all, this is what makes a cliche what it is – a lot of people backing it up.

The first mistake many people do when they choose a password is to think of something common or personal, something a lot of people are familiar with, and could easily guess. The second big mistake is using this easily attainable password on every single profile that they have.

The truth is that passwords are not that hard to break,  at leasts common passwords, that is. A simple word or a combination of words from the English language are probably the easiest ones to break by using common sense or a relevantly simple dictionary attack . With computers becoming faster and more powerful at an exponential rate, brute force attack is becoming accessible to more people. The latter is nothing you should worry about when trying to come up with a password for your wi-fi router though.

We performed a test with a simple 8-character letters-only password on a wi-fi router. It took 26 days before someone broke it, and began using our Internet connection for free. However, the trouble one can get into is far more serious than simply slower connection. People can do a lot of illegal things through your IP address and leave you to take the blame.

Adding a simple numerical character or a symbol make the password several times harder to break. Here you can find some great tips on how to choose a strong password. Also be sure to check this list of common passwords so you know what to steer away from.

If you run a website or a blog and want to take your site’s security one step further, consider remote monitoring on top of a good password. Our website monitoring service can even alert you if your your site is not performing properly while you are away.

So, tell us – what is the worst password you ever seen?

2010 Hurricane Season Web Performance and Uptime Report Results

Monday, November 1st, 2010

Three months ago we launched our traditional Hurricane Season Web Performance Report. During this time we continuously monitored five of the key websites which provide real-time forecasts, details, emergency information and donation opportunities when disaster strikes.

Now it is time to officially announce its end and summarize the results. Here’s what happened this year:

  • The 100% uptime mark was hit only by one of the websites.
  • High loading times plagued two of the monitored sites.
  • No severe downtimes were detected and the result is a visible improvement in the average uptime of all sites – 99.944% (compared to last year’s 99.760%)
  • The fastest average loading time sets the bar very high for the others – a stunning 0.389 seconds.

If you are curious to find out which are the sites that we monitored and what their results are, you can find the complete data here. Go ahead, see if your predictions will match the results!

Site Speed – It Matters!

Tuesday, October 12th, 2010

We are all obsessed with speed. Just today the elevator in my building got me thinking how often we get nervous with the slightest changes in our every day routines.

It usually takes the elevator around 12-15 seconds to get me up to the 4th floor. All of a sudden, the elevator door began malfunctioning, and as a result it now takes me 15 seconds to get to the 4th floor, and another 5 for the door to open. After a couple of days I began to think that the stairs are not such a bad option. Now, imagine that this is your website. People are used to getting the information they need when they need it. When your site gets slower and it takes 10-20 second for a page to load, people tend to get nervous and find an alternative route to get what they want.

Access time is probably one of the most important factors for a site. You might have great content and services, but if you are not able to present it in a timely fashion, you are just throwing your hard work away. There are various ways and good practices to make your site run faster. A good starting point would be to go through these Usability Guidelines. These guidelines are particularly useful if you like to give your audience better experience while on your site. It is also quite important for search engines. Since April 2010 Google officially considers speed a major factor, and it was about time. People should have the content they want, when they want it.

Google keeps track of your site’s performance, and tries to give you a rough idea on your site’s speed. It gets updated every 2 weeks or so. You can check the speed at which your site delivers content as often as every 5 minutes with our website monitoring service. If you still haven’t tried it, we are curious to know what you think about our free trial.

Quick Tips on Website Maintenance

Friday, October 8th, 2010

When are you performing your next website maintenance? It is night time, yes? Well, let us give you a few pointers on how to do it more smoothly.

Any intentional website downtime requires that you consider 4 main parties – your partners, your current and prospective users, and the search engines. Luckily, the tips below cater to all three.

Scheduled website maintenance

This one is really a no-brainer, however you will be surprised how many small and mid-sized businesses overlook this. People relying on your service need to be well aware that at some point in time they won’t be able to access your site. You can schedule your maintenance and warn them with a short message on your site, or by sending them a newsletter. I personally advise you do both. Don’t forget, we are talking about your most trusted audience here. You are doing this for the people most passionate about your product or service.

Check your server logs before you start

The best time to perform any changes that may result in considerable website downtime is the time of day when you get the least traffic. This helps in two ways. First -  you affect as little people as possible. Second – any unforeseen problems and extended downtime can be resolved before “working hours”, when you are most likely to lose business. Information of your website’s utilization are quite handy in this case. All the information you need is there. Unfortunately, performing website maintenance in the least busy period of time most likely means you won’t be getting a lot of sleep that night. Then again, it all depends on your audience. The greatest advantage of performing any major changes, in that manner, is that it is less likely for you to lose on your first time visitors. Like they say – “You only get one chance to make a first impression”.

Use 503 HTTP status code

This is not only very good for search engines, but it is in general a good practice to follow. 503 is your website’s way to tell a search engine “Hey, I’m a bit busy at the moment, please come back in an hour.”. This makes all the difference to search engines. You are not giving back a 404 error code, but a tidy little page, saying you are out for a while, but you will be back soon. Actually, what the engine reads is the response header. There you can specify the exact amount of time for which your service will be unavailable. The search engine bot will come to your site, receive the 503 status, and will quietly come back in a few hours to get the job done.

Since blogs are as popular as ever, many people requiring only a small site often go for a blog. Usually that blog is WordPress. There is this great plug-in you can use to give 503 status to search engines, when you are about to tinker with your site. It is called Maintenance Mode. It is probably one of the most useful WordPress tools I ever came by.

If you have any tips of your own, or would like to share a story, feel free to leave a comment.

Facebook Down

Friday, September 24th, 2010
Facebook was down – this is the news making the headlines today. Quite unexpectedly for both the Facebook team and the millions of users, the social networking giant went down yesterday from 2.30 p.m. EST and recovered around 6 p.m.  resulting, in their own words,  in “the worst outage we’ve had over four years”.  The failure was also immediately detected and confirmed by all of the locations in our monitoring network.

The reason for the outage was a series of problems involving an automated system designed to verify configuration values in the cache and replace invalid values with updated values from the persistent store. An error sent system into a feedback loop that only cutting traffic to a database cluster and rebooting the site could solve.

The social network has apologized for the downtime and is reportedly working to prevent future problems in the area. However, with a user-base of over 500 million, this outage is bound to have its repercussions. As InformationWeek notes: “As a comparison, a service disruption last year at another major Internet property, Google, resulted in a 5% drop in Internet traffic.”

But there is also a bright side to this unfortunate event. As today’s best tweet says: “Facebook is down. Worker productivity rises. U.S. climbs out of recession”. Or another one: “Facebook is down. Expect a huge spike in births in nine months.”

clomid, synthroid, zithromax, accutane, celebrex

The Anatomy of Response Time

Friday, September 3rd, 2010

 

There are many different components by which you can measure the performance of your websiteuptime, availability, speed, ease of use, etc. One of these components, which is by far the third most important after only availability and uptime, is the response time. In essence, response time is the total amount of time needed to download all the components of the page that the user is visiting.

While measuring the response time is not so difficult, reading into it and finding the exact cause of the slowdown is not that easy a task. So, to be able to precisely pinpoint why your site is loading slowеr than you’d expect, first you need to know the components of the response time.

On the whole, response time comprises four parts: DNS lookup time, Connection time, Redirect time, First byte and Last byte.

The DNS Lookup time is the time that is needed to resolve the website’s hostname to a certain IP address. Usually, if the DNS lookup time is high, it means that you might have a problem with your DNS servers. Keep in mind that most providers cache the DNS record for a specific time indicated at the so called “DNS zone” file, so when monitoring your site, the DNS lookup time affects the response time only once in case of multiple references pointing to the same domain name.

The second part – the Connection time – shows how long it takes to establish a connection to your server. This measurement can help you monitor your network latency. It is also a good indicator for routing or network issues.

Redirect time is the time it takes to follow any HTTP redirects in the server’s response. It also comprises the time for any DNS lookups or connection times that might occur during this process.

The First byte shows how long it takes from the moment the connection was created until the first byte is about to be transferred. The time to perform any negotiations with the server and the time needed for the server to calculate the result are also included. The First Byte time is measured in seconds, and, when too high, may indicate a problem with the server load.

The time necessary to download the final server response is called Last byte. Generally, you can use this value as a good bandwidth indicator – if it is too high you may want to decrease the page size or upgrade your bandwidth in order to increase the download speed from your site or server.

So, now that you know how to read the response time, why don’t you test the response time of your site here?

5 Easy Ways to Improve the Performance of Your Site

Thursday, July 22nd, 2010

In this blog we’ve already discussed the importance of response time. And I hardly need to tell you that when a website loads slowly… um, well, you’d rather take your business, reservation, purchase or pleasure somewhere else. So, now that you have your website up and running, you definitely don’t want it to be an underachiever and drive those potential clients away simply because it fails to load properly. So here are 5 simple ways to improve the performance of your site without too much effort.

 

1. Minimize the HTTP Requests

Why is it important? The answer:  the greater part (and I mean like 80%) of the response time is spent downloading the front-end components of the page – images, scripts, CSS and so on. Therefore, fewer components to download mean fewer HTTP requests and this, on the other hand, means faster response time of your page.
How to do this? Use combined files, CSS sprites and Image Maps. You may find them a little challenging in the beginning, but if you really want your site to perform well, this is the first starting point.

 

2. Compress to Impress

Why is it important? To put it simply, compression helps decrease the response time of a site by reducing the size of the HTTP response.
How to do this? The most popular method is Gzip. It helps you reduce the response size by almost 70%. Generally, servers choose what file types to Gzip. And while most sites Gzip their HTML content, you can take it one step further and compress even your scripts and stylesheets. This will reduce the weight of your site and significantly improve user experience.

 

3. Minify the JavaScript and CSS Documents

Why is it important? To minify means to remove all the unnecessary characters from the source code without losing any of its functionality. This method works especially well for JavaScript documents as it reduces the size of the downloaded file and this, in turn, has a direct effect on your website’s response time.
How to do this? Well, you can always do it manually… But why bother, when now you have such good tools like JSMin, Packer and YUICompressor, which can even compress your CSS files.

 

4. Stay Away from Redirects

Why is it important? Unless absolutely necessary, avoid redirects as they notably slow the response time. This happens because during the redirection nothing in the page can be loaded until the HTML from the new location arrives.
How to do this? Very simple – just don’t insert any redirects unless you have to.

 

5. Monitor Your Server Performance

Why is it important? Even if you have the best performing and most beautifully and efficiently designed site ever, if your server is not working… well, you can do the math.
How to do this? The answer: here.

 

 

To read more useful tips on site optimization visit the Yahoo!Developer Network and Six Revisions sites.
You can also share also your own tips in the comments below.

 

Real-life Ping

Wednesday, July 14th, 2010

Here is something funny a friend of mine passed on to me a few days ago. Enjoy these common everyday situations described with just as common to network administration terms.

DHCP

You wake up after wild drinking. Your first words are “Who am I?”, “Where am I?”. Your neighbour, who did not mix vodka with beer, tells you all your data, who you are and where you are. This neighbour behaves like DHCP-server. Note that in the Network there may be so-called “fake DHCP-servers”, e.g. your wife, to the question, “Who am I?”, may give you false information, “You are an alcoholic”. So, obtaining dynamic registration is vulnerable, therefore it’s recommended that you write your data (name, address) on a piece of paper.

Default routing

Go to a pedestrian and ask him/her “could you tell me how to find the George W. Bush cemetery?” Most probably you will be sent to a place, which contains four letters. That’s the so called “default routing”, or in other words, if you don’t know your destination address, the packets are being sent there (same like default gateway, or gateway by understanding)

TTL

Imagine you are 5 years old, and want to eat. You go to your Father and say “Dad, I want to eat”. He is watching TV, and following the routing table, sends you to your Mom. You go to her, and ask, “Mom, I want to eat”. Your Mom talks on the phone with a friend, and following her routing table, sends you back to Daddy. So, you walk from your Father to your Mother, just because the not so skilled administrators (Mom and Dad), have built improper routing table. To prevent such cases, the TTL (Time To Live) was created, which in this case means the patience in the kid, until he falls into the legs of Mom or Dad, totally tired. The latter is due to send a note to the person who has sent the kid to eat; that’s the so called ICMP packet.

Ping

You’ve surely have been in situation “you’re the fool”. You yell “John, you’re a fool”, and in return you hear, “George, you are the fool”. That’s a simple ping. You have just pinged John. Not everyone responds to pings, especially if they are well educated, e.g. Microsoft.com does not react to your pings. It’s useless to swear them, as we know they can hear us, but there’s no reaction. In any case, ping is good to see if the host is alive.

Traceroute

Imagine you live on the 9th floor and you want to find out who lives between you and Julia, who lives on the 3rd floor. You take a little bomb, and by the formula for free fall, you calucalate the explosion to happen on the 8th floor, that’s TTL=1000 ms. After the bomb explodes, you will see the angry face of the neighbour from the 8th floor. Time of reaction depends on server average load – is the neighbour busy. If there’s no answer at all, then your neighbour has icmp reponses forbidden. Then you put TTL=2000, etc. However, don’t forget, that if Julia lives on the 10th floor, that will be “no route to host”.

Now, if you excuse me, I’m going out to Traceroute my Ping until I TTL.