2.3 sec in total
198 ms
1.7 sec
319 ms
Click here to check amazing Bazzlewazzle content. Otherwise, check out these important facts you probably never knew about bazzlewazzle.com
Visit bazzlewazzle.comWe analyzed Bazzlewazzle.com page load time and found that the first response time was 198 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster. This domain responded with an error, which can significantly jeopardize Bazzlewazzle.com rating and web reputation
bazzlewazzle.com performance score
198 ms
101 ms
115 ms
134 ms
133 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 47% of them (52 requests) were addressed to the original Bazzlewazzle.com, 19% (21 requests) were made to Scontent.cdninstagram.com and 9% (10 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (750 ms) belongs to the original domain Bazzlewazzle.com.
Page size can be reduced by 972.1 kB (40%)
2.4 MB
1.5 MB
In fact, the total size of Bazzlewazzle.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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.8 kB or 78% of the original size.
Potential reduce by 54.5 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. Bazzlewazzle images are well optimized though.
Potential reduce by 669.7 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 669.7 kB or 70% of the original size.
Potential reduce by 204.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. Bazzlewazzle.com needs all CSS files to be minified and compressed as it can save up to 204.1 kB or 82% of the original size.
Number of requests can be reduced by 51 (52%)
98
47
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bazzlewazzle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
bazzlewazzle.com
198 ms
wp-emoji-release.min.js
101 ms
wpapp-styles.css
115 ms
style2-os.css
134 ms
lightbox.css
133 ms
font-awesome.css
175 ms
sb-instagram.css
178 ms
font-awesome.min.css
9 ms
checkbox.min.css
171 ms
form.min.css
173 ms
style.css
212 ms
font-awesome.min.css
222 ms
bootstrap.min.css
285 ms
owl.carousel.css
274 ms
owl.theme.css
238 ms
main.css
268 ms
jquery.js
442 ms
jquery-migrate.min.js
309 ms
bootstrap.min.js
360 ms
owl.carousel.min.js
391 ms
hoverIntent.min.js
351 ms
custom.js
341 ms
jquery.colorbox.js
391 ms
gallery-all.js
399 ms
jquery.hugeitmicro.min.js
424 ms
sb-instagram.js
534 ms
navigation.js
535 ms
skip-link-focus-fix.js
533 ms
wp-embed.min.js
532 ms
placeholders.min.js
533 ms
css
28 ms
x-click-but11.gif
278 ms
unesco-100X32.png
561 ms
search.png
269 ms
Ponta-do-Ouro-34-377x257.jpg
269 ms
yellow-billed-hornbill-377x257.jpg
269 ms
cheetah-staring-377x257.jpg
392 ms
cloudy-sunrise-at-three-rondawels-377x257.jpg
329 ms
20140409-074509-e1397365134547-377x257.jpg
278 ms
loader.png
417 ms
Ponta-do-Ouro-34-400x225.jpg
418 ms
yellow-billed-hornbill-400x225.jpg
401 ms
cheetah-staring-400x225.jpg
735 ms
cloudy-sunrise-at-three-rondawels-400x225.jpg
474 ms
orangeriver-010113-1051-400x225.jpg
558 ms
20140409-074509-e1397365134547-400x225.jpg
475 ms
photo-400x225.jpg
652 ms
Me_on_Top_of_the_World-400x225.jpg
596 ms
lions-and-elephant-400x225.jpg
690 ms
facebook.png
559 ms
google.png
599 ms
twitter.png
631 ms
instagram.png
651 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
36 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
36 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
37 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
37 ms
fontawesome-webfont.woff
750 ms
fontawesome-webfont.woff
36 ms
maps
35 ms
embed
199 ms
209874745
145 ms
recent
396 ms
arrowleft.png
443 ms
arrowright.png
510 ms
js
76 ms
init_embed.js
40 ms
11417506_735630476559861_1921557251_a.jpg
86 ms
common.js
68 ms
map.js
87 ms
google4.png
30 ms
overlay.js
56 ms
util.js
35 ms
onion.js
34 ms
stats.js
33 ms
ViewportInfoService.GetViewportInfo
37 ms
controls.js
33 ms
transparent.png
25 ms
kh
114 ms
css
102 ms
mapcnt6.png
50 ms
vt
42 ms
vt
43 ms
vt
52 ms
vt
51 ms
vt
52 ms
12729443_1510226569282823_755643948_n.jpg
73 ms
12747644_825411584236062_1028908623_n.jpg
261 ms
12729593_198009717221799_1679547284_n.jpg
82 ms
12748152_1052615934790833_440588469_n.jpg
114 ms
12717030_1697330033845731_237866314_n.jpg
106 ms
12747840_1529225450711725_2113225470_n.jpg
82 ms
12531097_153149335067371_413740910_n.jpg
168 ms
12628018_202793876741824_1139201570_n.jpg
144 ms
12317809_1731920547037721_1114102202_n.jpg
129 ms
12328144_975212715884962_273205346_n.jpg
145 ms
12093436_1685803911642634_1191076969_n.jpg
186 ms
12142110_1485044321803350_885871960_n.jpg
391 ms
11348140_791729784269868_39113611_n.jpg
203 ms
11887209_1005329102842792_2120716094_n.jpg
196 ms
11934916_910168759076907_1016367271_n.jpg
239 ms
11950556_1626561334283164_305460439_n.jpg
298 ms
11191371_1666892273531127_775686246_n.jpg
266 ms
11849399_505984969564632_654643706_n.jpg
246 ms
11379015_907698222622628_1822976434_n.jpg
279 ms
11424687_1590123231240128_157443653_n.jpg
328 ms
AuthenticationService.Authenticate
23 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
45 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
45 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
49 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
48 ms
bazzlewazzle.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bazzlewazzle.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Bazzlewazzle.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.
bazzlewazzle.com
Open Graph description is not detected on the main page of Bazzlewazzle. 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: