Tools & Wizards About Us
or.tl screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

or.tl

無料ダイナミックDNS(DDNS)サービス - ieServer.Net

Page Load Speed

2.7 sec in total

First Response

946 ms

Resources Loaded

1.6 sec

Page Rendered

118 ms

or.tl screenshot

About Website

Click here to check amazing Or content for China. Otherwise, check out these important facts you probably never knew about or.tl

家サーバー・プロジェクトでは、自宅でインターネットサーバーを動かす皆さんを支援する為に、ダイナミックDNS(DDNS)を無料提供します。提供ドメインは dip.jp, jpn.ph, fam.cx, myhome.cx, moe.hm, org.hmの６種類。

Visit or.tl

Key Findings

We analyzed Or.tl page load time and found that the first response time was 946 ms and then it took 1.7 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.

Performance Metrics

or.tl performance score

0

Network Requests Diagram

or.tl

946 ms

urchin.js

23 ms

__utm.gif

12 ms

bg.gif

406 ms

titleG.gif

608 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 12% of them (4 requests) were addressed to the original Or.tl, 15% (5 requests) were made to Googleads.g.doubleclick.net and 15% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (946 ms) belongs to the original domain Or.tl.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.8 kB (55%)

Content Size

47.3 kB

After Optimization

21.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Or.tl main page is 47.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 23.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.6 kB

  • Original 19.5 kB
  • After minification 16.0 kB
  • After compression 4.9 kB

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. This page needs HTML code to be minified as it can gain 3.5 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.6 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 396 B

  • Original 4.3 kB
  • After minification 3.9 kB

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. Or images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 10.7 kB

  • Original 23.0 kB
  • After minification 22.9 kB
  • After compression 12.3 kB

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 10.7 kB or 46% of the original size.

CSS Optimization

-27%

Potential reduce by 127 B

  • Original 469 B
  • After minification 425 B
  • After compression 342 B

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. Or.tl needs all CSS files to be minified and compressed as it can save up to 127 B or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (50%)

Requests Now

28

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Or. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

or.tl

or.tl

946 ms

urchin.js

urchin.js

23 ms

__utm.gif

__utm.gif

12 ms

bg.gif

bg.gif

406 ms

titleG.gif

titleG.gif

608 ms

btn_donateCC_LG.gif

btn_donateCC_LG.gif

368 ms

bgt

bgt

342 ms

pixel.gif

pixel.gif

96 ms

0.gif

0.gif

548 ms

bgt

bgt

565 ms

0.gif

0.gif

545 ms

show_ads.js

show_ads.js

44 ms

agoramail.gif

agoramail.gif

446 ms

ca-pub-3802694033433431.js

ca-pub-3802694033433431.js

63 ms

zrt_lookup.html

zrt_lookup.html

64 ms

show_ads_impl.js

show_ads_impl.js

67 ms

ads

ads

300 ms

osd.js

osd.js

14 ms

ads

ads

228 ms

ads

ads

393 ms

abg.js

abg.js

42 ms

css

css

66 ms

m_js_controller.js

m_js_controller.js

20 ms

favicon

favicon

81 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

24 ms

s

s

17 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

151 ms

x_button_blue2.png

x_button_blue2.png

12 ms

css

css

22 ms

favicon

favicon

122 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

15 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

174 ms

ui

ui

81 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

151 ms

SEO Factors

or.tl SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Or.tl can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Or.tl main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

or.tl

Open Graph description is not detected on the main page of Or. 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: