Tools & Wizards About Us
ierle.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ierle.com

www.ierle.com-官网首页

Page Load Speed

44.3 sec in total

First Response

4.4 sec

Resources Loaded

39.6 sec

Page Rendered

301 ms

ierle.com screenshot

About Website

Visit ierle.com now to see the best up-to-date Ierle content and also check out these interesting facts you probably never knew about ierle.com

买域名找4.cn-angel.+地球angel4cn

Visit ierle.com

Key Findings

We analyzed Ierle.com page load time and found that the first response time was 4.4 sec and then it took 39.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ierle.com performance score

0

Network Requests Diagram

ierle.com

4388 ms

global.css

1196 ms

default.css

3658 ms

jquery.min.js

10352 ms

thea9.js

1786 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 38% of them (19 requests) were addressed to the original Ierle.com, 12% (6 requests) were made to Pos.baidu.com and 10% (5 requests) were made to T10.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source T10.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 225.0 kB (36%)

Content Size

628.1 kB

After Optimization

403.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ierle.com main page is 628.1 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. 20% of websites need less resources to load. Javascripts take 288.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 30.6 kB

  • Original 40.4 kB
  • After minification 38.0 kB
  • After compression 9.8 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. 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 30.6 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 2.4 kB

  • Original 288.0 kB
  • After minification 285.6 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. Ierle images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 183.5 kB

  • Original 288.6 kB
  • After minification 288.6 kB
  • After compression 105.1 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 183.5 kB or 64% of the original size.

CSS Optimization

-77%

Potential reduce by 8.5 kB

  • Original 11.1 kB
  • After minification 9.6 kB
  • After compression 2.5 kB

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. Ierle.com needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (42%)

Requests Now

45

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ierle.com

ierle.com

4388 ms

global.css

global.css

1196 ms

default.css

default.css

3658 ms

jquery.min.js

jquery.min.js

10352 ms

thea9.js

thea9.js

1786 ms

thea10.js

thea10.js

1204 ms

logo.png

logo.png

5840 ms

top_bg_s1.png

top_bg_s1.png

581 ms

c.js

c.js

1260 ms

hcnm

hcnm

947 ms

f.js

f.js

699 ms

hcnm

hcnm

714 ms

title1_bg.png

title1_bg.png

1744 ms

icon2.png

icon2.png

600 ms

zsjz_bg.png

zsjz_bg.png

598 ms

rmjyzx_title.png

rmjyzx_title.png

615 ms

icon1.png

icon1.png

598 ms

title2_bg.png

title2_bg.png

1196 ms

icon3.png

icon3.png

1194 ms

title3_bg.png

title3_bg.png

1200 ms

title1_bg.png

title1_bg.png

1236 ms

left-1.png

left-1.png

8815 ms

right-1.png

right-1.png

8240 ms

h.js

h.js

1089 ms

hcnm

hcnm

1357 ms

hcnm

hcnm

1359 ms

21.gif

21.gif

1201 ms

s.js

s.js

2029 ms

hm.gif

hm.gif

760 ms

sync.htm

sync.htm

507 ms

ctm3.js

ctm3.js

487 ms

adx.php

adx.php

899 ms

u=1900256841,2357267496&fm=76

u=1900256841,2357267496&fm=76

3882 ms

u=1303544578,1541255543&fm=76

u=1303544578,1541255543&fm=76

1335 ms

reduce_bd-logo1_oper.png

reduce_bd-logo1_oper.png

509 ms

u=1273266684,1785469289&fm=76

u=1273266684,1785469289&fm=76

4598 ms

u=2676907194,745992136&fm=76

u=2676907194,745992136&fm=76

9397 ms

u=1879363596,3002839177&fm=76

u=1879363596,3002839177&fm=76

20296 ms

u=1856700798,2255477222&fm=76

u=1856700798,2255477222&fm=76

2016 ms

u=1839097243,1734846007&fm=76

u=1839097243,1734846007&fm=76

20294 ms

u=1673373481,2131241023&fm=76

u=1673373481,2131241023&fm=76

5354 ms

0f000rbhL7DsuS4JxbNB00.jpg

0f000rbhL7DsuS4JxbNB00.jpg

1100 ms

sync_pos.htm

sync_pos.htm

513 ms

sync2r.htm

sync2r.htm

1017 ms

o.htm

o.htm

1080 ms

hm.gif

hm.gif

706 ms

wh.js

wh.js

744 ms

ac.js

ac.js

507 ms

fp.htm

fp.htm

813 ms

fp.htm

fp.htm

242 ms

SEO Factors

ierle.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ierle.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ierle.com main page’s claimed encoding is gb2312. 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

ierle.com

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