Tools & Wizards About Us
ginzaroots.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ginzaroots.com

GINZA ROOTS TOKYO | ギンザルーツトウキョウ | パリの社交場をイメージした空間で、最高の撮影環境をお届けします

Page Load Speed

11.6 sec in total

First Response

1.3 sec

Resources Loaded

9.7 sec

Page Rendered

502 ms

ginzaroots.com screenshot

About Website

Welcome to ginzaroots.com homepage info - get ready to check GINZA ROOTS best content right away, or after learning these important things about ginzaroots.com

年間実績多数 ウェディング2次会・貸切・大型パーティー サポート充実・設備完備 GINZA ROOTS TOKYO

Visit ginzaroots.com

Key Findings

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

Performance Metrics

ginzaroots.com performance score

0

Network Requests Diagram

ginzaroots.com

1303 ms

style.css

321 ms

common.css

641 ms

style.css

679 ms

jquery-1.10.2.min.js

1031 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 67% of them (78 requests) were addressed to the original Ginzaroots.com, 20% (23 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Ginzaroots.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.7 kB (7%)

Content Size

5.6 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ginzaroots.com main page is 5.6 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. 55% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.8 kB

  • Original 31.0 kB
  • After minification 29.3 kB
  • After compression 7.1 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 23.8 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 197.4 kB

  • Original 5.4 MB
  • After minification 5.2 MB

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. GINZA ROOTS images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 112.4 kB

  • Original 172.3 kB
  • After minification 167.1 kB
  • After compression 59.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 112.4 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 36.0 kB

  • Original 43.7 kB
  • After minification 34.3 kB
  • After compression 7.6 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. Ginzaroots.com needs all CSS files to be minified and compressed as it can save up to 36.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (33%)

Requests Now

115

After Optimization

77

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ginzaroots.com

ginzaroots.com

1303 ms

style.css

style.css

321 ms

common.css

common.css

641 ms

style.css

style.css

679 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1031 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

513 ms

jquery.module.js

jquery.module.js

479 ms

lightbox-2.6.min.js

lightbox-2.6.min.js

483 ms

lightbox.css

lightbox.css

637 ms

jquery.film_roll.min.js

jquery.film_roll.min.js

647 ms

bg.png

bg.png

813 ms

f_bg.png

f_bg.png

340 ms

close.png

close.png

161 ms

loading.gif

loading.gif

174 ms

prev.png

prev.png

172 ms

next.png

next.png

163 ms

h_logo.png

h_logo.png

319 ms

h_tel.png

h_tel.png

320 ms

h_btn.png

h_btn.png

349 ms

h_view.png

h_view.png

347 ms

gnav01_on.png

gnav01_on.png

471 ms

gnav02_off.png

gnav02_off.png

480 ms

gnav03_off.png

gnav03_off.png

500 ms

gnav04_off.png

gnav04_off.png

517 ms

gnav05_off.png

gnav05_off.png

516 ms

gnav06_off.png

gnav06_off.png

582 ms

gnav07_off.png

gnav07_off.png

628 ms

mv01.png

mv01.png

2079 ms

mv02.png

mv02.png

2198 ms

mv03.png

mv03.png

4282 ms

mv04.png

mv04.png

2060 ms

mv_arw_l.png

mv_arw_l.png

741 ms

mv_arw_r.png

mv_arw_r.png

784 ms

top_news_ttl.png

top_news_ttl.png

904 ms

top_service_ttl01.png

top_service_ttl01.png

943 ms

top_service_img01.jpg

top_service_img01.jpg

1067 ms

top_service_btn.png

top_service_btn.png

1102 ms

top_service_ttl02.png

top_service_ttl02.png

1229 ms

top_service_img02.jpg

top_service_img02.jpg

1262 ms

top_service_ttl03.png

top_service_ttl03.png

1392 ms

top_service_img03.jpg

top_service_img03.jpg

1421 ms

top_service_ttl04.png

top_service_ttl04.png

1555 ms

top_service_img04.jpg

top_service_img04.jpg

1580 ms

top_feelings_ttl.png

top_feelings_ttl.png

1717 ms

top_feelings_img01s.jpg

top_feelings_img01s.jpg

1740 ms

all.js

all.js

269 ms

top_feelings_img02s.jpg

top_feelings_img02s.jpg

1867 ms

analytics.js

analytics.js

27 ms

collect

collect

13 ms

top_feelings_img03s.jpg

top_feelings_img03s.jpg

1761 ms

top_feelings_img04s.jpg

top_feelings_img04s.jpg

1898 ms

top_feelings_img05s.jpg

top_feelings_img05s.jpg

1908 ms

top_feelings_img06s.jpg

top_feelings_img06s.jpg

2051 ms

106 ms

xd_arbiter.php

xd_arbiter.php

213 ms

xd_arbiter.php

xd_arbiter.php

418 ms

top_feelings_img07s.jpg

top_feelings_img07s.jpg

1925 ms

lnav_ttl.png

lnav_ttl.png

1913 ms

lnav_stl01.png

lnav_stl01.png

1917 ms

lnav_img01.jpg

lnav_img01.jpg

2028 ms

lnav_stl02.png

lnav_stl02.png

2036 ms

lnav_img02.jpg

lnav_img02.jpg

1971 ms

lnav_stl03.png

lnav_stl03.png

1942 ms

lnav_img03.jpg

lnav_img03.jpg

1928 ms

lnav_btn.png

lnav_btn.png

2043 ms

lnav_bnr01.png

lnav_bnr01.png

2027 ms

lnav_bnr02.png

lnav_bnr02.png

2025 ms

lnav_fb.png

lnav_fb.png

1982 ms

lnav_tw.png

lnav_tw.png

1954 ms

lnav_ln.png

lnav_ln.png

1967 ms

f_logo.png

f_logo.png

1918 ms

f_btn.png

f_btn.png

1800 ms

h_bg.png

h_bg.png

1778 ms

h_bg02.png

h_bg02.png

1683 ms

top_news_bg.png

top_news_bg.png

1762 ms

top_service_line.png

top_service_line.png

1635 ms

top_feelings_bg.png

top_feelings_bg.png

1616 ms

top_feelings_btn.png

top_feelings_btn.png

1487 ms

f_line.png

f_line.png

1500 ms

mv_btn01_off.png

mv_btn01_off.png

1473 ms

mv_btn02_off.png

mv_btn02_off.png

1466 ms

mv_btn03_off.png

mv_btn03_off.png

1322 ms

mv_btn04_off.png

mv_btn04_off.png

1352 ms

ping

ping

31 ms

mv_btn01_on.png

mv_btn01_on.png

164 ms

like_box.php

like_box.php

1014 ms

kczA5SVYRy-.css

kczA5SVYRy-.css

285 ms

5gv7lSltRdg.css

5gv7lSltRdg.css

356 ms

9FbwY9OGefM.css

9FbwY9OGefM.css

425 ms

YlgL_kgYceV.css

YlgL_kgYceV.css

556 ms

XCdv7aD40Gm.js

XCdv7aD40Gm.js

621 ms

5frqWlpFEeI.js

5frqWlpFEeI.js

640 ms

mn6tHWuLI-Y.js

mn6tHWuLI-Y.js

489 ms

x8BMxYCqTb9.js

x8BMxYCqTb9.js

490 ms

QKy94bWvcbp.js

QKy94bWvcbp.js

491 ms

5paioeCYCa7.js

5paioeCYCa7.js

569 ms

wRXOQ26LQ1k.js

wRXOQ26LQ1k.js

658 ms

UMeIUxuSxxa.js

UMeIUxuSxxa.js

765 ms

50Trs1RKgUY.js

50Trs1RKgUY.js

665 ms

10689750_984614234886945_3702874056926576585_n.jpg

10689750_984614234886945_3702874056926576585_n.jpg

491 ms

1557440_1204179019597131_7430571611707609894_n.jpg

1557440_1204179019597131_7430571611707609894_n.jpg

592 ms

12642626_1231653300183036_2840651252935363569_n.jpg

12642626_1231653300183036_2840651252935363569_n.jpg

750 ms

12669544_1231071126907920_4664582692211154409_n.jpg

12669544_1231071126907920_4664582692211154409_n.jpg

1448 ms

12644815_1230451453636554_7348434841005837035_n.jpg

12644815_1230451453636554_7348434841005837035_n.jpg

932 ms

12573740_1229766477038385_7264227011425443017_n.jpg

12573740_1229766477038385_7264227011425443017_n.jpg

845 ms

12651231_1229167040431662_9186838507715263526_n.jpg

12651231_1229167040431662_9186838507715263526_n.jpg

824 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

85 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

83 ms

mbF8ssTVP_5.png

mbF8ssTVP_5.png

82 ms

Fe6g47SXw-8.png

Fe6g47SXw-8.png

83 ms

L5AOQ9vzKfo.png

L5AOQ9vzKfo.png

86 ms

oULnqcel5Nm.png

oULnqcel5Nm.png

84 ms

q2ibvFgTxmh.png

q2ibvFgTxmh.png

135 ms

A2JLtDOGyCJ.png

A2JLtDOGyCJ.png

139 ms

Fy3hs8lKW0M.png

Fy3hs8lKW0M.png

137 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

70 ms

SEO Factors

ginzaroots.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 Ginzaroots.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 Ginzaroots.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

ginzaroots.com

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