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 30 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 3507 hours ago
SiteSpeedLab Overall Website Rating for this website
Based on our speed test results table and considering features of the current webserver location
(France, Paris), we concluded overall
This website speed rank is 67.
That means 67% of the sites from the
Paris 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.
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 (83.167.41.117) 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.19s (which is better than 22% of all sites).
For more detailed stats look at DNS tests graph and DNS resolve page for France, Paris location
(Average value on the widget is an average DNS resolve time for websites hosted at the same location).
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
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
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
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
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
NY, New York
282 ms
—
—
—
45% 318/220 ms
Florida, Tampa
278 ms
—
—
—
20% 263/220 ms
Germany
Frankfurt
159 ms
—
—
—
20% 59/49 ms
Canada
Montreal
203 ms
—
—
—
77% 452/256 ms
United Kingdom
Gloucester
29 ms
—
—
—
253% 409/116 ms
Fragment of Paris DNS Speed rating table for this website
The table is constructed according to the data from the US datacenters
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 104.119Kb/s
(which is better than 67% of all sites in this region).
For more detailed stats check out report for Paris 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
Butineo.fr'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.
This is a good practice to give the user content in compressed form.
We've detected 240.55 Kb of content that could be compressed.
By compressing content you can achieve the size of ~ 60.14 Kb
(saving 180.41 Kb). This would accelerate the page loading speed and would positively
impact the bandwidth savings in Neo Telecoms.
http://butineo.fr/styles/core_website/core.css. File size 5.55 Kb and you can save up to 4.16 Kb
http://butineo.fr/includes/butineo_common_includes/incCommonCode.js?ca.... File size 31.16 Kb and you can save up to 23.37 Kb
http://butineo.fr/includes/butineo_common_includes/butineo_common/incS.... File size 18.17 Kb and you can save up to 13.62 Kb
http://butineo.fr/Flash/VM_FlashContent.js. File size 3.54 Kb and you can save up to 2.66 Kb
http://butineo.fr/includes/butineo_common_includes/incFormCode.js. File size 35.31 Kb and you can save up to 26.48 Kb
http://butineo.fr/includes/butineo_common_includes/butineo_common/incR.... File size 14.22 Kb and you can save up to 10.66 Kb
http://butineo.fr/includes/tracking-butineo.js. File size 7.59 Kb and you can save up to 5.69 Kb
http://butineo.fr/styles/core_website/panels.css. File size 20.76 Kb and you can save up to 15.57 Kb
http://butineo.fr/styles/core_website/navigation.css. File size 7.59 Kb and you can save up to 5.7 Kb
http://butineo.fr/styles/core_website/questionnaire.css. File size 16.45 Kb and you can save up to 12.34 Kb
http://butineo.fr/styles/core_website/custom_questionnaires.css. File size 0.12 Kb and you can save up to 0.09 Kb
http://butineo.fr/styles/core_website/registration.css. File size 12.23 Kb and you can save up to 9.17 Kb
http://butineo.fr/styles/core_website/subsidiary.css. File size 13.4 Kb and you can save up to 10.05 Kb
http://butineo.fr/styles/core_website/myaccount.css. File size 11.2 Kb and you can save up to 8.4 Kb
http://butineo.fr/styles/core_website/thankyou.css. File size 7.08 Kb and you can save up to 5.31 Kb
http://butineo.fr/styles/core_website/thankyou_one.css. File size 8.84 Kb and you can save up to 6.63 Kb
http://butineo.fr/styles/core_website/thankyou_two.css. File size 7.34 Kb and you can save up to 5.5 Kb
http://butineo.fr/styles/core_website/thankyou_three.css. File size 10.15 Kb and you can save up to 7.61 Kb
http://butineo.fr/styles/core_website/custom_questionnaires/webbrands.css. File size 1.36 Kb and you can save up to 1.02 Kb
http://butineo.fr/styles/core_website/curseurs_ff.css. File size 0.17 Kb and you can save up to 0.13 Kb
http://butineo.fr/Flash/AC_RunActiveContent.js. File size 8.32 Kb and you can save up to 6.24 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://butineo.fr/ Content-Encoding: text/html; Charset=ISO-8859-1. File size 32.49 Kb.
http://butineo.fr/includes/butineo_common_includes/incCommonCode.js?ca... Content-Encoding: application/x-javascript. File size 31.16 Kb.
http://butineo.fr/includes/butineo_common_includes/incFormCode.js Content-Encoding: application/x-javascript. File size 35.31 Kb.
http://butineo.fr/images/features/btn2LoTree.jpg Content-Encoding: image/jpeg. File size 36.37 Kb.
http://butineo.fr/images/features/ban.jpg Content-Encoding: image/jpeg. File size 33.5 Kb.
http://butineo.fr/images/features/CQ_160x160.jpg Content-Encoding: image/jpeg. File size 50.93 Kb.
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 butineo.fr page has
10
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!
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 10 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 1 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 http://butineo.fr/images/core_website/panels/butineo/alexFB.jpg dimensions:
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.
<ahref="#main-nav">skip to main navigation</a>
We suggest you to remake it in this way:
58.
<ahref="#main-nav"title="en ligne">skip to main navigation</a>
Of course, you can (and should) use more proper phrase instead of the "en ligne" that describes the link #main-nav.