Tools & Wizards About Us
nhjww.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nhjww.com

TestPage

Page Load Speed

25.2 sec in total

First Response

1.7 sec

Resources Loaded

23.1 sec

Page Rendered

415 ms

nhjww.com screenshot

About Website

Click here to check amazing Nhjww content. Otherwise, check out these important facts you probably never knew about nhjww.com

南怀瑾文网 南怀瑾文网

Visit nhjww.com

Key Findings

We analyzed Nhjww.com page load time and found that the first response time was 1.7 sec and then it took 23.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

nhjww.com performance score

0

Network Requests Diagram

nhjww.com

1694 ms

pw_core.css

655 ms

core.js

645 ms

pw_ajax.js

775 ms

Deploy.js

628 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 94% of them (75 requests) were addressed to the original Nhjww.com, 3% (2 requests) were made to Wwmm.cn and 3% (2 requests) were made to Zgfofa.nhjww.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Init.phpwind.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.3 kB (58%)

Content Size

348.8 kB

After Optimization

145.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nhjww.com main page is 348.8 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. Images take 113.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 69.2 kB

  • Original 91.7 kB
  • After minification 91.6 kB
  • After compression 22.6 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 69.2 kB or 75% of the original size.

Image Optimization

-23%

Potential reduce by 25.8 kB

  • Original 113.9 kB
  • After minification 88.1 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, Nhjww needs image optimization as it can save up to 25.8 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 85.4 kB

  • Original 113.6 kB
  • After minification 88.1 kB
  • After compression 28.2 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 85.4 kB or 75% of the original size.

CSS Optimization

-78%

Potential reduce by 22.9 kB

  • Original 29.5 kB
  • After minification 27.1 kB
  • After compression 6.6 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. Nhjww.com needs all CSS files to be minified and compressed as it can save up to 22.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (40%)

Requests Now

78

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nhjww.com

nhjww.com

1694 ms

pw_core.css

pw_core.css

655 ms

core.js

core.js

645 ms

pw_ajax.js

pw_ajax.js

775 ms

Deploy.js

Deploy.js

628 ms

global.js

global.js

915 ms

adminview.js

adminview.js

790 ms

app_global.js

app_global.js

705 ms

zh_cn.js

zh_cn.js

391 ms

%E6%96%87%E8%B4%A4%E4%B9%A6%E9%99%A2.gif

%E6%96%87%E8%B4%A4%E4%B9%A6%E9%99%A2.gif

6353 ms

snwh.gif

snwh.gif

1186 ms

22_5_909e4be4dc1f513.jpg

22_5_909e4be4dc1f513.jpg

1564 ms

czg.jpg

czg.jpg

1413 ms

wdns.jpg

wdns.jpg

1227 ms

snlt.gif

snlt.gif

1239 ms

nanxue.gif

nanxue.gif

1641 ms

nhjww.gif

nhjww.gif

1411 ms

rwcl.jpg

rwcl.jpg

1565 ms

zljs.jpg

zljs.jpg

1638 ms

dfg.gif

dfg.gif

1580 ms

jxy.gif

jxy.gif

1741 ms

zgfw.jpg

zgfw.jpg

1902 ms

coolke.gif

coolke.gif

2450 ms

yshin.gif

yshin.gif

2123 ms

8_3907_9f65381fb5693b1.jpg

8_3907_9f65381fb5693b1.jpg

1965 ms

8_3907_1ec721189841848.jpg

8_3907_1ec721189841848.jpg

1972 ms

shlaoku.gif

shlaoku.gif

2130 ms

laoku-2.jpg

laoku-2.jpg

2780 ms

banner.gif

banner.gif

327 ms

logo.jpg

logo.jpg

602 ms

right.gif

right.gif

593 ms

m_bg.gif

m_bg.gif

319 ms

m_1.gif

m_1.gif

344 ms

m_2.gif

m_2.gif

344 ms

style.gif

style.gif

637 ms

search_input.png

search_input.png

658 ms

down.png

down.png

688 ms

search_btn.png

search_btn.png

672 ms

cate_fold.gif

cate_fold.gif

946 ms

22.gif

22.gif

947 ms

5.gif

5.gif

973 ms

17.gif

17.gif

988 ms

23.gif

23.gif

988 ms

4.gif

4.gif

1001 ms

24.gif

24.gif

1342 ms

3.gif

3.gif

1747 ms

21.gif

21.gif

1343 ms

18.gif

18.gif

1377 ms

25.gif

25.gif

1345 ms

16.gif

16.gif

1381 ms

31.gif

31.gif

1671 ms

6.gif

6.gif

1663 ms

Contact%20us.gif

Contact%20us.gif

1719 ms

wap.gif

wap.gif

1720 ms

top.gif

top.gif

1721 ms

%E6%96%87%E6%98%8E%E5%A4%A9%E5%9C%B0.gif

%E6%96%87%E6%98%8E%E5%A4%A9%E5%9C%B0.gif

5932 ms

zgfofa_lj.png

zgfofa_lj.png

2710 ms

c_bg.gif

c_bg.gif

1959 ms

c_1.gif

c_1.gif

1995 ms

c_2.gif

c_2.gif

2058 ms

c_left.gif

c_left.gif

2093 ms

c_right.gif

c_right.gif

2094 ms

button.png

button.png

2108 ms

colon.png

colon.png

2729 ms

anc.gif

anc.gif

2824 ms

dotB.png

dotB.png

2398 ms

init.php

init.php

20310 ms

y.php

y.php

2164 ms

head.gif

head.gif

2129 ms

old.gif

old.gif

2140 ms

f_bg1.gif

f_bg1.gif

2429 ms

f_1.gif

f_1.gif

2189 ms

f_2.gif

f_2.gif

2202 ms

f_bg2.gif

f_bg2.gif

2175 ms

f_a.gif

f_a.gif

2433 ms

f_b.gif

f_b.gif

2506 ms

f_bg3.gif

f_bg3.gif

2437 ms

f_c.gif

f_c.gif

2264 ms

f_d.gif

f_d.gif

2197 ms

top.png

top.png

2229 ms

SEO Factors

nhjww.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nhjww.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 Nhjww.com main page’s claimed encoding is gbk. 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

nhjww.com

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