oe.cd website information.
oe.cd domain name is registered by .CD top-level domain registry. See the other sites registred in .CD domain zone.
No name server records were found.
and probably website oe.cd is hosted by AMAZON-02 - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-02 - Amazon.com, Inc., US hosting company.
According to Alexa traffic rank the highest website oe.cd position was 55945 (in the world). The lowest Alexa rank position was 965918. Now website oe.cd ranked in Alexa database as number 208933 (in the world).
Website oe.cd Desktop speed measurement score (78/100) is better than the results of 65.98% of other sites shows that the page desktop performance can be improved.
oe.cd Mobile usability score (60/100) is better than the results of 3.95% of other sites and shows that the page mobile usability is poor and can be improved.
Mobile speed measurement score of oe.cd (60/100) is better than the results of 54.7% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Nov-17-2024 | 208,933 | 3,157 |
| Nov-16-2024 | 212,090 | -2,711 |
| Nov-15-2024 | 209,379 | -1,554 |
| Nov-14-2024 | 207,825 | -5,749 |
| Nov-13-2024 | 202,076 | 0 |
| Nov-12-2024 | 202,076 | 0 |
| Nov-11-2024 | 202,076 | 0 |
Advertisement
oe.cd Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
oe.cd whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
oe.cd domain is not supported
oe.cd server information
Servers Location
| IP Address |
|---|
| Country |
|---|
oe.cd desktop page speed rank
Last tested: 2018-05-19
oe.cd Desktop Speed Test Quick Summary
priority - 12 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 6 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://oe.cd/site/js/jquery.tmpl.js
https://oe.cd/site/js/oecd.js
https://oe.cd/site/js/message.js
https://oe.cd/site/js/date.js
https://oe.cd/site/js/jquery.sparkline.js
Optimize CSS Delivery of the following:
priority - 5 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://oe.cd/site/img/logo.gif (expiration not specified)
https://oe.cd/site/img/spin_16_e5ecf9.gif (expiration not specified)
https://oe.cd/site/img/spin_24_e5ecf9.gif (expiration not specified)
https://oe.cd/site/js/date.js (expiration not specified)
https://oe.cd/site/js/jquery.sparkline.js (expiration not specified)
https://oe.cd/site/js/jquery.tmpl.js (expiration not specified)
https://oe.cd/site/js/message.js (expiration not specified)
https://oe.cd/site/js/oecd.js (expiration not specified)
priority - 4 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 36.9KiB (79% reduction).
Compressing https://oe.cd/site/api.php?action=stats_traffic&ur…ce=get_all&format=json could save 207B (52% reduction).
priority - 3 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 34KiB (41% reduction).
Minifying https://oe.cd/site/js/jquery.sparkline.js could save 8.8KiB (38% reduction) after compression.
Minifying https://oe.cd/site/js/jquery.tmpl.js could save 3KiB (49% reduction) after compression.
Minifying https://oe.cd/site/js/oecd.js could save 1.5KiB (41% reduction) after compression.
Minifying https://oe.cd/site/js/message.js could save 128B (31% reduction) after compression.
priority - 2 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 0 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 4KiB (40% reduction).
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 346B (16% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 281B (15% reduction).
oe.cd Desktop Resources
| Total Resources | 14 |
| Number of Hosts | 2 |
| Static Resources | 10 |
| JavaScript Resources | 8 |
| CSS Resources | 1 |
oe.cd Desktop Resource Breakdown
oe.cd mobile page speed rank
Last tested: 2018-06-06
oe.cd Mobile Speed Test Quick Summary
priority - 48 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 6 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://oe.cd/site/js/jquery.tmpl.js
https://oe.cd/site/js/oecd.js
https://oe.cd/site/js/message.js
https://oe.cd/site/js/date.js
https://oe.cd/site/js/jquery.sparkline.js
Optimize CSS Delivery of the following:
priority - 8 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 7 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://oe.cd/site/img/logo.gif (expiration not specified)
https://oe.cd/site/img/spin_16_e5ecf9.gif (expiration not specified)
https://oe.cd/site/img/spin_24_e5ecf9.gif (expiration not specified)
https://oe.cd/site/js/date.js (expiration not specified)
https://oe.cd/site/js/jquery.sparkline.js (expiration not specified)
https://oe.cd/site/js/jquery.tmpl.js (expiration not specified)
https://oe.cd/site/js/message.js (expiration not specified)
https://oe.cd/site/js/oecd.js (expiration not specified)
priority - 4 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 36.2KiB (80% reduction).
Compressing https://oe.cd/site/api.php?action=stats_traffic&ur…ce=get_all&format=json could save 270B (56% reduction).
priority - 3 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 34KiB (41% reduction).
Minifying https://oe.cd/site/js/jquery.sparkline.js could save 8.8KiB (38% reduction) after compression.
Minifying https://oe.cd/site/js/jquery.tmpl.js could save 3KiB (49% reduction) after compression.
Minifying https://oe.cd/site/js/oecd.js could save 1.5KiB (41% reduction) after compression.
Minifying https://oe.cd/site/js/message.js could save 128B (31% reduction) after compression.
priority - 0 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 4KiB (40% reduction).
priority - 0 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 346B (16% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 281B (15% reduction).
oe.cd Mobile Resources
| Total Resources | 14 |
| Number of Hosts | 2 |
| Static Resources | 10 |
| JavaScript Resources | 8 |
| CSS Resources | 1 |
oe.cd Mobile Resource Breakdown
oe.cd mobile page usability
Last tested: 2018-06-06
oe.cd Mobile Usability Test Quick Summary
priority - 40 Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Paste your long URL here: renders only 5 pixels tall (13 CSS pixels).Shorten and 2 others render only 5 pixels tall (13 CSS pixels).Only OECD-rela…this website. renders only 5 pixels tall (13 CSS pixels).Click statistics: and 1 others render only 5 pixels tall (13 CSS pixels).All time and 1 others render only 5 pixels tall (13 CSS pixels).Data Portal and 11 others render only 5 pixels tall (13 CSS pixels).Restrict search results to: renders only 5 pixels tall (13 CSS pixels).Long URL renders only 5 pixels tall (13 CSS pixels).Short URL and 1 others render only 5 pixels tall (13 CSS pixels).Clicks renders only 5 pixels tall (13 CSS pixels).www.oecd-ilibr…_campaign=pbsm and 29 others render only 5 pixels tall (13 CSS pixels).6 Jun 2018 and 14 others render only 5 pixels tall (13 CSS pixels).879 and 16 others render only 5 pixels tall (13 CSS pixels).Details » and 14 others render only 5 pixels tall (13 CSS pixels).Page and 1 others render only 5 pixels tall (13 CSS pixels).Older › renders only 5 pixels tall (13 CSS pixels).Powered by Yourls and 2 others render only 5 pixels tall (13 CSS pixels).priority - 21 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<button id="search_button" type="submit">Search</button> is close to 1 other tap targets.<button id="all_time" type="button" class="button button-selected">All time</button> is close to 1 other tap targets.<button id="month" type="button" class="button">Month</button> and 4 others are close to other tap targets.<button id="namespace_fp" type="button" class="button">FreePreview</button> and 1 others are close to other tap targets.<a href="https://oe.cd/2ii" class="info">oe.cd/2ii</a> and 28 others are close to other tap targets.<a href="https://oe.cd/2ii+">7</a> and 14 others are close to other tap targets.<a href="https://oe.cd/2ii+" class="details"></a> and 14 others are close to other tap targets.<canvas> and 14 others are close to other tap targets.<a href="https://oe.cd/2ii+" class="details">Details »</a> and 14 others are close to other tap targets.<a id="older" href="#">Older ›</a> is close to 1 other tap targets.priority - 10 Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
Configure a viewport for this page.
oe.cd similar domains
www.oe.net
www.oe.org
www.oe.info
www.oe.biz
www.oe.us
www.oe.mobi
www.e.cd
www.oe.cd
www.ie.cd
www.oie.cd
www.ioe.cd
www.ke.cd
www.oke.cd
www.koe.cd
www.le.cd
www.ole.cd
www.loe.cd
www.pe.cd
www.ope.cd
www.poe.cd
www.o.cd
www.ow.cd
www.oew.cd
www.owe.cd
www.os.cd
www.oes.cd
www.ose.cd
www.od.cd
www.oed.cd
www.ode.cd
www.or.cd
www.oer.cd
www.ore.cd
oe.cd Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
oe.cd TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.