Tools & Wizards About Us
rocards.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rocards.org

Main Page - RoCards-Forum

Page Load Speed

3.9 sec in total

First Response

960 ms

Resources Loaded

2.4 sec

Page Rendered

526 ms

rocards.org screenshot

About Website

Welcome to rocards.org homepage info - get ready to check Ro Cards best content right away, or after learning these important things about rocards.org

RoCards - dein deutsches Ragnarok Portal! Hier gibs Datenbanken und eine freundliche Communtiy zu RagnarökOnline!

Visit rocards.org

Key Findings

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

Performance Metrics

rocards.org performance score

0

Network Requests Diagram

rocards.org

960 ms

protoaculous.1.8.2.min.js

418 ms

default.js

174 ms

PopupMenuList.class.js

172 ms

AjaxRequest.class.js

186 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 75% of them (49 requests) were addressed to the original Rocards.org, 8% (5 requests) were made to Pagead2.googlesyndication.com and 6% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Rocards.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 387.8 kB (57%)

Content Size

680.5 kB

After Optimization

292.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rocards.org main page is 680.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 215.0 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 168.7 kB

  • Original 187.2 kB
  • After minification 143.4 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 43.7 kB, which is 23% 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 168.7 kB or 90% of the original size.

Image Optimization

-7%

Potential reduce by 13.2 kB

  • Original 190.4 kB
  • After minification 177.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. Ro Cards images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 133.2 kB

  • Original 215.0 kB
  • After minification 207.0 kB
  • After compression 81.8 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 133.2 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 72.8 kB

  • Original 88.0 kB
  • After minification 79.6 kB
  • After compression 15.2 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. Rocards.org needs all CSS files to be minified and compressed as it can save up to 72.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (60%)

Requests Now

62

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rocards.org

rocards.org

960 ms

protoaculous.1.8.2.min.js

protoaculous.1.8.2.min.js

418 ms

default.js

default.js

174 ms

PopupMenuList.class.js

PopupMenuList.class.js

172 ms

AjaxRequest.class.js

AjaxRequest.class.js

186 ms

burningBoard.css

burningBoard.css

182 ms

style-15.css

style-15.css

247 ms

BoardMarkAsRead.class.js

BoardMarkAsRead.class.js

369 ms

show_ads.js

show_ads.js

5 ms

body.png

body.png

517 ms

button-home.gif

button-home.gif

273 ms

button-member.gif

button-member.gif

274 ms

button-team.gif

button-team.gif

270 ms

button-world.gif

button-world.gif

271 ms

button-gallery.gif

button-gallery.gif

271 ms

avatar-default.png

avatar-default.png

443 ms

loginS.png

loginS.png

451 ms

registerS.png

registerS.png

405 ms

languageEnS.png

languageEnS.png

479 ms

languageDe-informalS.png

languageDe-informalS.png

426 ms

submitS.png

submitS.png

496 ms

indexL.gif

indexL.gif

649 ms

minusS.png

minusS.png

545 ms

boardNewM.gif

boardNewM.gif

653 ms

goToFirstNewPostS.png

goToFirstNewPostS.png

584 ms

boardM.gif

boardM.gif

716 ms

usersS.png

usersS.png

681 ms

boardS.png

boardS.png

647 ms

boardNewS.png

boardNewS.png

715 ms

boardRedirectS.png

boardRedirectS.png

775 ms

plusS.png

plusS.png

745 ms

membersM.png

membersM.png

772 ms

statisticsM.png

statisticsM.png

800 ms

tagM.png

tagM.png

828 ms

boardMarkAsReadS.png

boardMarkAsReadS.png

808 ms

helpS.png

helpS.png

835 ms

legalNoticeS.png

legalNoticeS.png

854 ms

termsOfUseS.png

termsOfUseS.png

855 ms

styleOptionsS.png

styleOptionsS.png

883 ms

dateS.png

dateS.png

888 ms

upS.png

upS.png

919 ms

searchHeadS.png

searchHeadS.png

915 ms

infoM.png

infoM.png

1046 ms

listInner.jpg

listInner.jpg

917 ms

searchHeadOptionsS.png

searchHeadOptionsS.png

948 ms

ga.js

ga.js

30 ms

__utm.gif

__utm.gif

39 ms

ca-pub-4117465709797601.js

ca-pub-4117465709797601.js

149 ms

zrt_lookup.html

zrt_lookup.html

50 ms

show_ads_impl.js

show_ads_impl.js

69 ms

headbg2.jpg

headbg2.jpg

784 ms

externalURL.png

externalURL.png

753 ms

button-n.jpg

button-n.jpg

758 ms

loginOptionsS.png

loginOptionsS.png

811 ms

ads

ads

216 ms

osd.js

osd.js

9 ms

m_js_controller.js

m_js_controller.js

26 ms

abg.js

abg.js

40 ms

favicon

favicon

64 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

60 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

37 ms

s

s

26 ms

x_button_blue2.png

x_button_blue2.png

15 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

4 ms

print.css

print.css

88 ms

SEO Factors

rocards.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rocards.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Rocards.org 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

rocards.org

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