Posts Tagged ‘website monitoring’

Tweet Your Status – How to Use WebSitePulse with ifttt.com and Twitter

Thursday, June 21st, 2012

There are a lot of interesting ways in which you can use our monitoring services. Engaging in online reputation management is also one of them. A main prerequisite for establishing a good name for you and your business is being transparent. But let’s face it, eventually your website will experience downtime. It happens even to the best of sites. And more often than not it is your responsibility keep track of the performance and availability of your website, and take proper action when needed.

In the unfortunate event of your website going down, for one reason or another, it won’t take long for your visitors to find out. It is better for them to learn about it from you rather than speculate on social networks about the outage. Do you remember how Twitter used to have issues remaining online under heavy use? They came up with what became an internet meme – the fail whale. It was their own way of saying: “Yes, there is a problem and we are working on it”.

You can now do some proactive reputation management of your own, by using their platform and our monitoring services. Your visitors have twitter accounts, and when your site goes down you will get flak on Twitter. It is just something that happens with popular websites. Fear not, for there is a solution to this problem. Being upfront about a problem will save a few twitter users the time to write about it.

By using WebSitePulse monitoring with ifttt.com you can let your Twitter followers know there is a problem, and you are working on it. Even better, you can also keep them informed of the status and inform them when the issue is cleared.

How does it work?

The alerts you get in your email are easily convertible to tweets. Obviously, we don’t want to flood twitter with too much information and unnecessary updates, so information will be provided only when the site goes down and when it recovers. To do this, you need to use two “if this then that” recipes.

The first recipe will let people know that you have experienced a problem and you are doing your best to get your website up and running. Over at ifttt.com we have set a simple rule. Each time when a new email containing the text “Timeout warning for www.example.com” is received, we would tweet the following message:

Www.example.com is experiencing minor technical issues. We’re working on it! Expect the website back online any moment now.”

Letting people know there is a problem is just as important as updating them when the website has recovered. The second recipe uses the same approach as recipe number one. We use ifttt.com to monitor our email account for a recovery message containing “Recovered www.example.com”. Then we tweet out a preset message, e.g.:

“Ok, www.example.com is back online, running like a charm. Let us know if you have experienced any problems.”

Now you have an automated system to inform your followers about site issues as they happen. It is advisable to use this approach moderately and create your own ifttt.com recipes. There are many other ways in which you can use the combination of email alerts and tweets. If you have some maintenance work scheduled, you can create a custom message based on that.

Do you have any good recipes to share? Leave them in the comment section, below.

Calling All Guest Bloggers!

Monday, June 4th, 2012

Guest Blogging Oportunities

Guest bloggers and savvy tech people, come right in! We’ve been expecting you. We are thrilled to announce that we are officially accepting guest posts on blog.websitepulse.com. If you are passionate about your service, particular topic of interest, or simply want to share your experience – Drop us a line and share your idea! We are here for you and happy to publish inquisitive, well-written content.

You are not limited to written content, though a minimum amount of text would make your content more presentable and engaging to the audience. We are looking for all types of content that can fit nicely on our blog. If you have an interesting infographic, informative video, a podcast, or even good presentation, we would love to share it with our audience. All can submit their content and share experience on topics including, but not limited to:

  • Website performance monitoring – Case studies on website performance are well accepted, including those of your own site.
  • Server monitoring – A list of your favorite utilities and practices, or maybe your experience with your server software and hardware, would make an interesting read for our readers.
  • Performance monitoring tools – Share tips on how you keep your service running. Ideas about combination of different monitoring tools, or performance enhancing tactics would be the thing people want to read about.
  • Hardware and software disaster recovery – Tell is about the problems you had and how you managed to recover. Each piece of advice is valuable.
  • Tell us about your service and what makes it great.

For those of you, looking to publish good old written content, we want to point out that a topic can hardly be covered in less than 300-350 words. Meeting that minimum will make for a better guest post. Fear not, if your submission is too long. We shall split it in half and have you as a guest on the blog for a while longer.

Guest authors with ideas different from the ones listed above are welcome to write us on marketing@websitepulse.com. All queries will be answered in a timely fashion. We are always opened to suggestions and would love to publish something different on our blog.

Write for us and you will get your content published within 48 hours! All submitted articles will go through our arcane screening process, and once approved, go on our blog. Write with confidence, quality content will make its way to the blog in no time!

“So what’s in it for me?” – One might ask. We will award all approved guest posts with 3 months of unlimited WebSitePulse monitoring accounts. All you can use for up to $500 in 3 months! Authors will be allowed to leave their mark on the blog by including 2 links in the byline, accompanied by short introduction and contact details.

To be sure that your material will get published, what to avoid, and how you could enormously benefit from joining our blog, please check our Editorial Guidelines!

HTTP Archive

Friday, June 10th, 2011

I stumbled upon httparchive.org last month and I think anyone concerned with the performance of his website should take a look at it. It will give you a good idea of the current status of the web. There are some pretty interesting figures on it. The best way to describe the site is by quoting the title on their homepage “TheHTTP Archive tracks how the Web is built.” As simple as that.

The averages on that site are calculated by using raw data from all the sites listed in Alexa 500, Alexa US 500, Alexa 10,000, Fortune 500, Global 500 and Quantcast10K. To get accurate data each site is loaded 9 times. Then the data is fed and parsed to the database. What you get are some pretty interesting figures.

Httparchive.org provides intimate data for the most popular websites on the web. Not that the data is not available for anyone with the right toolset. It is just brought up pretty well. I personally enjoy the filmstrip tool, showing you how a site loads and what is visible through the different stages.

I am not too surprised to see that Steve Sounders is the person behind the website. For the few of you who haven’t heard of him, he is the guy who came up with YSlow and, yes, he works at Google.

Just to get a taste of the information on the site, take a look at the interesting stats. If you think you are using too much CSS or JS, look again. You might be surprised. The fact 56% of these sites doesn’t have cache control still keeps me awake at night.

There are usually two ways to learn good lesson:

Through your own mistakes
Through other peoples’ mistakes

Needless to say, the latter sounds better. On httparchive.org you can see what some of the top players did right, and where they went wrong. It is a great point of reference for web designers, web developers, system administrators and even business owners.

Browser emulation and a good part of the information there are sourced from webpagetest.org . You should definitely go on and check that site too. You can see how your website looks in different browsers and under different circumstances.

Custom Error Pages

Tuesday, March 22nd, 2011

As you most probably know, each year we have several seasonal report periods during which we monitor the leaders in the retailing industry to see if their online performance matches their reputation. This year is no different and last month we published the results for this Valentine’s day online retailer monitoring.

One of the interesting cases that caught our attention is the site of Victoria’s Secret. While at first glance their uptime does not strike the user with a 100% uptime percentage, the downtime recorded for their transaction happened regularly (every 2 days), always around 5 am and lasted usually for about 15 minutes. Since 5 a.m. is clearly not the busiest shopping time of the day, it was most likely a regular, scheduled site maintenance. However, this was not indicated either in their error message or elsewhere on their site. Instead, next to the picture of the stunningly beautiful Alessandra Ambrosio stood the awkward downtime excuse “We’re sorry, our site is temporarily unavailable.” .

This instance got me thinking about the importance of customizing the error pages which your customers will inevitably run into sooner or later, be it due to site maintenance or a navigation error. In the example above, if the company had simply changed the message and informed their customers that this was a planned maintenance, their uptime percentage will have reached the 100% limit.

Customized error pages help you retain your visitors and even help you attract new ones which have landed on your page by sheer force of chance and typing mistakes. Most visitors leave the site when they get to an error page, and only a handful will try a different URL. That is why the custom page should provide the clients with:
  • the correct page that they might be looking for,
  • a search engine that will help them find their required page
  • a sincere and/or fun explanation or image.

The customized error page is a great way to reassure your visitors that they have come to the right place. Furthermore, it gives your future prospects one more reason to remember your website and return to it and even recommend it later.

Aside from helping you save face, a customized error page can help you monitor your visitors behavior and see what kind of information the people are looking for on your website. All that you need to do is to set the error page to submit a broken link to the webmaster. In this way you will be able to fix and upgrade your website accordingly and in a timely manner. Another plus side is that custom 404 pages help the search engines consider these pages not as error pages when they are set to return a 200 OK response in the header. As a result they get indexed and appear in the SERPs. Keep in mind that this is not a very good practice as the 404 status should be indicated in the header in such cases.

Below you can see 15 original and fun examples of custom error pages. If you would like to see even more, we recommend clicking here and here.

 

clomid, synthroid, zithromax, accutane, celebrex

“We Don’t Need To Monitor Our Sites”

Friday, February 4th, 2011

“We don’t need external service to monitor our sites. We have people on staff to take care of this.”

Many people think like this. Many people, who make important decisions in your company, might think like this. They are both right and wrong. They are right about 99% of the time and we are wrong about 1% of the time. Then again, that 1% percent seems to matter to business owners, as we have come to understand.

Recently, a company hosting many online services, experienced massive downtime. It turned out that when 99% of your business is online, 1% of downtime is a lot more that it looked. Centralization and decentralization of hosting is probably a topic for a whole different post, but for the means of our argument – keeping all the eggs in one bag proved extremely harmful.

Just before Christmas, all sites went down for about 6 hours – 6 good business hours, we might add. There were immediate consequences and there still are collateral consequences to this. Six hours of downtime in a single month means ~99.2% uptime. This is bad. No hosting provider will advertise this on his homepage. The initial damage consisted of loosing business as well as keeping employees unoccupied for the better part of the day. A lot of crucial administrative tasks failed at that point too.

Everything went crashing down in a matter of hours, leaving more than one business vulnerable. When company owners have multiple businesses to look after and they all fail simultaneously, they don’t experience 6 hours of downtime, but 6 hours of downtime multiplied by the number of businesses they have.

The cause of all this was a failed backup device, which should have kicked in, but it never did. The problem could have been easily prevented if performance issues were early detected. With no proactive alerts, the only way one could have seen the problem coming is if he spent all day checking how sites load. It sounds pretty much like what our tools do and they don’t require work related benefits and a parking space :) .