Tools & Wizards About Us
52rr.net screenshot

Report Summary

  • 0

    Performance

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

52rr.net

Page Load Speed

7.4 sec in total

First Response

591 ms

Resources Loaded

6.6 sec

Page Rendered

207 ms

52rr.net screenshot

About Website

Welcome to 52rr.net homepage info - get ready to check 52 Rr best content for United States right away, or after learning these important things about 52rr.net

人人美剧－中国最大美剧社区,由人人影视转型后专门为美剧迷们打造的高质量讨论交流社区

Visit 52rr.net

Key Findings

We analyzed 52rr.net page load time and found that the first response time was 591 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize 52rr.net rating and web reputation

Performance Metrics

52rr.net performance score

0

Network Requests Diagram

52rr.net

591 ms

forum.php

261 ms

style_2_common.css

350 ms

style_2_forum_index.css

323 ms

common.js

499 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 90% of them (57 requests) were addressed to the original 52rr.net, 2% (1 request) were made to Discuz.gtimg.cn and 2% (1 request) were made to S11.cnzz.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Discuz.gtimg.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 223.3 kB (63%)

Content Size

354.5 kB

After Optimization

131.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 52rr.net main page is 354.5 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. 30% of websites need less resources to load. Javascripts take 149.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 26.9 kB

  • Original 34.4 kB
  • After minification 32.7 kB
  • After compression 7.5 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 26.9 kB or 78% of the original size.

Image Optimization

-20%

Potential reduce by 16.3 kB

  • Original 81.4 kB
  • After minification 65.2 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, 52 Rr needs image optimization as it can save up to 16.3 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-73%

Potential reduce by 109.7 kB

  • Original 149.7 kB
  • After minification 125.4 kB
  • After compression 40.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 109.7 kB or 73% of the original size.

CSS Optimization

-79%

Potential reduce by 70.5 kB

  • Original 89.0 kB
  • After minification 87.2 kB
  • After compression 18.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. 52rr.net needs all CSS files to be minified and compressed as it can save up to 70.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (22%)

Requests Now

58

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

52rr.net

52rr.net

591 ms

forum.php

forum.php

261 ms

style_2_common.css

style_2_common.css

350 ms

style_2_forum_index.css

style_2_forum_index.css

323 ms

common.js

common.js

499 ms

forum.js

forum.js

345 ms

msclass.js

msclass.js

341 ms

discuz_tips.js

discuz_tips.js

2552 ms

body.gif

body.gif

171 ms

body.jpg

body.jpg

341 ms

toptb.png

toptb.png

172 ms

tpipe.png

tpipe.png

160 ms

elogin.png

elogin.png

166 ms

eis.png

eis.png

173 ms

eis_pop.gif

eis_pop.gif

319 ms

logo.png

logo.png

330 ms

logor.png

logor.png

340 ms

nv.png

nv.png

340 ms

search.gif

search.gif

340 ms

nv_a.png

nv_a.png

476 ms

nv_li.png

nv_li.png

490 ms

wp_l.png

wp_l.png

505 ms

wp_r.png

wp_r.png

507 ms

wp_t.gif

wp_t.gif

506 ms

8d7da69026dd97634cdb57e1a195a580.jpg

8d7da69026dd97634cdb57e1a195a580.jpg

1188 ms

06af6a53aeabe3a0fa2033073e66ac58.jpg

06af6a53aeabe3a0fa2033073e66ac58.jpg

1271 ms

dce8450bbafcf9eb4dcc0301da8903d3.jpg

dce8450bbafcf9eb4dcc0301da8903d3.jpg

982 ms

1fce22d19e371493b6453b5c61fb8d7e.jpg

1fce22d19e371493b6453b5c61fb8d7e.jpg

1012 ms

b43514dbf73e89ad7a79003045e17429.jpg

b43514dbf73e89ad7a79003045e17429.jpg

1185 ms

collapsed_no.gif

collapsed_no.gif

1352 ms

forum.gif

forum.gif

1354 ms

forum_new.gif

forum_new.gif

1357 ms

security.png

security.png

1356 ms

pt.gif

pt.gif

1423 ms

ptem.gif

ptem.gif

1469 ms

sg.gif

sg.gif

1515 ms

sg_l.gif

sg_l.gif

1517 ms

stat.php

stat.php

1357 ms

common_extra.js

common_extra.js

1376 ms

sg_r.gif

sg_r.gif

1370 ms

fl_bm_c.gif

fl_bm_c.gif

1427 ms

eis_topuser.gif

eis_topuser.gif

1477 ms

sortnum.png

sortnum.png

1527 ms

t1_m.gif

t1_m.gif

1381 ms

t1_l.gif

t1_l.gif

1376 ms

fl_bm.gif

fl_bm.gif

1368 ms

fl_bm_h.gif

fl_bm_h.gif

1414 ms

fl_bm_h_on.gif

fl_bm_h_on.gif

1470 ms

eis_footer.png

eis_footer.png

1525 ms

01_avatar_small.jpg

01_avatar_small.jpg

1191 ms

86_avatar_small.jpg

86_avatar_small.jpg

1022 ms

noavatar_small.gif

noavatar_small.gif

853 ms

46_avatar_small.jpg

46_avatar_small.jpg

763 ms

22_avatar_small.jpg

22_avatar_small.jpg

787 ms

15_avatar_small.jpg

15_avatar_small.jpg

845 ms

58_avatar_small.jpg

58_avatar_small.jpg

723 ms

stat.htm

stat.htm

163 ms

core.php

core.php

925 ms

t1_r.gif

t1_r.gif

453 ms

t1_li.gif

t1_li.gif

454 ms

9.gif

9.gif

1357 ms

scrolltop.png

scrolltop.png

172 ms

app.gif

app.gif

1116 ms

Accessibility Review

52rr.net accessibility score

53

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

52rr.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

52rr.net SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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 52rr.net 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 52rr.net 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

52rr.net

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