Analyze

contact.oecd.org: OECD Account Management

Page load speed analysis

  • 59/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    823 ms

  • Resources loaded

    1.8 sec

  • Page rendered

    170 ms

  • Total page load time

    2.8 sec

Visit contact.oecd.org now to see the best up-to-date Contact OECD content for United States and also check out these interesting facts you probably never knew about contact.oecd.org

We analyzed Contact.oecd.org page load time and found that the first response time was 823 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Page optimization

  • HTML 28.9 kB
    Images 19.4 kB
    Javascripts 54.8 kB
    CSS 15.7 kB

    In fact, the total size of Contact.oecd.org main page is 118.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 54.8 kB which makes up the majority of the site volume.

    • Original 28.9 kB
    • After minification 26.9 kB
    • After compression 9.1 kB

    HTML optimization

    HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.8 kB or 68% of the original size.

    • Original 19.4 kB
    • After optimization 15.9 kB

    Image optimization

    Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Contact OECD needs image optimization as it can save up to 3.5 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

    • Original 54.8 kB
    • After minification 35.7 kB
    • After compression 9.1 kB

    JavaScript optimization

    It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 45.6 kB or 83% of the original size.

    • Original 15.7 kB
    • After minification 11.2 kB
    • After compression 3.1 kB

    CSS optimization

    CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Contact.oecd.org needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 80% of the original size.

Network requests diagram

  • contact.oecd.org
  • master.css
  • main.css
  • thickbox.css
  • fonct.js
  • WebResource.axd
  • WebResource.axd
  • AutoRefresh.aspx
  • logooecd_en.png
  • bandoGeneric.jpg
  • TabGauche.gif
  • TabDroite.gif
  • GetImg.aspx
  • background.gif

Our browser made a total of 14 requests to load all elements on the main page. We found that 93% of them (13 requests) were addressed to the original Contact.oecd.org, 7% (1 request) were made to Oecd.org. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Oecd.org.

Additional info on contact.oecd.org

Requests

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Contact OECD. According to our analytics all requests are already optimized.

3

Javascripts

6

Images

3

CSS

1

AJAX

13

All

Possible request optimization

3

Javascripts

6

Images

3

CSS

1

AJAX

0

Optimized

13

All

Good result

IP address

Contact.oecd.org uses IP address which is currently shared with 3 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

contact.oecd.org

webnet.oecd.org

acts.oecd.org

iomctoolbox.oecd.org

78.41.128.131

DNS records

Type Host Target/ip TTL Other
A

webnet.wip.oecd.org

78.41.128.131 68
CNAME

contact.oecd.org

webnet.wip.oecd.org 659

Language and encoding

Normal result

Language

EN en language flag

Detected

N/A  language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contact.oecd.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Contact.oecd.org main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

HTTPS certificate

SSL Certificate

Contact.oecd.org has a valid and up-to-date SSL certificate that expires on January 28, 2019.

Good result

Visitor World Map

Country of origin for 10.6% of all visits is United States. It lies approximately 4680 miles away from the server location (France) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up Contact.oecd.org page load time for the majority of users is moving the server to United States or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of Contact OECD. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

contact.oecd.org

Share this report in social media

Analyze another website

Analyze