Tools & Wizards About Us
play.riftforge.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

play.riftforge.com

Apache HTTP Server Test Page powered by CentOS

Page Load Speed

3.3 sec in total

First Response

696 ms

Resources Loaded

2.4 sec

Page Rendered

147 ms

play.riftforge.com screenshot

About Website

Visit play.riftforge.com now to see the best up-to-date Play Riftforge content for Argentina and also check out these interesting facts you probably never knew about play.riftforge.com

Riftforge has a modern gameplay featuring 40 classes with over 70 unique skills.

Visit play.riftforge.com

Key Findings

We analyzed Play.riftforge.com page load time and found that the first response time was 696 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

play.riftforge.com performance score

0

Network Requests Diagram

play.riftforge.com

696 ms

system.base.css

94 ms

system.menus.css

186 ms

system.messages.css

185 ms

system.theme.css

187 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 87% of them (54 requests) were addressed to the original Play.riftforge.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (846 ms) belongs to the original domain Play.riftforge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 555.4 kB (53%)

Content Size

1.1 MB

After Optimization

499.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Play.riftforge.com main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 441.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.7 kB

  • Original 19.8 kB
  • After minification 18.7 kB
  • After compression 5.0 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 14.7 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 37.7 kB

  • Original 341.3 kB
  • After minification 303.7 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, Play Riftforge needs image optimization as it can save up to 37.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 293.3 kB

  • Original 441.4 kB
  • After minification 411.5 kB
  • After compression 148.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 293.3 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 209.6 kB

  • Original 252.0 kB
  • After minification 186.3 kB
  • After compression 42.3 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. Play.riftforge.com needs all CSS files to be minified and compressed as it can save up to 209.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (69%)

Requests Now

59

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

play.riftforge.com

play.riftforge.com

696 ms

system.base.css

system.base.css

94 ms

system.menus.css

system.menus.css

186 ms

system.messages.css

system.messages.css

185 ms

system.theme.css

system.theme.css

187 ms

comment.css

comment.css

189 ms

field.css

field.css

191 ms

node.css

node.css

189 ms

search.css

search.css

275 ms

user.css

user.css

276 ms

forum.css

forum.css

278 ms

views.css

views.css

279 ms

ctools.css

ctools.css

279 ms

ds_2col.css

ds_2col.css

365 ms

field_group.field_ui.css

field_group.field_ui.css

366 ms

at.layout.css

at.layout.css

371 ms

html-elements.css

html-elements.css

371 ms

forms.css

forms.css

373 ms

tables.css

tables.css

376 ms

fields.css

fields.css

454 ms

page.css

page.css

456 ms

navigation.css

navigation.css

462 ms

articles.css

articles.css

463 ms

comments.css

comments.css

464 ms

blocks.css

blocks.css

472 ms

riftforge.css

riftforge.css

726 ms

tabs.css

tabs.css

546 ms

tooltip.css

tooltip.css

552 ms

print.css

print.css

555 ms

jquery.min.js

jquery.min.js

749 ms

jquery.once.js

jquery.once.js

563 ms

drupal.js

drupal.js

636 ms

jquery.cookie.js

jquery.cookie.js

643 ms

jump-menu.js

jump-menu.js

648 ms

authcache.js

authcache.js

657 ms

conversion.js

conversion.js

20 ms

authcache_menu.js

authcache_menu.js

745 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

665 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

846 ms

jquery-ui-touch-punch.js

jquery-ui-touch-punch.js

588 ms

script.js

script.js

640 ms

jquery.tooltip.js

jquery.tooltip.js

640 ms

logo.png

logo.png

103 ms

home-btns.png

home-btns.png

103 ms

header_bottom.png

header_bottom.png

102 ms

content_top.png

content_top.png

456 ms

content_back.jpg

content_back.jpg

188 ms

riftforge_home.png

riftforge_home.png

103 ms

spacer.gif

spacer.gif

187 ms

riftforge_home_sm.png

riftforge_home_sm.png

189 ms

riftforge_home_sm_link.gif

riftforge_home_sm_link.gif

190 ms

invites_left.png

invites_left.png

192 ms

buttons.png

buttons.png

551 ms

77 ms

like.php

like.php

85 ms

content_bottom.png

content_bottom.png

346 ms

ratio.woff

ratio.woff

259 ms

ga.js

ga.js

48 ms

__utm.gif

__utm.gif

14 ms

459 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

491 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

558 ms

SEO Factors

play.riftforge.com 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 Play.riftforge.com 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 Play.riftforge.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

play.riftforge.com

Open Graph data is detected on the main page of Play Riftforge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: