Tools & Wizards About Us
ihlj.top screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ihlj.top

ihlj.top 售卖中

Page Load Speed

51.3 sec in total

First Response

4 sec

Resources Loaded

46.8 sec

Page Rendered

545 ms

ihlj.top screenshot

About Website

Click here to check amazing Ihlj content. Otherwise, check out these important facts you probably never knew about ihlj.top

Visit ihlj.top

Key Findings

We analyzed Ihlj.top page load time and found that the first response time was 4 sec and then it took 47.3 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

ihlj.top performance score

0

Network Requests Diagram

ihlj.top

3965 ms

style.css

13870 ms

common.js

4232 ms

index.js

808 ms

qq.css

788 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that all of those requests were addressed to Ihlj.top and no external sources were called. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Ihlj.top.

Page Optimization Overview & Recommendations

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

Content Size

175.1 kB

After Optimization

78.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ihlj.top main page is 175.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. Only 10% of websites need less resources to load. Images take 70.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 28.3 kB

  • Original 34.4 kB
  • After minification 29.1 kB
  • After compression 6.2 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 5.3 kB, which is 15% 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 28.3 kB or 82% of the original size.

Image Optimization

-18%

Potential reduce by 12.6 kB

  • Original 70.8 kB
  • After minification 58.3 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. Obviously, Ihlj needs image optimization as it can save up to 12.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 30.0 kB

  • Original 38.6 kB
  • After minification 26.9 kB
  • After compression 8.6 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 30.0 kB or 78% of the original size.

CSS Optimization

-82%

Potential reduce by 25.7 kB

  • Original 31.2 kB
  • After minification 23.6 kB
  • After compression 5.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. Ihlj.top needs all CSS files to be minified and compressed as it can save up to 25.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (9%)

Requests Now

46

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ihlj.top

ihlj.top

3965 ms

style.css

style.css

13870 ms

common.js

common.js

4232 ms

index.js

index.js

808 ms

qq.css

qq.css

788 ms

ServiceQQ.js

ServiceQQ.js

1199 ms

utils.js

utils.js

929 ms

cycle_image.js

cycle_image.js

1353 ms

logo.gif

logo.gif

12792 ms

xhhlb200.jpg

xhhlb200.jpg

14882 ms

79_thumb_G_1439904840294.jpg

79_thumb_G_1439904840294.jpg

9697 ms

77_thumb_G_1439904804527.jpg

77_thumb_G_1439904804527.jpg

9709 ms

78_thumb_G_1439904816791.jpg

78_thumb_G_1439904816791.jpg

10851 ms

73_thumb_G_1439904726652.jpg

73_thumb_G_1439904726652.jpg

9859 ms

74_thumb_G_1439904760093.jpg

74_thumb_G_1439904760093.jpg

11297 ms

75_thumb_G_1439904780026.jpg

75_thumb_G_1439904780026.jpg

11281 ms

76_thumb_G_1439904795650.jpg

76_thumb_G_1439904795650.jpg

11315 ms

81_thumb_G_1439904888109.jpg

81_thumb_G_1439904888109.jpg

13881 ms

82_thumb_G_1439904902527.jpg

82_thumb_G_1439904902527.jpg

12202 ms

83_thumb_G_1439904940839.jpg

83_thumb_G_1439904940839.jpg

14514 ms

64_thumb_G_1439904586360.jpg

64_thumb_G_1439904586360.jpg

12207 ms

63_thumb_G_1439904577523.jpg

63_thumb_G_1439904577523.jpg

12603 ms

65_thumb_G_1439904594014.jpg

65_thumb_G_1439904594014.jpg

12619 ms

66_thumb_G_1439904641913.jpg

66_thumb_G_1439904641913.jpg

12996 ms

67_thumb_G_1439904647932.jpg

67_thumb_G_1439904647932.jpg

13032 ms

68_thumb_G_1439904653309.jpg

68_thumb_G_1439904653309.jpg

20228 ms

69_thumb_G_1439904659574.jpg

69_thumb_G_1439904659574.jpg

13419 ms

70_thumb_G_1439904692219.jpg

70_thumb_G_1439904692219.jpg

13418 ms

71_thumb_G_1439904700165.jpg

71_thumb_G_1439904700165.jpg

13871 ms

72_thumb_G_1439904714977.jpg

72_thumb_G_1439904714977.jpg

13874 ms

43_thumb_G_1430215211563.jpg

43_thumb_G_1430215211563.jpg

14259 ms

49_thumb_G_1430214359393.jpg

49_thumb_G_1430214359393.jpg

14306 ms

48_thumb_G_1430214507348.jpg

48_thumb_G_1430214507348.jpg

15357 ms

41_thumb_G_1430215565383.jpg

41_thumb_G_1430215565383.jpg

14626 ms

42_thumb_G_1430215429761.jpg

42_thumb_G_1430215429761.jpg

16056 ms

sanjiao1.gif

sanjiao1.gif

14927 ms

header_bg.gif

header_bg.gif

15145 ms

search_input.gif

search_input.gif

15289 ms

bnt_search.gif

bnt_search.gif

16987 ms

wangxia.gif

wangxia.gif

15460 ms

tuchu.gif

tuchu.gif

17462 ms

background.gif

background.gif

16879 ms

buy_car_bg1.gif

buy_car_bg1.gif

17438 ms

jiesuan_bg.gif

jiesuan_bg.gif

16406 ms

data.js

data.js

7141 ms

newart_tit.gif

newart_tit.gif

7600 ms

bg.gif

bg.gif

20365 ms

tit1.gif

tit1.gif

6566 ms

biao1.gif

biao1.gif

6455 ms

help_line.gif

help_line.gif

6640 ms

footer_dlbg.gif

footer_dlbg.gif

6681 ms

SEO Factors

ihlj.top SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ihlj.top 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 Ihlj.top 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.

Social Sharing Optimization

ihlj.top

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