Performance and Uptime of URL Shorteners
INTRODUCTION
WatchMouse monitored the availability (uptime) and performance (page load speed) of the most popular URL Shorteners from February 24 through March 28, 2011.REPORT_INTRO_MORE
A blog article including observations, analyses and performance statistics of the most popular URL Shorteners that were monitored by WatchMouse can be viewed at: WatchMouse Blog
PR_REPORT_AVAILABILITY
| # |
REPORT_WEBSITE |
REPORT_UPTIME |
REPORT_DOWNTIME |
| 1 |
BudURL |
100.00 |
0 minutes |
| 1 |
fb.me |
100.00 |
0 minutes |
| 1 |
goo.gl |
100.00 |
0 minutes |
| 4 |
amzn.to |
99.99 |
4 minutes |
| 4 |
binged.it (bitly.Pro) |
99.99 |
4 minutes |
| 4 |
bit.ly |
99.99 |
4 minutes |
| 4 |
is.gd |
99.99 |
4 minutes |
| 4 |
lnkd.in |
99.99 |
4 minutes |
| 4 |
ow.ly |
99.99 |
4 minutes |
| 10 |
j.mp |
99.98 |
9 minutes |
| 11 |
mcaf.ee |
99.97 |
13 minutes |
| 11 |
lnk.ms |
99.97 |
13 minutes |
| 11 |
youtu.be |
99.97 |
13 minutes |
| 14 |
y.ahoo.it |
99.95 |
22 minutes |
| 15 |
wp.me |
99.94 |
27 minutes |
| 16 |
fwd4.me |
99.93 |
31 minutes |
| 17 |
tinyurl.com |
99.90 |
45 minutes |
| 18 |
tcrn.ch (bitly.Pro) |
99.88 |
54 minutes |
| 19 |
su.pr |
99.76 |
1 hour, 47 minutes |
| 20 |
t.co |
99.71 |
2 hours, 9 minutes |
| 21 |
snurl.com |
98.11 |
14 hours, 4 minutes |
| 22 |
digg.com |
37.71 |
19 days, 7 hours, 26 minutes |
| 23 |
to. |
0.00 |
31 days, 0 hours, 0 minutes |
| 23 |
tr.im |
0.00 |
31 days, 0 hours, 0 minutes |
| 23 |
twurl.cc |
0.00 |
31 days, 0 hours, 0 minutes |
NOTE: The Twitter URL shortener t.co is blocked from China, which caused some downtime as measured from our monitoring stations (two consecutive errors from two different locations in China is regarded as downtime). If the errors from the China locations are excluded the uptime for t.co is 100%.
The performance (page load speed) was measured for the most popular URL Shorteners and the results are displayed in the graphs below.
Note that the chart on the left is without the resolve time (time to lookup the IP address for the specific host name), and the second chart includes the resolve time. As you can see the resolve time can be a very significant part of the total loading time, which is mostly caused by the use of uncommon TLDs like ".gd". Altough not an issue for most users, as these popular URL shorteners are often cached by the ISP, this is an issue for people that are connected to the internet through for example a company network with a private DNS.
PR_REPORT_SPI_INTRO
METHODOLOGY
WatchMouse monitored the availability (uptime) and performance (page load speed) of the most popular URL Shorteners from February 24 through March 28, 2011.
Availability
METHODOLOGY_TXT
PERFORMANCE
METHODOLOGY_PERFORMANCE
- Resolve time: LEGENDA_RESOLVETIME
- Connect time: LEGENDA_CONNECTTIME
- Processing time: LEGENDA_PROCESSINGTIME
- Download time: LEGENDA_DOWNLOADTIME
- Total time: LEGENDA_TOTALTIME
Site Performance Index
SPI_DEFINITION
RESEARCH_COVERS BudURL, fb.me, goo.gl, amzn.to, binged.it (bitly.Pro), bit.ly, is.gd, lnkd.in, ow.ly, j.mp, mcaf.ee, lnk.ms, youtu.be, y.ahoo.it, wp.me, fwd4.me, tinyurl.com, tcrn.ch (bitly.Pro), su.pr, t.co, snurl.com, digg.com, to., tr.im, twurl.cc.
PR_LEARN_MORE www.watchmouse.com
