Tools & Wizards About Us
currycarry.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

currycarry.jp

【カレーデリバリーのカレーキャリー】

Page Load Speed

23.5 sec in total

First Response

858 ms

Resources Loaded

22.3 sec

Page Rendered

334 ms

currycarry.jp screenshot

About Website

Welcome to currycarry.jp homepage info - get ready to check Currycarry best content right away, or after learning these important things about currycarry.jp

カレーキャリーでは264通りのバラエティー豊かなメニューと、吟味された良質の素材から生まれた本格派の“欧風カレー”をぜひお試しください。

Visit currycarry.jp

Key Findings

We analyzed Currycarry.jp page load time and found that the first response time was 858 ms and then it took 22.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

currycarry.jp performance score

0

Network Requests Diagram

currycarry.jp

858 ms

jquery.js

1289 ms

ddsmoothmenu.js

605 ms

ddsmoothmenu.css

392 ms

main.css

390 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 82% of them (14 requests) were addressed to the original Currycarry.jp, 12% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Web10.jimdo.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Web10.jimdo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.5 kB (28%)

Content Size

486.8 kB

After Optimization

352.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Currycarry.jp main page is 486.8 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. Images take 302.3 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 3.1 kB

  • Original 5.4 kB
  • After minification 5.0 kB
  • After compression 2.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 3.1 kB or 58% of the original size.

Image Optimization

-0%

Potential reduce by 421 B

  • Original 302.3 kB
  • After minification 301.8 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. Currycarry images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 111.4 kB

  • Original 153.0 kB
  • After minification 101.1 kB
  • After compression 41.6 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 111.4 kB or 73% of the original size.

CSS Optimization

-75%

Potential reduce by 19.6 kB

  • Original 26.1 kB
  • After minification 23.6 kB
  • After compression 6.6 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. Currycarry.jp needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (47%)

Requests Now

15

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

currycarry.jp

currycarry.jp

858 ms

jquery.js

jquery.js

1289 ms

ddsmoothmenu.js

ddsmoothmenu.js

605 ms

ddsmoothmenu.css

ddsmoothmenu.css

392 ms

main.css

main.css

390 ms

layout.css

layout.css

396 ms

font.css

font.css

404 ms

web.css

web.css

1091 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

853 ms

2.gif

2.gif

20289 ms

p1.gif

p1.gif

272 ms

spacer.gif

spacer.gif

274 ms

emotionheader.jpg

emotionheader.jpg

1872 ms

order_btn.png

order_btn.png

276 ms

ga.js

ga.js

165 ms

down.gif

down.gif

239 ms

__utm.gif

__utm.gif

58 ms

SEO Factors

currycarry.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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

currycarry.jp

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