Tools & Wizards About Us
kanki.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

kanki.com

Home - Kanki Japanese House of Steak and Sushi | Raleigh, NC

Page Load Speed

1.4 sec in total

First Response

184 ms

Resources Loaded

796 ms

Page Rendered

371 ms

kanki.com screenshot

About Website

Visit kanki.com now to see the best up-to-date Kanki content for United States and also check out these interesting facts you probably never knew about kanki.com

Visit Kanki, a Japanese and sushi restaurant with three Triangle locations in Raleigh, North Raleigh, Durham. We specialize in teppanyaki and specialty sushi.

Visit kanki.com

Key Findings

We analyzed Kanki.com page load time and found that the first response time was 184 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

kanki.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value20.9 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

kanki.com

184 ms

css

65 ms

css

77 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

56 ms

css_u7MZUqvsqy8402d0RdK0_-GL-rzCHNloVvAyXnHdVr0.css

83 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 68% of them (42 requests) were addressed to the original Kanki.com, 13% (8 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (404 ms) belongs to the original domain Kanki.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 335.5 kB (14%)

Content Size

2.4 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kanki.com main page is 2.4 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 26.7 kB

  • Original 35.5 kB
  • After minification 34.4 kB
  • After compression 8.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. 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 26.7 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 102.9 kB

  • Original 2.1 MB
  • After minification 2.0 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. Kanki images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 167.1 kB

  • Original 246.7 kB
  • After minification 204.4 kB
  • After compression 79.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 167.1 kB or 68% of the original size.

CSS Optimization

-79%

Potential reduce by 38.8 kB

  • Original 49.3 kB
  • After minification 47.8 kB
  • After compression 10.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. Kanki.com needs all CSS files to be minified and compressed as it can save up to 38.8 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kanki. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kanki.com

kanki.com

184 ms

css

css

65 ms

css

css

77 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

56 ms

css_u7MZUqvsqy8402d0RdK0_-GL-rzCHNloVvAyXnHdVr0.css

css_u7MZUqvsqy8402d0RdK0_-GL-rzCHNloVvAyXnHdVr0.css

83 ms

css_9tSqeZVGrCh0O2-RjWti8pzVuO8WtrRx4-wShPmbwZ0.css

css_9tSqeZVGrCh0O2-RjWti8pzVuO8WtrRx4-wShPmbwZ0.css

72 ms

css_ZhW9sGQLra2P81CnW-AkBrx4udJGRGddMJyuCTB_zvE.css

css_ZhW9sGQLra2P81CnW-AkBrx4udJGRGddMJyuCTB_zvE.css

76 ms

respond.min.js

respond.min.js

80 ms

js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js

js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js

112 ms

js_X9gJhwZFvwblCfcf94-njvIUwKy7Ghi4p_XM_iK87gA.js

js_X9gJhwZFvwblCfcf94-njvIUwKy7Ghi4p_XM_iK87gA.js

110 ms

js_34ua6Wa4zdLTd9wTTJkiVl8XuMlyJDY94NC6wwoqRqQ.js

js_34ua6Wa4zdLTd9wTTJkiVl8XuMlyJDY94NC6wwoqRqQ.js

129 ms

js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js

js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js

128 ms

conversion.js

conversion.js

26 ms

dc.js

dc.js

66 ms

all.js

all.js

183 ms

76 ms

body-background.jpg

body-background.jpg

126 ms

Home-1.jpg

Home-1.jpg

298 ms

Home-2.jpg

Home-2.jpg

325 ms

logo-background.png

logo-background.png

72 ms

logo.png

logo.png

98 ms

logo.png

logo.png

68 ms

menu-icon.png

menu-icon.png

96 ms

red-texture.jpg

red-texture.jpg

115 ms

close-button.png

close-button.png

157 ms

Home-1.jpg

Home-1.jpg

240 ms

Home-2.jpg

Home-2.jpg

297 ms

crabtree-valley-mall.jpg

crabtree-valley-mall.jpg

172 ms

durham.jpg

durham.jpg

191 ms

north-raleigh.jpg

north-raleigh.jpg

222 ms

main-background.jpg

main-background.jpg

229 ms

holiday-gift-cards.jpg

holiday-gift-cards.jpg

295 ms

food-menus-corner.png

food-menus-corner.png

270 ms

food-menus-heading.png

food-menus-heading.png

293 ms

menus-item-background.png

menus-item-background.png

312 ms

hibachi-icon.png

hibachi-icon.png

326 ms

sushi-icon.png

sushi-icon.png

328 ms

sides-icon.png

sides-icon.png

336 ms

drinks-icon.png

drinks-icon.png

335 ms

features-icon.png

features-icon.png

347 ms

seasonal-icon.png

seasonal-icon.png

364 ms

footer-background.png

footer-background.png

367 ms

footer-container-background.jpg

footer-container-background.jpg

373 ms

twitter-icon.png

twitter-icon.png

376 ms

facebook-icon.png

facebook-icon.png

377 ms

instagram-icon.png

instagram-icon.png

389 ms

location-name-background.png

location-name-background.png

404 ms

locations-item-background.jpg

locations-item-background.jpg

401 ms

MG9KbUZFchDs94Tbv9U-pSZ2oysoEQEeKwjgmXLRnTc.ttf

MG9KbUZFchDs94Tbv9U-pSZ2oysoEQEeKwjgmXLRnTc.ttf

37 ms

SQVfzoJBbj9t3aVcmbspRpS3E-kSBmtLoNJPDtbj2Pk.ttf

SQVfzoJBbj9t3aVcmbspRpS3E-kSBmtLoNJPDtbj2Pk.ttf

44 ms

uDssvmXgp7Nj3i336k_dSpS3E-kSBmtLoNJPDtbj2Pk.ttf

uDssvmXgp7Nj3i336k_dSpS3E-kSBmtLoNJPDtbj2Pk.ttf

66 ms

-91TwiFzqeL1F7Kh91APwZS3E-kSBmtLoNJPDtbj2Pk.ttf

-91TwiFzqeL1F7Kh91APwZS3E-kSBmtLoNJPDtbj2Pk.ttf

62 ms

Q-XbT1m22Fi9BEKb7y59O8DdSZkkecOE1hvV7ZHvhyU.ttf

Q-XbT1m22Fi9BEKb7y59O8DdSZkkecOE1hvV7ZHvhyU.ttf

62 ms

IWi8e5bpnqhMRsZKTcTUWsBaWKZ57bY3RXgXH6dOjZ0.ttf

IWi8e5bpnqhMRsZKTcTUWsBaWKZ57bY3RXgXH6dOjZ0.ttf

65 ms

jvx_POxM6YeT6dBBhDfmuXYhjbSpvc47ee6xR_80Hnw.ttf

jvx_POxM6YeT6dBBhDfmuXYhjbSpvc47ee6xR_80Hnw.ttf

65 ms

F5BSMOSf_T8GT2wiqqpj3SwlidHJgAgmTjOEEzwu1L8.ttf

F5BSMOSf_T8GT2wiqqpj3SwlidHJgAgmTjOEEzwu1L8.ttf

65 ms

__utm.gif

__utm.gif

18 ms

__utm.gif

__utm.gif

37 ms

54 ms

136 ms

xd_arbiter.php

xd_arbiter.php

129 ms

xd_arbiter.php

xd_arbiter.php

254 ms

Accessibility Review

kanki.com accessibility score

47

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

kanki.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

kanki.com SEO score

82

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanki.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Kanki.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

kanki.com

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