Tools & Wizards About Us
joke58.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

joke58.com

www.joke58.com-官网首页

Page Load Speed

21.6 sec in total

First Response

1 sec

Resources Loaded

20.3 sec

Page Rendered

281 ms

joke58.com screenshot

About Website

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

笑话网-07-20年记录-历史百度权重4

Visit joke58.com

Key Findings

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

joke58.com performance score

0

Network Requests Diagram

joke58.com

1006 ms

www.joke58.com

3452 ms

style5.css

1433 ms

navMenu14.css

501 ms

users.asp

481 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 61% of them (51 requests) were addressed to the original Joke58.com, 6% (5 requests) were made to Pagead2.googlesyndication.com and 6% (5 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (11.4 sec) belongs to the original domain Joke58.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 254.8 kB (29%)

Content Size

892.3 kB

After Optimization

637.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 49.4 kB

  • Original 60.7 kB
  • After minification 60.5 kB
  • After compression 11.4 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.4 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 38.2 kB

  • Original 512.2 kB
  • After minification 474.0 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. Joke 58 images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 139.3 kB

  • Original 284.2 kB
  • After minification 272.6 kB
  • After compression 144.9 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 139.3 kB or 49% of the original size.

CSS Optimization

-80%

Potential reduce by 28.0 kB

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

Requests Breakdown

Number of requests can be reduced by 43 (57%)

Requests Now

75

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

joke58.com

joke58.com

1006 ms

www.joke58.com

www.joke58.com

3452 ms

style5.css

style5.css

1433 ms

navMenu14.css

navMenu14.css

501 ms

users.asp

users.asp

481 ms

time2.js

time2.js

530 ms

jieri.js

jieri.js

530 ms

index.js

index.js

345 ms

swf.js

swf.js

505 ms

common.js

common.js

605 ms

jquery.js

jquery.js

3244 ms

ads.js

ads.js

831 ms

configJs.asp

configJs.asp

337 ms

configJs.js

configJs.js

365 ms

popup.js

popup.js

685 ms

top.js

top.js

752 ms

stat.php

stat.php

604 ms

top_bg.gif

top_bg.gif

286 ms

5

5

1402 ms

rss.gif

rss.gif

227 ms

logo.jpg

logo.jpg

613 ms

top_menuBg.gif

top_menuBg.gif

366 ms

top_menuDz.gif

top_menuDz.gif

341 ms

top_searchDz.gif

top_searchDz.gif

378 ms

top_searchBtn.gif

top_searchBtn.gif

423 ms

show_ads.js

show_ads.js

39 ms

zrt_lookup.html

zrt_lookup.html

49 ms

show_ads_impl.js

show_ads_impl.js

51 ms

2013031647025033.jpg

2013031647025033.jpg

1668 ms

2013031646686753.jpg

2013031646686753.jpg

1810 ms

2013031645603001.jpg

2013031645603001.jpg

1821 ms

2012112666585641.jpg

2012112666585641.jpg

1887 ms

2012083001857376.jpg

2012083001857376.jpg

3027 ms

2012083002057516.jpg

2012083002057516.jpg

2797 ms

2012061581179121.jpg

2012061581179121.jpg

4635 ms

2012061580904169.jpg

2012061580904169.jpg

4724 ms

OT20120325161219108.jpg

OT20120325161219108.jpg

4406 ms

OT20120325161301108.jpg

OT20120325161301108.jpg

4144 ms

OT20120325161214320.jpg

OT20120325161214320.jpg

4648 ms

OT20120325161259542.jpg

OT20120325161259542.jpg

11419 ms

OT20120325161005219.jpg

OT20120325161005219.jpg

7757 ms

OT20120325161006431.jpg

OT20120325161006431.jpg

9185 ms

OT20120325160958542.jpg

OT20120325160958542.jpg

10269 ms

ads

ads

37 ms

index_announ.gif

index_announ.gif

5051 ms

arrow1.gif

arrow1.gif

5054 ms

index_new.gif

index_new.gif

5474 ms

osd.js

osd.js

37 ms

index_recom.gif

index_recom.gif

5467 ms

arrow2.gif

arrow2.gif

5905 ms

item.gif

item.gif

5937 ms

arrow3.gif

arrow3.gif

6417 ms

adsbygoogle.js

adsbygoogle.js

12 ms

ca-pub-5321988207656416.js

ca-pub-5321988207656416.js

88 ms

ads

ads

32 ms

item2.gif

item2.gif

6380 ms

z_stat.php

z_stat.php

1009 ms

stat.htm

stat.htm

1367 ms

core.php

core.php

1983 ms

beijing

beijing

1976 ms

9.gif

9.gif

1631 ms

pic.gif

pic.gif

1079 ms

links.htm

links.htm

3949 ms

bottom_logo.gif

bottom_logo.gif

3963 ms

shell_v2.js

shell_v2.js

3710 ms

stat.htm

stat.htm

180 ms

core.php

core.php

455 ms

494 ms

9.gif

9.gif

1560 ms

TrojanInspect.aspx

TrojanInspect.aspx

1061 ms

model5.css

model5.css

1792 ms

c.php

c.php

1689 ms

popup.js

popup.js

3550 ms

popup.css

popup.css

2848 ms

style.css

style.css

3263 ms

tdflagx1.gif

tdflagx1.gif

3185 ms

app.gif

app.gif

8226 ms

app.gif

app.gif

5181 ms

stat.htm

stat.htm

674 ms

core.php

core.php

1177 ms

logger.js

logger.js

326 ms

bds_s_v2.js

bds_s_v2.js

1177 ms

bdsstyle.css

bdsstyle.css

299 ms

l7.gif

l7.gif

289 ms

SEO Factors

joke58.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    GB2312

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

joke58.com

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