Tools & Wizards About Us
sucre-en-rose.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sucre-en-rose.com

HTML SiteMap

Page Load Speed

4.1 sec in total

First Response

877 ms

Resources Loaded

3.1 sec

Page Rendered

173 ms

sucre-en-rose.com screenshot

About Website

Welcome to sucre-en-rose.com homepage info - get ready to check Sucre En Rose best content for Japan right away, or after learning these important things about sucre-en-rose.com

つくば市のフレンチレストラン、Sucre-en-Rose（シュクル・アン・ローズ）です。ミシュランのスターシェフたちと培った、こだわりのフランス料理をご賞味ください。お手軽な値段のランチメニューもあります。

Visit sucre-en-rose.com

Key Findings

We analyzed Sucre-en-rose.com page load time and found that the first response time was 877 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

sucre-en-rose.com performance score

0

Network Requests Diagram

sucre-en-rose.com

877 ms

import.css

322 ms

jquery.js

336 ms

jquery.page-scroller.js

337 ms

external.js

338 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 92% of them (35 requests) were addressed to the original Sucre-en-rose.com, 5% (2 requests) were made to Twitbuttons.com and 3% (1 request) were made to Badge.facebook.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Sucre-en-rose.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.2 kB (71%)

Content Size

26.9 kB

After Optimization

7.8 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Sucre-en-rose.com main page is 26.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. Only 10% of websites need less resources to load. HTML takes 13.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 9.4 kB

  • Original 13.0 kB
  • After minification 12.0 kB
  • After compression 3.6 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 9.4 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.4 kB
  • After minification 1.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. Sucre En Rose images are well optimized though.

CSS Optimization

-78%

Potential reduce by 9.8 kB

  • Original 12.6 kB
  • After minification 7.8 kB
  • After compression 2.8 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. Sucre-en-rose.com needs all CSS files to be minified and compressed as it can save up to 9.8 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

28

After Optimization

22

  • Images
  • CSS

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

Network Requests Diagram

sucre-en-rose.com

sucre-en-rose.com

877 ms

import.css

import.css

322 ms

jquery.js

jquery.js

336 ms

jquery.page-scroller.js

jquery.page-scroller.js

337 ms

external.js

external.js

338 ms

rollover.js

rollover.js

339 ms

home.css

home.css

471 ms

all.css

all.css

322 ms

layout.css

layout.css

351 ms

header.css

header.css

184 ms

side.css

side.css

183 ms

footer.css

footer.css

185 ms

119131014888045.959.479234977.png

119131014888045.959.479234977.png

46 ms

tw6.gif

tw6.gif

134 ms

bg_header01.jpg

bg_header01.jpg

162 ms

h2_logo01.gif

h2_logo01.gif

172 ms

img_tel02.gif

img_tel02.gif

164 ms

navi_global01.gif

navi_global01.gif

336 ms

bg_promotion01.jpg

bg_promotion01.jpg

375 ms

bg_promotion02.jpg

bg_promotion02.jpg

1332 ms

img_promotion01.jpg

img_promotion01.jpg

1432 ms

bn_cuisine01.jpg

bn_cuisine01.jpg

1115 ms

bn_sweets01.jpg

bn_sweets01.jpg

1171 ms

h4_index01.gif

h4_index01.gif

503 ms

bdr_vertical01.gif

bdr_vertical01.gif

543 ms

bdr_horizontal01.gif

bdr_horizontal01.gif

670 ms

bn_staff01.jpg

bn_staff01.jpg

1045 ms

bn_access01.jpg

bn_access01.jpg

1539 ms

bn_blog01.jpg

bn_blog01.jpg

1379 ms

bn_blog02.jpg

bn_blog02.jpg

1431 ms

img_index15.jpg

img_index15.jpg

1339 ms

img_index16.jpg

img_index16.jpg

1499 ms

img_index01.jpg

img_index01.jpg

1843 ms

img_pagetop01.jpg

img_pagetop01.jpg

1547 ms

bg_footer01.jpg

bg_footer01.jpg

1747 ms

bg_footer_top01.jpg

bg_footer_top01.jpg

1750 ms

txt_copyright01.gif

txt_copyright01.gif

1665 ms

tw6.gif

tw6.gif

237 ms

SEO Factors

sucre-en-rose.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

sucre-en-rose.com

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