4.8 sec in total
650 ms
3.8 sec
300 ms
Click here to check amazing La Rochelle content for Japan. Otherwise, check out these important facts you probably never knew about la-rochelle.co.jp
料理の鉄人でおなじみのムッシュ坂井宏行がオーナーをを務めるフレンチレストラン ラ・ロシェル。新鮮な素材をふんだんに使用した斬新なお料理は、驚きと楽しみを生みます。格調あるインテリアと最高のおもてなしは、洗練された雰囲気を創り出します。南青山、山王、福岡の店舗でお待ちしております。
Visit la-rochelle.co.jpWe analyzed La-rochelle.co.jp page load time and found that the first response time was 650 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
la-rochelle.co.jp performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value59.0 s
0/100
25%
Value11.0 s
6/100
10%
Value3,550 ms
1/100
30%
Value0.516
15/100
15%
Value54.7 s
0/100
10%
650 ms
181 ms
476 ms
315 ms
315 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 94% of them (66 requests) were addressed to the original La-rochelle.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Static.dudamobile.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain La-rochelle.co.jp.
Page size can be reduced by 135.0 kB (8%)
1.7 MB
1.6 MB
In fact, the total size of La-rochelle.co.jp main page is 1.7 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. 25% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 9.3 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.3 kB or 70% of the original size.
Potential reduce by 6.2 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. La Rochelle images are well optimized though.
Potential reduce by 112.4 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.
Potential reduce by 7.1 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. La-rochelle.co.jp needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 75% of the original size.
Number of requests can be reduced by 37 (54%)
69
32
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of La Rochelle. 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 5 to 1 for CSS and as a result speed up the page load time.
la-rochelle.co.jp
650 ms
import_top.css
181 ms
jquery.js
476 ms
opacity-rollover2.1.js
315 ms
common_event.js
315 ms
jquery.bgSwitcher-min.js
330 ms
jquery.color.js
344 ms
header_event.js
358 ms
DM_redirect.js
11 ms
reset.css
294 ms
font.css
293 ms
base_layout.css
317 ms
top.css
335 ms
analytics.js
40 ms
logo.png
359 ms
h_aoyama.gif
159 ms
h_fukuoka.gif
166 ms
h_sanno.gif
171 ms
h_eng.gif
158 ms
h_btn_contact.gif
157 ms
gnav_news_off.gif
313 ms
gnav_about_off.gif
314 ms
gnav_shop_off.gif
315 ms
gnav_chef_off.gif
331 ms
gnav_bridal_off.gif
342 ms
topimg_bg.gif
468 ms
main0.jpg
1241 ms
event_bg.png
470 ms
t_event_aoyama.png
498 ms
aoyama_event012.jpg
521 ms
t_event_fukuoka.png
540 ms
fukuoka_event19.jpg
638 ms
t_event_sanno.png
628 ms
sanno_event23.jpg
825 ms
iledere_bnr.jpg
1365 ms
card_bnr.jpg
903 ms
bnr_stamp.jpg
1095 ms
border_dotted.gif
792 ms
t_news.gif
949 ms
icon_aoyama.gif
991 ms
icon_fukuoka.gif
1085 ms
icon_sanno.gif
1104 ms
bnr_bridal.jpg
1652 ms
bnr_aoyama.jpg
1620 ms
bnr_fukuoka.jpg
1412 ms
bnr_sanno.jpg
1423 ms
bnr_about.jpg
1430 ms
bnr_chef.jpg
1556 ms
bnr_recruit.jpg
1724 ms
arrow_black01.gif
1551 ms
collect
4 ms
collect
61 ms
f_aoyama.jpg
1460 ms
f_fukuoka.jpg
1606 ms
f_sanno.jpg
1602 ms
footer_logo.gif
1612 ms
arrow_white01.gif
1636 ms
arrow_white02.gif
1509 ms
copyright.gif
1576 ms
f_btn_contact.gif
1606 ms
f_btn_blog.jpg
1607 ms
btn_pagetop.png
1593 ms
gnav_news_on.gif
1628 ms
gnav_about_on.gif
1519 ms
gnav_shop_on.gif
1575 ms
gnav_chef_on.gif
1576 ms
gnav_bridal_on.gif
1571 ms
main1.jpg
1936 ms
main2.jpg
1899 ms
main3.jpg
2000 ms
la-rochelle.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
la-rochelle.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
la-rochelle.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise La-rochelle.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that La-rochelle.co.jp 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.
la-rochelle.co.jp
Open Graph description is not detected on the main page of La Rochelle. 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: