Tools & Wizards About Us
bento.finedine.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

bento.finedine.jp

レストラン・デリバリーのファインダイン｜fineDine【ファインダイン】

Page Load Speed

4.2 sec in total

First Response

770 ms

Resources Loaded

3.1 sec

Page Rendered

280 ms

bento.finedine.jp screenshot

About Website

Visit bento.finedine.jp now to see the best up-to-date Bento FineDine content for Japan and also check out these interesting facts you probably never knew about bento.finedine.jp

ファインダイン弁当は、人気レストランのお弁当をご自宅やオフィスにお届けするサービス。会議弁当、ランチョンセミナー、ご自宅での集まりにご利 用ください。

Visit bento.finedine.jp

Key Findings

We analyzed Bento.finedine.jp page load time and found that the first response time was 770 ms and then it took 3.4 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

bento.finedine.jp performance score

0

Network Requests Diagram

bento.finedine.jp

770 ms

style.css

289 ms

jquery.js

732 ms

smart-crossfade.js

297 ms

finedine.js

299 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 97% of them (70 requests) were addressed to the original Bento.finedine.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Bento.finedine.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 539.3 kB (46%)

Content Size

1.2 MB

After Optimization

633.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bento.finedine.jp main page is 1.2 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. 40% of websites need less resources to load. Images take 564.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.6 kB

  • Original 18.3 kB
  • After minification 16.0 kB
  • After compression 4.8 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 2.3 kB, which is 13% 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 13.6 kB or 74% of the original size.

Image Optimization

-12%

Potential reduce by 65.9 kB

  • Original 564.3 kB
  • After minification 498.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. Obviously, Bento FineDine needs image optimization as it can save up to 65.9 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 388.7 kB

  • Original 504.7 kB
  • After minification 424.6 kB
  • After compression 116.0 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 388.7 kB or 77% of the original size.

CSS Optimization

-83%

Potential reduce by 71.2 kB

  • Original 85.7 kB
  • After minification 66.3 kB
  • After compression 14.5 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. Bento.finedine.jp needs all CSS files to be minified and compressed as it can save up to 71.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (31%)

Requests Now

71

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bento.finedine.jp

bento.finedine.jp

770 ms

style.css

style.css

289 ms

jquery.js

jquery.js

732 ms

smart-crossfade.js

smart-crossfade.js

297 ms

finedine.js

finedine.js

299 ms

jquery.tipsy.js

jquery.tipsy.js

300 ms

jquery-ui-1.8.6.custom.css

jquery-ui-1.8.6.custom.css

453 ms

application.css

application.css

433 ms

jquery.ui.datepicker-ja.js

jquery.ui.datepicker-ja.js

303 ms

jquery-ui-1.8.6.custom.min.js

jquery-ui-1.8.6.custom.min.js

1178 ms

jquery.jsonp-2.1.3.min.js

jquery.jsonp-2.1.3.min.js

308 ms

application.js

application.js

1024 ms

reset.css

reset.css

303 ms

lib.css

lib.css

309 ms

common.css

common.css

317 ms

text.css

text.css

448 ms

templates.css

templates.css

457 ms

general.css

general.css

467 ms

bg_all.gif

bg_all.gif

148 ms

logo.gif

logo.gif

150 ms

fig_tel.gif

fig_tel.gif

153 ms

pic_mainvisual_01.jpg

pic_mainvisual_01.jpg

879 ms

ttl_search.gif

ttl_search.gif

293 ms

box_mid_search.gif

box_mid_search.gif

297 ms

box_head_search.gif

box_head_search.gif

302 ms

bg_date_bottom.gif

bg_date_bottom.gif

439 ms

bg_date_top.gif

bg_date_top.gif

445 ms

bg_date.gif

bg_date.gif

451 ms

fig_serch.png

fig_serch.png

529 ms

btn_today_off.jpg

btn_today_off.jpg

601 ms

btn_date.png

btn_date.png

600 ms

btn_day_time.png

btn_day_time.png

602 ms

btn_form.png

btn_form.png

675 ms

btn_price.png

btn_price.png

679 ms

fig_keyword.gif

fig_keyword.gif

729 ms

btn_search.gif

btn_search.gif

738 ms

ttl_reccommend.gif

ttl_reccommend.gif

751 ms

logo_suzuki.jpg

logo_suzuki.jpg

820 ms

pic_bento_suzuki.jpg

pic_bento_suzuki.jpg

824 ms

btn_rst_detail.jpg

btn_rst_detail.jpg

875 ms

logo_butagumi.jpg

logo_butagumi.jpg

1033 ms

pic_bento_butagumi.jpg

pic_bento_butagumi.jpg

1088 ms

logo_miyashita.jpg

logo_miyashita.jpg

966 ms

pic_bento_miyashita.jpg

pic_bento_miyashita.jpg

969 ms

logo_akiji.jpg

logo_akiji.jpg

1017 ms

pic_bento_akiji.jpg

pic_bento_akiji.jpg

1164 ms

box_head_wlcm.jpg

box_head_wlcm.jpg

1112 ms

box_mid_wlcm.gif

box_mid_wlcm.gif

1115 ms

box_head_wlcm_mid.jpg

box_head_wlcm_mid.jpg

1163 ms

btn_register_s.jpg

btn_register_s.jpg

1179 ms

btn_login.jpg

btn_login.jpg

1238 ms

ttl_cart_right.gif

ttl_cart_right.gif

1214 ms

btn_red.jpg

btn_red.jpg

1126 ms

box_foot_wlcm.gif

box_foot_wlcm.gif

1166 ms

icn_arw_whi_02.png

icn_arw_whi_02.png

1164 ms

btn_org.jpg

btn_org.jpg

1041 ms

icn_arw_brwn.png

icn_arw_brwn.png

1099 ms

ttl_news_right.gif

ttl_news_right.gif

1110 ms

icn_arw_brwn_02.png

icn_arw_brwn_02.png

1037 ms

bnr_deliver.jpg

bnr_deliver.jpg

1024 ms

bnr_credit.jpg

bnr_credit.jpg

1019 ms

logo_rex.gif

logo_rex.gif

1030 ms

logo_ginsara.gif

logo_ginsara.gif

1017 ms

analytics.js

analytics.js

27 ms

logo_kamatora.gif

logo_kamatora.gif

974 ms

collect

collect

18 ms

logo_currycurry.gif

logo_currycurry.gif

963 ms

logo_age.gif

logo_age.gif

1007 ms

logo_ginben.gif

logo_ginben.gif

1006 ms

logo_littleartist.gif

logo_littleartist.gif

954 ms

preloader.gif

preloader.gif

1016 ms

ui-bg_fine-grain_10_eceadf_60x60.png

ui-bg_fine-grain_10_eceadf_60x60.png

973 ms

SEO Factors

bento.finedine.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bento.finedine.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 Bento.finedine.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.

Social Sharing Optimization

bento.finedine.jp

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