Uiuc.edu

 
Ads by Google

Latency Testing Disabled.

SiteSpeedLab can't measure the latency of the uiuc.edu. While performing tests we do not get responses from the remote server 128.174.4.87.
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester
Learn more at DNS Testing Profile
Separate test for different locations, time frames
Learn more at PageSpeed Testing Profile

WebSite Speed Profile

Site Speed Success Formula = good website latency + fast DNS lookup + high page load speed.
Site Speed Laboratory offers analysis of DNS Lookup speed & latency tests (ping) & Page Load speed for every website. Our analysis is based on data for May 25 2011. Since the first of July 2010 we carried out 23 tests from locations
for the main page of this website, the last of which were made about 3596 hours ago

Tests Summary

DNS Summary

Page Speed Summary

Site Speed Laboratory Summary for this website

Location Ping Ping,
change
DNS Lookup DNS Resolve,
change
Page Speed Page Speed,
change
 Usa
50.70% of traffic
NY, New York 47 ms 28 % 405.37 Kb/s 4%
Florida, Tampa 132 ms 110 %
 Germany
3.00% of traffic
Frankfurt 126 ms 4 %
 Canada
2.20% of traffic
Montreal 26 ms
 United Kingdom
2.90% of traffic
Gloucester 151 ms

Summary Widget

SiteSpeedLab Overall Website Rating for this website
Based on our speed test results table and considering features of the current webserver location (United states, Urbana), we concluded
overall This website speed rank is 80. That means 80% of the sites from the Urbana are slower for visitors than this website.

It is important to understand that you can't evaluate website speed without considering website audience location. You should evaluate the speed of the site considering location of your primary audience (visitors), and not just from abstract tests from various points of the planet. There is a chance that your website is quite slow for visitors from German but pretty quick for Australian users at the same time. Based on a primary audience location data Site Speed Laboratory maintains objective rating. Test servers located in the Usa and Germany are more useful and important to Uiuc.edu because the shares of each country are 50.70 and 3.00 percent respectively.

You should not overestimate the importance of the website speed factor. Google has more than 200 ranking factors and website speed is just one of them.

DNS Lookup Speed

Browser should lookup domain name and get IP address of the server (128.174.4.87) before downloading the page. We test DNS resolve for this domain from 5 locations. That's how we've got the average time of receiving IP: 0.1s (which is better than 60% of all sites). For more detailed stats look at DNS tests graph and DNS resolve page for United states, Urbana location (Average value on the widget is an average DNS resolve time for websites hosted at the same location).

DNS History Graph

Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss

Compare DNS Speed

Compare DNS Lookup


vs

Our Servers
Usa
NY, New York
Florida, Tampa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester

The table below shows the dynamic of the DNS Lookup speed changes for the website from various locations.

Location Last check 7 day change 1 month change 3 month change 6 month change
 Usa
50.70% of traffic
NY, New York 47 ms 15%
46/40 ms
Florida, Tampa 132 ms 1%
92/93 ms
 Germany
3.00% of traffic
Frankfurt 126 ms
 Canada
2.20% of traffic
Montreal 26 ms 8%
36/39 ms
 United Kingdom
2.90% of traffic
Gloucester 151 ms 12%
138/123 ms

Fragment of Urbana DNS Speed rating table for this website

The table is constructed according to the data from the US datacenters

# Domain Compare DNS Resolve Speed Provider
1. Otm.illinois.edu 75 ms University Of Illinois
2. Fass.org 82 ms Champaign Telephone Company
3. Llvm.org 83 ms University Of Illinois, Ccso
4. Hillside.net 90 ms Paetec Communications
5. Dominopower.com 95 ms Prominic.net
6. Uiuc.edu 96 ms University Of Illinois, Ccso
7. Outlookpower.com 103 ms Prominic.net
8. Cazoodle.com 126 ms University Of Illinois
... ... ... ... ...
15. Cuwin.net 475 ms Comcast Business Communications

Page Speed Test

Content-Type's Weights
 
 
Content-Type's Weights by Hosts
 
 
Downloading page itself is the final stage of the testing. Actually, this is the last stage, after which page is displayed completely for user. The download speed depends on many factors. Main factors are the following: the width of the bandwidth up to the domain, the number of simultaneous download threads, speed of the server, a distance between user and domain web server. Recent measurements have shown the speed of page download for this domain is 405.367Kb/s (which is better than 80% of all sites in this region). For more detailed stats check out report for Urbana hosted websites.

 
 
 

Page Speed

Page Speed is a key factor in the website speed estimations (along with DNS lookup speed and website latency). Speed of the page loading, sophisticated subdomains usage for static content (images, css), optimized code (html, js), hosting on fast servers with good latency to its audience leads to good results and, ultimately, to a good website profitability.

While conducting tests we emulate a visit your website using the browser Firefox 3.5.6. Test results of the page loading listed in this table:

Pagespeed Flash Table

Ways to improve website performance

Once the document (website's main page) has been downloaded, we analyze it. It allows us to give webmasters some recommendations on how to optimize page load speed. We analyze the internal and external factors.

Reduse DNS Resolve

Browsers must resolve site's hosts to display all of the elements of the Uiuc.edu's page. Every domain name resolve requires a time, which precedes the load from a specific domain. You can speed up page loading by reducing the number of hosts, from which elements of the page are loaded.
 Host illinois.edu (69 files)
 Host emergency.webservices.illinois.edu (1 file)
 Host ocsp.thawte.com (1 file)
 Host www.google-analytics.com (1 file)

Enable GZIP Compression

This is a good practice to give the user content in compressed form. We've detected 229.02 Kb of content that could be compressed. By compressing content you can achieve the size of ~ 57.26 Kb (saving 171.77 Kb). This would accelerate the page loading speed and would positively impact the bandwidth savings in University Of Illinois, Ccso.
http://illinois.edu/. File size 19.47 Kb and you can save up to 14.6 Kb
http://illinois.edu/assets/js/weather.js. File size 3.63 Kb and you can save up to 2.72 Kb
http://illinois.edu/assets/css/print-hp.css. File size 6.31 Kb and you can save up to 4.74 Kb
http://illinois.edu/lb/imageList/1292?XSL=NONE&1293715942968. File size 25.91 Kb and you can save up to 19.44 Kb
http://illinois.edu/assets/css/reset.css. File size 1.28 Kb and you can save up to 0.96 Kb
http://illinois.edu/assets/css/hp-layout.css. File size 5.97 Kb and you can save up to 4.47 Kb
http://illinois.edu/assets/css/hp-text.css. File size 5.17 Kb and you can save up to 3.88 Kb
http://illinois.edu/assets/css/sitewide-layout.css. File size 2.61 Kb and you can save up to 1.95 Kb
http://illinois.edu/assets/css/sitewide-text.css. File size 2.58 Kb and you can save up to 1.94 Kb
http://illinois.edu/lb/pc/1267/161.js. File size 9.12 Kb and you can save up to 6.84 Kb
http://illinois.edu/lb/pc/1303/134.js. File size 1.66 Kb and you can save up to 1.25 Kb
http://illinois.edu/lb/pc/72/134.js. File size 1.39 Kb and you can save up to 1.04 Kb
http://illinois.edu/lb/pc/72/135.js. File size 1.92 Kb and you can save up to 1.44 Kb
http://illinois.edu/lb/pc/1426/125.js. File size 20.41 Kb and you can save up to 15.31 Kb
http://illinois.edu/lb/pc/1171/141.js. File size 5.99 Kb and you can save up to 4.5 Kb
http://illinois.edu/lb/pc/1288/138.js. File size 1.25 Kb and you can save up to 0.94 Kb
http://illinois.edu/wpt/web_page_tracker.js. File size 1.02 Kb and you can save up to 0.77 Kb
http://emergency.webservices.illinois.edu/illinois.js. File size 0.01 Kb and you can save up to 0.01 Kb
https://illinois.edu/assets/js/campusSearchBar.js. File size 4.18 Kb and you can save up to 3.14 Kb
https://illinois.edu/webservices/toolbox/pc/ss3/prototype.js. File size 71.26 Kb and you can save up to 53.45 Kb
https://illinois.edu/webservices/toolbox/pc/ss3/effects.js. File size 37.87 Kb and you can save up to 28.4 Kb

Keep Components under 25K

Users often visit web site using a mobile phone. Even the most modern and advanced gadgets have some limitations. For example an iPhone browser do not cache page components bigger than 25K. So you should strive to ensure that scripts, CSS-styles, etc. are less than 25K.
http://illinois.edu/lb/imageList/1292?XSL=NONE&1293715942968  Content-Encoding: text/html. File size 25.91 Kb.
http://illinois.edu/assets/images/homepage/bg_homepage.jpg  Content-Encoding: image/jpeg. File size 76.04 Kb.
http://illinois.edu/assets/images/homepage/illinoisFlashOverlay.png  Content-Encoding: image/png. File size 181.98 Kb.
https://illinois.edu/lb/files/2008/12/19/7173.jpg  Content-Encoding: image/jpeg. File size 44.94 Kb.
https://illinois.edu/lb/files/2008/12/19/7171.jpg  Content-Encoding: image/jpeg. File size 102.27 Kb.
https://illinois.edu/lb/files/2009/11/13/22977.jpg  Content-Encoding: image/jpeg. File size 242.29 Kb.
https://illinois.edu/lb/files/2009/12/21/23764.jpg  Content-Encoding: image/jpeg. File size 575.23 Kb.
https://illinois.edu/lb/files/2010/03/19/25486.jpg  Content-Encoding: image/jpeg. File size 78.06 Kb.
https://illinois.edu/lb/files/2009/12/21/23754.jpg  Content-Encoding: image/jpeg. File size 614.17 Kb.
https://illinois.edu/lb/files/2008/12/19/7181.jpg  Content-Encoding: image/jpeg. File size 76.73 Kb.
https://illinois.edu/lb/files/2008/12/19/7170.jpg  Content-Encoding: image/jpeg. File size 107.42 Kb.
https://illinois.edu/lb/files/2008/12/19/7162.jpg  Content-Encoding: image/jpeg. File size 81.68 Kb.
https://illinois.edu/lb/files/2008/12/19/7159.jpg  Content-Encoding: image/jpeg. File size 42.91 Kb.
https://illinois.edu/webservices/toolbox/pc/ss3/prototype.js  Content-Encoding: application/x-javascript. File size 71.26 Kb.
https://illinois.edu/webservices/toolbox/pc/ss3/effects.js  Content-Encoding: application/x-javascript. File size 37.87 Kb.

Avoid 301 & 302 Redirects

Redirect allows you to make website or page available under many URLs. Webmasters use redirects when their sites change domain name, several websites are merged into one, document is moved too a new location, etc. Using a redirect delays content obtaining. Any delay negatively affects on the user experience. We've detected that page has 2 redirects before page components start loading. The following list contains some of these redirects:
http://illinois.edu/pc/imageList/1292?XSL=NONE&1293715942968 redirects to http://illinois.edu/lb/imageList/1292?XSL=NONE&1293715942968
http://webtools.uiuc.edu/pc/count?url=http://illinois.edu/&title=Unive... redirects to http://illinois.edu/lb/count?url=http://illinois.edu/&title=University...
Try to reduce the number unnecessary redirects.

Alternate text for the images.

As you may already know, search engine that indexes your pages, do not have eyes. And all content you are trying to display on your site is just HTML & CSS code, images, Flash, etc for the robots. It is It's extremely important to describe each of the objects more datailed using ALT, TITLE and other tags.

Our robot has determined that the uiuc.edu page has 11 images, which has no tag ALT. Tag ALT is a text field, that specifies an alternate text for an image. But not only. Search engines consider this tag as a supplemental result for assessing the content of your page entirely. Do not ignore it!

For example your page has this code:
62.   <img src="http://illinois.edu/assets/images/homepage/illinoisFlashOverlay.png" style="position: relative; top: -416px; z-index: 2000;">
We recommend you use rich img code in that place:
62.   <img src="http://illinois.edu/assets/images/homepage/illinoisFlashOverlay.png" style="position: relative; top: -416px; z-index: 2000;" alt="illinois">


P.S. We used keyword for this image that seemed to us most important for your page. But you can go ahead and give to each of 11 images an ALT text. This problem requires responsible approach. No need to put the same text at alt tag of the all images. Imagine that the pictures do not show and try to make sure that users understand what is shown on the picture based on the alt tag

Specify image dimensions

The browser needs to know the actual dimensions of image (width and height) to quickly render webpage.

We have detected that the 18 images has no width and height.

If you do not specify the width and/or height, then in order to correctly display the image browser needs to download it and only then put on the screen. Otherwise, there is a chance browser will display elements under the picture inappropriately as well as the possible presence of "jumping" effect of the page content (until the page load is finished).

We provide below example of how to define the image https://illinois.edu/lb/files/2010/11/23/30588.jpg dimensions:
221.   <img alt="name" src="https://illinois.edu/lb/files/2010/11/23/30588.jpg" width="IMAGE_WIDTH_HERE" height="IMAGE_HEIGHT_HERE">

Using H1 tag

Avoid frequent use of the <Н1> tag. Our robot has found 3 <Н1> tags in the document's body. We recommend you use one <Н1> tag per page only.

Use the TITLE for A tag

As we have already mentioned, search engine bots can not see the site like a people do it. They more focused on the descriptions of certain page elements. That's why we strongly recommend use TITLE operator in the "A" tag. This operator not only describes the page referenced by the page more detailed, but also takes part in the page describing. For example, you have the link on your website:
58.   <a href="http://www.identitystandards.illinois.edu">
We suggest you to remake it in this way:
58.   <a href="http://www.identitystandards.illinois.edu" title="university of illinois">
Of course, you can (and should) use more proper phrase instead of the "university of illinois" that describes the link http://www.identitystandards.illinois.edu.

Number of links on the page

Try to avoid a large number of links on the page. Our robot have found 131 links on this page. Google recommends to keep the number of links fewer than 100. More information about this topic you can find in Google Webmaster Guidelines and in the post "How many links per page?" by Matt Cutts (head of Google’s Webspam team)


Our Mailbox © 2009 — 2011 SiteSpeedLab & SiteSpeedLab.com
Be Quick or Be Dead