Tools & Wizards About Us
kekanto.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kekanto.com.br

Delivery Direto | Encontre restaurantes que entregam na sua casa

Page Load Speed

7.4 sec in total

First Response

2.8 sec

Resources Loaded

4.2 sec

Page Rendered

328 ms

kekanto.com.br screenshot

About Website

Visit kekanto.com.br now to see the best up-to-date Kekanto content for Brazil and also check out these interesting facts you probably never knew about kekanto.com.br

Faça pedidos online em restaurantes perto de casa. Encontre restaurantes com descontos ótimos que entregam na sua região.

Visit kekanto.com.br

Key Findings

We analyzed Kekanto.com.br page load time and found that the first response time was 2.8 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

kekanto.com.br performance score

0

Network Requests Diagram

kekanto.com.br

2849 ms

css

55 ms

bootstrap.min.css,kekanto.css

72 ms

post_box.css

67 ms

kanalytics.js

478 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Kekanto.com.br, 13% (9 requests) were made to 1.kekantoimg.com and 13% (9 requests) were made to 3.kekantoimg.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Kekanto.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.0 kB (53%)

Content Size

749.4 kB

After Optimization

352.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kekanto.com.br main page is 749.4 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. 40% of websites need less resources to load. Javascripts take 377.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 153.4 kB

  • Original 179.9 kB
  • After minification 122.8 kB
  • After compression 26.6 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 57.1 kB, which is 32% 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 153.4 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 6.3 kB

  • Original 187.1 kB
  • After minification 180.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. Kekanto images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 234.2 kB

  • Original 377.7 kB
  • After minification 367.1 kB
  • After compression 143.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 234.2 kB or 62% of the original size.

CSS Optimization

-67%

Potential reduce by 3.2 kB

  • Original 4.7 kB
  • After minification 3.5 kB
  • After compression 1.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. Kekanto.com.br needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (40%)

Requests Now

62

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kekanto.com.br

kekanto.com.br

2849 ms

css

css

55 ms

bootstrap.min.css,kekanto.css

bootstrap.min.css,kekanto.css

72 ms

post_box.css

post_box.css

67 ms

kanalytics.js

kanalytics.js

478 ms

gpt.js

gpt.js

36 ms

multiplus-popup-fullscreen.png

multiplus-popup-fullscreen.png

348 ms

gtm.js

gtm.js

147 ms

logo-kekanto-2016.png

logo-kekanto-2016.png

362 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

139 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

271 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

361 ms

pubads_impl_81.js

pubads_impl_81.js

222 ms

sprite_n_kkto.png

sprite_n_kkto.png

341 ms

1639832.jpg

1639832.jpg

396 ms

1639854.jpg

1639854.jpg

389 ms

1657175.jpg

1657175.jpg

395 ms

583546.jpg

583546.jpg

386 ms

1640241.jpg

1640241.jpg

281 ms

1639841.jpg

1639841.jpg

280 ms

1639949.jpg

1639949.jpg

323 ms

1639849.jpg

1639849.jpg

323 ms

1063321.jpg

1063321.jpg

330 ms

1664857.jpg

1664857.jpg

329 ms

1624743.jpg

1624743.jpg

385 ms

1670331.jpg

1670331.jpg

382 ms

275751.jpg

275751.jpg

387 ms

1639848.jpg

1639848.jpg

340 ms

98956.jpg

98956.jpg

381 ms

multi_bg_1.png

multi_bg_1.png

329 ms

btn_android.png

btn_android.png

339 ms

btn_ios.png

btn_ios.png

321 ms

btn_wp.png

btn_wp.png

579 ms

app_kekanto.png

app_kekanto.png

389 ms

sprite_estrelas.png

sprite_estrelas.png

328 ms

Pikaday.css

Pikaday.css

408 ms

b=js&v=.v80&f=kekanto.js

b=js&v=.v80&f=kekanto.js

161 ms

pikaday.jquery.js,config_push_chrome.js,main_push_chrome.js

pikaday.jquery.js,config_push_chrome.js,main_push_chrome.js

69 ms

1683258.jpg

1683258.jpg

375 ms

1914002o.jpg

1914002o.jpg

372 ms

footer-sao-paulo.jpg

footer-sao-paulo.jpg

318 ms

222723o.jpg

222723o.jpg

372 ms

850115.jpg

850115.jpg

374 ms

383039o.jpg

383039o.jpg

374 ms

1684943.jpg

1684943.jpg

377 ms

747047o.jpg

747047o.jpg

377 ms

prefeitura.png

prefeitura.png

536 ms

analytics.js

analytics.js

180 ms

fontello.woff

fontello.woff

598 ms

fontello.woff

fontello.woff

116 ms

1363.js

1363.js

223 ms

container.html

container.html

129 ms

collect

collect

14 ms

collect

collect

196 ms

ga.js

ga.js

150 ms

client:plusone.js

client:plusone.js

166 ms

s

s

124 ms

u

u

115 ms

__utm.gif

__utm.gif

90 ms

__utm.gif

__utm.gif

83 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

24 ms

postmessageRelay

postmessageRelay

46 ms

collect

collect

24 ms

api.js

api.js

42 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

69 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

56 ms

nr-852.min.js

nr-852.min.js

55 ms

SEO Factors

kekanto.com.br SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kekanto.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Kekanto.com.br 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

kekanto.com.br

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