7.3 sec in total
1.1 sec
5 sec
1.2 sec
Visit cafebusybee.com now to see the best up-to-date Cafe Busy Bee content and also check out these interesting facts you probably never knew about cafebusybee.com
Welcome to Busy Bee Cafe, Pokhara. Our Cafe is the most hot and happening place in town. We have the best live music performed by our own local bands.
Visit cafebusybee.comWe analyzed Cafebusybee.com page load time and found that the first response time was 1.1 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
cafebusybee.com performance score
1122 ms
85 ms
217 ms
199 ms
228 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 50% of them (48 requests) were addressed to the original Cafebusybee.com, 23% (22 requests) were made to Static.xx.fbcdn.net and 4% (4 requests) were made to Tripadvisor.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Cafebusybee.com.
Page size can be reduced by 742.0 kB (33%)
2.2 MB
1.5 MB
In fact, the total size of Cafebusybee.com main page is 2.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 37.7 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 37.7 kB or 78% of the original size.
Potential reduce by 61.2 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. Cafe Busy Bee images are well optimized though.
Potential reduce by 399.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 399.5 kB or 71% of the original size.
Potential reduce by 243.7 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. Cafebusybee.com needs all CSS files to be minified and compressed as it can save up to 243.7 kB or 83% of the original size.
Number of requests can be reduced by 52 (63%)
82
30
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cafe Busy Bee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.cafebusybee.com
1122 ms
wp-emoji-release.min.js
85 ms
styles.css
217 ms
settings.css
199 ms
testimonials.css
228 ms
jquery.js
305 ms
jquery-migrate.min.js
243 ms
sharethis.js
22 ms
style.css
207 ms
jquery.min.js
326 ms
bootstrap.min.js
331 ms
owl.carousel.js
290 ms
main.js
325 ms
jquery.form.min.js
330 ms
scripts.js
404 ms
jquery.themepunch.tools.min.js
384 ms
jquery.themepunch.revolution.min.js
520 ms
jquery.touchSwipe.min.js
478 ms
jquery.carouFredSel-6.2.1.js
527 ms
testimonials.js
489 ms
wp-embed.min.js
484 ms
wejs
61 ms
backend.css
904 ms
theme.css
263 ms
logo.png
261 ms
IMG_0188.jpg
391 ms
busybee2.jpg
369 ms
busybee3.jpg
376 ms
14390880_10154788309910579_2198999690230590207_n.jpg
437 ms
portal-v2.html
40 ms
pview
30 ms
sc
8 ms
bootstrap.min.css
98 ms
font-awesome.min.css
187 ms
owl.carousel.css
172 ms
owl.theme.css
190 ms
css
40 ms
css
53 ms
150_logo-11900-2.png
133 ms
ver.png
403 ms
fullbg.jpg
271 ms
woodbg.jpg
401 ms
music.png
132 ms
bar.png
132 ms
drinks.png
132 ms
foosball.png
152 ms
projector.png
263 ms
night.png
263 ms
flogo.png
607 ms
page.php
196 ms
waiter.png
337 ms
WidgetEmbed-selfserveprop
161 ms
kmKnZrc3Hgbbcjq75U4uslyuy4kn0qNZaxU.woff
75 ms
kmKiZrc3Hgbbcjq75U4uslyuy4kn0qviTgY3KcY.woff
155 ms
JTUSjIg1_i6t8kCHKm459WlhzQ.woff
161 ms
JTURjIg1_i6t8kCHKm45_dJE3gnD-A.woff
160 ms
fontawesome-webfont.woff
489 ms
gototop.png
885 ms
d6FPiOyXG_y.css
116 ms
XEx2-uP0Yml.js
123 ms
gdubTbs8BVr.js
163 ms
qbn7sPmFm1a.js
162 ms
Yw9ECELkTtd.js
166 ms
CIVcvZHipv7.js
149 ms
4cIiPol996W.js
174 ms
dyV3qsrTAy9.js
161 ms
vrZe-AqollU.js
177 ms
D2IqYON6k0P.js
179 ms
UhWhPF139tZ.js
179 ms
www.cafebusybee.com
858 ms
revolution.extension.slideanims.min.js
198 ms
revolution.extension.layeranimation.min.js
200 ms
revolution.extension.navigation.min.js
357 ms
t4b_widget_self_serve_property-v2455771303a.css
161 ms
cdswidgets_m-c-v22480917520a.js
168 ms
11050101_10153315474405579_8163729533835467472_o.png
223 ms
M1Igcn84_4v.js
30 ms
ApcBOUT5FoS.png
22 ms
ver.png
412 ms
478 ms
101 ms
onuUJj0tCqE.png
34 ms
revicons.woff
91 ms
css;base64,
10 ms
L8MW8Ah7kvk.css
75 ms
9dZlw4wAPJc.js
74 ms
XsZrBzRbAuP.js
74 ms
IvXs96C8BCn.js
73 ms
gDib98frgJW.js
73 ms
jXP1806tPlE.js
73 ms
css;%20charset=utf-8,.l_c3pyo2v0u%7Bmargin-bottom:6px%7D.a_c3pyo4on2%7Bmargin-right:8px%7D.r_c3pyo2ey1%20.h_c3pyo4oy5%7B-webkit-box-align:center;display:-webkit-box%7D.y_c3pyo2ta3%7Bmargin-bottom:-6px%7D.u_c3pyo2ta4%7Bpadding-bottom:6px%7D._5v3q%20.l_c3pyo2v0u%7Bmargin-bottom:11px%7D._5v3q%20.l_c3pyo2v0u.i_c3pynyi2f%7Bmargin-bottom:-1px%7D._5v3q%20.l_c3pyo2v0u.i_c3pynyi2f%20.o_c3pynyi2g%7Bpadding-bottom:3px%7D._5v3q%20._5pa-%20.l_c3pyo2v0u%7Bmargin-bottom:7px%7D.r_c3pyo2ey1%7Bborder-bottom:1px%20solid%20%2523e9e9e9;color:%25237f7f7f;display:block;font-size:13px;margin:-18px%200%2014px;padding:13px%200%2013px%7D._5v3q%20._90od%20.r_c3pyo2ey1%7Bborder-bottom:none;padding-bottom:0;padding-top:12px%7D._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1,._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1%20a%7Bcolor:%2523606770%7D._5v3q%20._90oc%20._1s31%20.r_c3pyo2ey1%20.profileLink%7Bfont-weight:500%7D._5v3q%20.r_c3pyo2ey1%7Bborder-bottom-color:%2523e5e5e5;color:%252390949c;line-height:15px;margin:-12px%200%2012px;padding:10px%2023px%2010px%200%7D._5v3q%20.r_c3pyo2ey1.x_c3pynzq_4,._1s31.x_c3pynzq_4%20.r_c3pyo2ey1%7Bcolor:%2523616770%7D._5v3q%20.r_c3pyo2ey1.v_c3pynzq_6,._1s31.v_c3pynzq_6%20.r_c3pyo2ey1%7Bfont-size:13px%7D._3ccb%20.r_c3pyo2ey1%7Bfont-size:12px;padding-bottom:9px;padding-top:11px%7D._49gl%20.r_c3pyo2ey1%7Bdisplay:none%7D._6q1a%20.i_c3pyo4rdp.r_c3pyo2ey1%7B-webkit-box-align:center;display:-webkit-box%7D._6q1a%20.i_c3pyo4rdp%20.w_c3pyo4re7%7Bfont-size:14px;line-height:16px%7D._6q1a%20.i_c3pyo4rdp%20.w_c3pyo4re7%20.profileLink%7Bfont-weight:bold%7D._6q1a%20.q_c3pyo4i9a%7Bpadding-right:0%7D._6q1a%20.i_c3pyo4rdp%20.u_c3pyo46d6%7B-webkit-box-flex:1;font-weight:bold;word-break:break-word%7D._6q1a%20.i_c3pyo4rdp%20.e_c3pyo4re8%7B-webkit-box-align:center;background-color:%252342b72a;border-radius:50%25;-webkit-box-shadow:0%202px%204px%200%20rgba(0,%200,%200,%20.1);display:-webkit-inline-box;height:24px;-webkit-box-pack:center;margin-right:8px;width:24px%7D%2523bootloader_TvoAA%7Bheight:42px;%7D.bootloader_TvoAA%7Bdisplay:block!important;%7D
71 ms
LcYJYpBb7bj.css
72 ms
05eiaXtg9Ig.js
75 ms
Tripadvisor_lockup_horizontal_secondary_registered-11900-2.svg
44 ms
analytics.js
110 ms
TripAdvisor_Regular.woff
17 ms
cafebusybee.com SEO score
EN
EN
US-ASCII
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cafebusybee.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Cafebusybee.com main page’s claimed encoding is us-ascii. 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.
cafebusybee.com
Open Graph data is detected on the main page of Cafe Busy Bee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: