Tools & Wizards About Us
nakaei.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

nakaei.com

中栄（なかえい）｜築地　卸売市場｜大正元年創業の老舗インドカレー店

Page Load Speed

4.7 sec in total

First Response

532 ms

Resources Loaded

3.7 sec

Page Rendered

414 ms

nakaei.com screenshot

About Website

Welcome to nakaei.com homepage info - get ready to check Nakaei best content right away, or after learning these important things about nakaei.com

築地市場内でランチなら大正元年創業の老舗カレーの中栄（なかえい）です。独自の伝統製法で（全て手作り）によるリーズナブルでボリュームのあるカレーをご提供させて頂きます。市場に来た際は、印度カレーの中栄にお越し下さい。

Visit nakaei.com

Key Findings

We analyzed Nakaei.com page load time and found that the first response time was 532 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.

Performance Metrics

nakaei.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value25.6 s

0/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.674

8/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

nakaei.com

532 ms

www.nakaei.com

586 ms

style.css

181 ms

colorbox.css

329 ms

style.min.css

330 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 90% of them (53 requests) were addressed to the original Nakaei.com, 3% (2 requests) were made to Ajax.googleapis.com and 3% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Nakaei.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 777.1 kB (8%)

Content Size

10.1 MB

After Optimization

9.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nakaei.com main page is 10.1 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. 50% of websites need less resources to load. Images take 9.9 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.1 kB

  • Original 29.5 kB
  • After minification 27.3 kB
  • After compression 7.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. 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 22.1 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 714.6 kB

  • Original 9.9 MB
  • After minification 9.2 MB

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. Nakaei images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 5.9 kB

  • Original 118.3 kB
  • After minification 118.3 kB
  • After compression 112.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-61%

Potential reduce by 34.5 kB

  • Original 56.6 kB
  • After minification 46.9 kB
  • After compression 22.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. Nakaei.com needs all CSS files to be minified and compressed as it can save up to 34.5 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (57%)

Requests Now

56

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nakaei.com

nakaei.com

532 ms

www.nakaei.com

www.nakaei.com

586 ms

style.css

style.css

181 ms

colorbox.css

colorbox.css

329 ms

style.min.css

style.min.css

330 ms

styles.css

styles.css

327 ms

jquery-ui.min.css

jquery-ui.min.css

7 ms

jquery-ui-timepicker-addon.min.css

jquery-ui-timepicker-addon.min.css

339 ms

jss-style.css

jss-style.css

349 ms

mappress.css

mappress.css

344 ms

jquery.js

jquery.js

657 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

484 ms

jquery-colorbox-wrapper-min.js

jquery-colorbox-wrapper-min.js

483 ms

script.js

script.js

500 ms

style-module.css

style-module.css

501 ms

style-editor.css

style-editor.css

514 ms

font-awesome.min.css

font-awesome.min.css

22 ms

flexslider.css

flexslider.css

643 ms

public.css

public.css

643 ms

jquery.form.min.js

jquery.form.min.js

682 ms

scripts.js

scripts.js

682 ms

core.min.js

core.min.js

718 ms

datepicker.min.js

datepicker.min.js

810 ms

datepicker-ja.min.js

datepicker-ja.min.js

5 ms

jquery-ui-timepicker-addon.min.js

jquery-ui-timepicker-addon.min.js

815 ms

jquery-ui-timepicker-ja.js

jquery-ui-timepicker-ja.js

806 ms

widget.min.js

widget.min.js

824 ms

mouse.min.js

mouse.min.js

835 ms

slider.min.js

slider.min.js

858 ms

button.min.js

button.min.js

968 ms

jquery-ui-sliderAccess.js

jquery-ui-sliderAccess.js

973 ms

jss-script.js

jss-script.js

973 ms

wp-embed.min.js

wp-embed.min.js

988 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1006 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

841 ms

news_bg.png

news_bg.png

799 ms

bg_header.png

bg_header.png

642 ms

logo.png

logo.png

643 ms

tel2103.png

tel2103.png

822 ms

bg_menu1.png

bg_menu1.png

520 ms

mv012-1900x617.png

mv012-1900x617.png

1945 ms

mv021-1900x617.png

mv021-1900x617.png

1875 ms

mv02-1900x617.png

mv02-1900x617.png

1782 ms

mv041-1900x617.png

mv041-1900x617.png

1786 ms

kodawari.png

kodawari.png

961 ms

menu.png

menu.png

1149 ms

shop.png

shop.png

1125 ms

goaisatsu.png

goaisatsu.png

1289 ms

side_menu.png

side_menu.png

1315 ms

side_shop.png

side_shop.png

1453 ms

side_eigyou2103.png

side_eigyou2103.png

1807 ms

bg_nav_01.png

bg_nav_01.png

1597 ms

bg_greeting1.png

bg_greeting1.png

1761 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

38 ms

ga.js

ga.js

22 ms

arrow.png

arrow.png

1887 ms

__utm.gif

__utm.gif

12 ms

overlay.png

overlay.png

1581 ms

bg_direction_nav.png

bg_direction_nav.png

1575 ms

Accessibility Review

nakaei.com accessibility score

67

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nakaei.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nakaei.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

nakaei.com

Open Graph data is detected on the main page of Nakaei. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: