Tools & Wizards About Us
nextfood.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nextfood.jp

ケータリングの食楽宝庫

Page Load Speed

3.6 sec in total

First Response

619 ms

Resources Loaded

2.9 sec

Page Rendered

130 ms

nextfood.jp screenshot

About Website

Click here to check amazing Nextfood content. Otherwise, check out these important facts you probably never knew about nextfood.jp

懇親会、決起集会、打ち上げ、歓送迎会、忘新年会、様々なシーンで会議室、イベントスペースを使用して、お客様のご要望に合わせて鮮やかに演出致します。イベントスタッフ、会食用のお弁当のご提供。ブッフェのセッティング、ドリンクサービス、ホットミールサービス、撤収や回収までを行います。キッチン設備がない場所へのお届けもOK！！

Visit nextfood.jp

Key Findings

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

nextfood.jp performance score

0

Network Requests Diagram

nextfood.jp

619 ms

screen.css

415 ms

two-column-left.css

449 ms

swfobject.js

348 ms

urchin.js

6 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 89% of them (34 requests) were addressed to the original Nextfood.jp, 11% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Nextfood.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.5 kB (12%)

Content Size

263.5 kB

After Optimization

233.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 5.5 kB

  • Original 8.0 kB
  • After minification 7.1 kB
  • After compression 2.5 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 896 B, which is 11% 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 5.5 kB or 69% of the original size.

Image Optimization

-3%

Potential reduce by 7.3 kB

  • Original 210.0 kB
  • After minification 202.7 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. Nextfood images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 5.7 kB

  • Original 30.7 kB
  • After minification 30.2 kB
  • After compression 25.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 5.7 kB or 19% of the original size.

CSS Optimization

-81%

Potential reduce by 11.9 kB

  • Original 14.8 kB
  • After minification 11.7 kB
  • After compression 2.9 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. Nextfood.jp needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (41%)

Requests Now

37

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nextfood. 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

nextfood.jp

nextfood.jp

619 ms

screen.css

screen.css

415 ms

two-column-left.css

two-column-left.css

449 ms

swfobject.js

swfobject.js

348 ms

urchin.js

urchin.js

6 ms

common.css

common.css

167 ms

fonts.css

fonts.css

215 ms

layout-default.css

layout-default.css

331 ms

theme.css

theme.css

543 ms

nav.css

nav.css

331 ms

bg.gif

bg.gif

167 ms

banner.gif

banner.gif

368 ms

contents-bg.gif

contents-bg.gif

183 ms

contents-top.gif

contents-top.gif

190 ms

header-menu1-on.gif

header-menu1-on.gif

184 ms

header-menu1.gif

header-menu1.gif

332 ms

header-menu2-on.gif

header-menu2-on.gif

341 ms

header-menu2.gif

header-menu2.gif

365 ms

header-menu3-on.gif

header-menu3-on.gif

364 ms

header-menu3.gif

header-menu3.gif

376 ms

inquiry.gif

inquiry.gif

496 ms

baner.jpg

baner.jpg

1019 ms

aoyama_banr.jpg

aoyama_banr.jpg

723 ms

nextbanar.jpg

nextbanar.jpg

725 ms

tsychapel_newbanner.jpg

tsychapel_newbanner.jpg

546 ms

rental.jpg

rental.jpg

749 ms

main-banner1.jpg

main-banner1.jpg

815 ms

lead-icon.gif

lead-icon.gif

720 ms

main-banner2.jpg

main-banner2.jpg

1074 ms

main-banner3.jpg

main-banner3.jpg

1077 ms

pagebody-inner.gif

pagebody-inner.gif

901 ms

entry-bg.gif

entry-bg.gif

928 ms

new-icon-on.gif

new-icon-on.gif

980 ms

new-icon.gif

new-icon.gif

1083 ms

footer-bg.gif

footer-bg.gif

1115 ms

__utm.gif

__utm.gif

2 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

13 ms

SEO Factors

nextfood.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 Nextfood.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 Nextfood.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

nextfood.jp

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