Tools & Wizards About Us
royalroc.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

royalroc.com

株式会社エムアップホールディングス

Page Load Speed

4.9 sec in total

First Response

498 ms

Resources Loaded

4.1 sec

Page Rendered

264 ms

royalroc.com screenshot

About Website

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

m-up,M-UP,エムアップ

Visit royalroc.com

Key Findings

We analyzed Royalroc.com page load time and found that the first response time was 498 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

royalroc.com performance score

0

Network Requests Diagram

royalroc.com

498 ms

import.css

344 ms

AC_RunActiveContent.js

353 ms

jsapi

40 ms

common.js

366 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 55% of them (43 requests) were addressed to the original Royalroc.com, 36% (28 requests) were made to Img.royalroc.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Royalroc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.5 kB (6%)

Content Size

518.9 kB

After Optimization

485.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 18.0 kB

  • Original 23.3 kB
  • After minification 18.5 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 21% 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 18.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 123 B

  • Original 448.5 kB
  • After minification 448.4 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. Royalroc images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 7.8 kB

  • Original 37.1 kB
  • After minification 34.2 kB
  • After compression 29.3 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 7.8 kB or 21% of the original size.

CSS Optimization

-76%

Potential reduce by 7.5 kB

  • Original 9.9 kB
  • After minification 7.5 kB
  • After compression 2.4 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. Royalroc.com needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (21%)

Requests Now

77

After Optimization

61

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalroc.com

royalroc.com

498 ms

import.css

import.css

344 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

353 ms

jsapi

jsapi

40 ms

common.js

common.js

366 ms

index.js

index.js

339 ms

default.css

default.css

346 ms

reset.css

reset.css

357 ms

layout.css

layout.css

354 ms

jquery.min.js

jquery.min.js

44 ms

ga.js

ga.js

146 ms

royalroc_logo.jpg

royalroc_logo.jpg

186 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

399 ms

bt_newitem.gif

bt_newitem.gif

175 ms

roenproducebyhiromutakahara.gif

roenproducebyhiromutakahara.gif

328 ms

roen.gif

roen.gif

350 ms

hiromutakahara.gif

hiromutakahara.gif

369 ms

akm.gif

akm.gif

369 ms

attackthemind7.gif

attackthemind7.gif

461 ms

moonagedevilment.gif

moonagedevilment.gif

490 ms

francistmorks.gif

francistmorks.gif

693 ms

juryblack.gif

juryblack.gif

684 ms

dresscamp.gif

dresscamp.gif

681 ms

harakiri.gif

harakiri.gif

709 ms

gigor.gif

gigor.gif

815 ms

decade.gif

decade.gif

827 ms

gravevault.gif

gravevault.gif

1013 ms

brownbunny.gif

brownbunny.gif

1048 ms

overthetwelve.gif

overthetwelve.gif

1050 ms

3rdware.gif

3rdware.gif

1042 ms

3rdwarel.gif

3rdwarel.gif

1131 ms

troiso.gif

troiso.gif

1159 ms

resterods.gif

resterods.gif

1336 ms

sale.gif

sale.gif

1355 ms

guitaer.gif

guitaer.gif

1373 ms

rocblog.gif

rocblog.gif

1383 ms

recruit.jpg

recruit.jpg

1476 ms

bu_login.gif

bu_login.gif

1515 ms

spacer.gif

spacer.gif

1662 ms

bu_membersin.gif

bu_membersin.gif

1718 ms

bu_memberstokuten.gif

bu_memberstokuten.gif

1716 ms

070205_pt.gif

070205_pt.gif

1748 ms

roen2015AUWI.jpg

roen2015AUWI.jpg

2675 ms

decade2015.jpg

decade2015.jpg

2799 ms

DECADE1.jpg

DECADE1.jpg

2348 ms

DECADE2.jpg

DECADE2.jpg

2390 ms

hiromutakahara2.jpg

hiromutakahara2.jpg

2401 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

346 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

348 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

355 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

368 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

369 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

679 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

681 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

697 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

704 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

699 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

714 ms

w100_h120.500_1.jpg

w100_h120.500_1.jpg

1024 ms

w100_h120.1.jpg

w100_h120.1.jpg

1025 ms

w100_h120.1.jpg

w100_h120.1.jpg

1049 ms

w100_h120.1.jpg

w100_h120.1.jpg

1031 ms

w100_h120.1.jpg

w100_h120.1.jpg

1046 ms

w100_h120.1.jpg

w100_h120.1.jpg

1058 ms

w100_h120.1.jpg

w100_h120.1.jpg

1356 ms

w100_h120.1.jpg

w100_h120.1.jpg

1386 ms

w100_h120.1.jpg

w100_h120.1.jpg

1380 ms

w100_h120.1.jpg

w100_h120.1.jpg

1372 ms

w100_h120.1.jpg

w100_h120.1.jpg

1390 ms

w100_h120.1.jpg

w100_h120.1.jpg

1420 ms

w100_h120.1.jpg

w100_h120.1.jpg

1697 ms

w100_h120.9.jpg

w100_h120.9.jpg

1695 ms

w100_h120.19.jpg

w100_h120.19.jpg

1737 ms

w100_h120.1.jpg

w100_h120.1.jpg

1754 ms

uh.js

uh.js

521 ms

ScriptServlet

ScriptServlet

50 ms

__utm.gif

__utm.gif

13 ms

bt_newitem_on.gif

bt_newitem_on.gif

1993 ms

SEO Factors

royalroc.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

royalroc.com

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