Tools & Wizards About Us
laposte.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

laposte.co.jp

東京千代田区にある南フランス料理のお店 ビストロ・ラ・ポスト

Page Load Speed

4.5 sec in total

First Response

533 ms

Resources Loaded

3.8 sec

Page Rendered

214 ms

laposte.co.jp screenshot

About Website

Visit laposte.co.jp now to see the best up-to-date Laposte content and also check out these interesting facts you probably never knew about laposte.co.jp

千代田区永田町駅にほど近い緑が広がる平河町の一角にある隠れ家的なお店ビストロ・ラ・ポスト。本格的な南フランス料理が気兼ねなく楽しめます。好評のチョコレートケーキは当サイトで購入していただけます。

Visit laposte.co.jp

Key Findings

We analyzed Laposte.co.jp page load time and found that the first response time was 533 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

laposte.co.jp performance score

0

Network Requests Diagram

laposte.co.jp

533 ms

main.css

165 ms

navigation.css

320 ms

images.js

359 ms

urchin.js

8 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 93% of them (25 requests) were addressed to the original Laposte.co.jp, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Laposte.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.1 kB (2%)

Content Size

736.4 kB

After Optimization

725.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Laposte.co.jp main page is 736.4 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. 15% of websites need less resources to load. Images take 716.0 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 3.2 kB

  • Original 5.4 kB
  • After minification 5.2 kB
  • After compression 2.2 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 3.2 kB or 59% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 716.0 kB
  • After minification 716.0 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. Laposte images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 971 B

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.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 971 B or 14% of the original size.

CSS Optimization

-85%

Potential reduce by 7.0 kB

  • Original 8.2 kB
  • After minification 5.5 kB
  • After compression 1.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. Laposte.co.jp needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

24

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

laposte.co.jp

laposte.co.jp

533 ms

main.css

main.css

165 ms

navigation.css

navigation.css

320 ms

images.js

images.js

359 ms

urchin.js

urchin.js

8 ms

qrcord.jpg

qrcord.jpg

2166 ms

body_bg.jpg

body_bg.jpg

155 ms

bg.jpg

bg.jpg

218 ms

bg_up.jpg

bg_up.jpg

1003 ms

header_bg.jpg

header_bg.jpg

614 ms

b1.jpg

b1.jpg

309 ms

b2.jpg

b2.jpg

693 ms

b3.jpg

b3.jpg

1126 ms

b4.jpg

b4.jpg

574 ms

b5.jpg

b5.jpg

462 ms

main_visual.jpg

main_visual.jpg

1536 ms

line.gif

line.gif

753 ms

top_info.jpg

top_info.jpg

768 ms

top_line.gif

top_line.gif

867 ms

top_recommend.jpg

top_recommend.jpg

1117 ms

footer_bg.jpg

footer_bg.jpg

929 ms

b6.gif

b6.gif

1038 ms

b7.gif

b7.gif

1082 ms

copy.jpg

copy.jpg

1186 ms

top_recommend_img00.jpg

top_recommend_img00.jpg

2422 ms

top_recommend_img01.jpg

top_recommend_img01.jpg

2902 ms

__utm.gif

__utm.gif

4 ms

SEO Factors

laposte.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Laposte.co.jp 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 Laposte.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

laposte.co.jp

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