Tools & Wizards About Us
neihanshequ.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

neihanshequ.com

【内涵段子官网】搞笑段子，图片，视频，直播社区 - 内涵社区(www.neihanshequ.com)

Page Load Speed

29.2 sec in total

First Response

4.2 sec

Resources Loaded

24.4 sec

Page Rendered

541 ms

neihanshequ.com screenshot

About Website

Welcome to neihanshequ.com homepage info - get ready to check Neihanshequ best content for China right away, or after learning these important things about neihanshequ.com

国民级轻松搞笑社区，网络热辣段子发源地，包含各类短视频、脑洞神评论、图片、段子、精华等。内涵的不只是段子！

Visit neihanshequ.com

Key Findings

We analyzed Neihanshequ.com page load time and found that the first response time was 4.2 sec and then it took 25 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.

Performance Metrics

neihanshequ.com performance score

0

Network Requests Diagram

neihanshequ.com

4244 ms

common_5a9b1ea.css

3112 ms

common_17a88da.css

3119 ms

pagelet_8d5867c.css

5744 ms

index_b0da364.css

3663 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Neihanshequ.com, 33% (18 requests) were made to S2.pstatp.com and 25% (14 requests) were made to S0.pstatp.com. The less responsive or slowest element that took the longest time to load (15.5 sec) relates to the external source Q.qlogo.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.4 kB (60%)

Content Size

499.9 kB

After Optimization

200.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Neihanshequ.com main page is 499.9 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 301.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 49.5 kB

  • Original 63.4 kB
  • After minification 57.1 kB
  • After compression 13.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. 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 49.5 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 756 B

  • Original 98.4 kB
  • After minification 97.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. Neihanshequ images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 221.0 kB

  • Original 301.4 kB
  • After minification 279.1 kB
  • After compression 80.4 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 221.0 kB or 73% of the original size.

CSS Optimization

-77%

Potential reduce by 28.2 kB

  • Original 36.8 kB
  • After minification 36.8 kB
  • After compression 8.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. Neihanshequ.com needs all CSS files to be minified and compressed as it can save up to 28.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (54%)

Requests Now

54

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neihanshequ. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

neihanshequ.com

neihanshequ.com

4244 ms

common_5a9b1ea.css

common_5a9b1ea.css

3112 ms

common_17a88da.css

common_17a88da.css

3119 ms

pagelet_8d5867c.css

pagelet_8d5867c.css

5744 ms

index_b0da364.css

index_b0da364.css

3663 ms

lib_8b2e779.js

lib_8b2e779.js

3156 ms

underscore_3d00f9f.js

underscore_3d00f9f.js

2354 ms

core_9b729c5.js

core_9b729c5.js

2924 ms

pagelet_d7a7ec9.js

pagelet_d7a7ec9.js

2240 ms

common_77b32db.js

common_77b32db.js

4240 ms

hm.js

hm.js

2230 ms

duanzi_new_98a9323.png

duanzi_new_98a9323.png

552 ms

yisi_47bf37d.png

yisi_47bf37d.png

453 ms

create_6dc71fd.png

create_6dc71fd.png

1598 ms

joke_jokeessay_new_c0cceed.png

joke_jokeessay_new_c0cceed.png

1857 ms

apple_f1d8cd0.png

apple_f1d8cd0.png

926 ms

phone_new_93c60d5.png

phone_new_93c60d5.png

926 ms

logo_741b09e.png

logo_741b09e.png

1151 ms

complain_64d5e94.png

complain_64d5e94.png

560 ms

login_c1be955.png

login_c1be955.png

560 ms

qrcode_joke_essay_a60675d.png

qrcode_joke_essay_a60675d.png

592 ms

backTop_e8b77a0.png

backTop_e8b77a0.png

1151 ms

android_174ebda.png

android_174ebda.png

882 ms

bury_2eed8c8.png

bury_2eed8c8.png

1038 ms

repin_3a60097.png

repin_3a60097.png

1071 ms

comment_29f6e62.png

comment_29f6e62.png

1345 ms

score_abc2489.png

score_abc2489.png

1343 ms

qq_weibo_4528205.png

qq_weibo_4528205.png

2155 ms

qzone_sns_baebea1.png

qzone_sns_baebea1.png

1621 ms

digg_7ad8226.png

digg_7ad8226.png

1079 ms

share_67b66b0.png

share_67b66b0.png

1079 ms

sina_weibo_728a7a2.png

sina_weibo_728a7a2.png

1118 ms

up_3b7bf0c.png

up_3b7bf0c.png

3285 ms

1588 ms

bds_s_360.js

bds_s_360.js

1902 ms

41100035aa73c82cd76

41100035aa73c82cd76

1773 ms

40

40

15478 ms

46

46

5248 ms

2b7000ec2234240ac90

2b7000ec2234240ac90

576 ms

14f0018f6f35fb4777b

14f0018f6f35fb4777b

1979 ms

head_50.jpg

head_50.jpg

525 ms

46

46

5249 ms

46

46

5247 ms

2b60022a8187cc186b1

2b60022a8187cc186b1

572 ms

2062247312

2062247312

573 ms

3871559161

3871559161

572 ms

4110002d8eca95cc3e8

4110002d8eca95cc3e8

572 ms

14f00254c07633c6891

14f00254c07633c6891

573 ms

2b600229f3fc36f2ff4

2b600229f3fc36f2ff4

580 ms

5371175959

5371175959

1764 ms

3458474126

3458474126

1816 ms

1390987509

1390987509

2433 ms

4d00124d90f74de17a

4d00124d90f74de17a

2721 ms

40

40

15516 ms

hm.gif

hm.gif

1126 ms

SEO Factors

neihanshequ.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neihanshequ.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Neihanshequ.com 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

neihanshequ.com

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