4.4 sec in total
157 ms
4 sec
287 ms
Click here to check amazing Build A Bear content for Mexico. Otherwise, check out these important facts you probably never knew about buildabear.mx
Let's celebrate all the good stuff inside each & every one of us. All the moments, the memories—the stuff you love. Shop online or find a Workshop near you.
Visit buildabear.mxWe analyzed Buildabear.mx page load time and found that the first response time was 157 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
buildabear.mx performance score
157 ms
948 ms
265 ms
466 ms
269 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 95% of them (97 requests) were addressed to the original Buildabear.mx, 2% (2 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Buildabear.mx.
Page size can be reduced by 1.6 MB (47%)
3.5 MB
1.8 MB
In fact, the total size of Buildabear.mx main page is 3.5 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.5 MB which makes up the majority of the site volume.
Potential reduce by 55.9 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 15.1 kB, which is 23% 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 55.9 kB or 84% of the original size.
Potential reduce by 44.1 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. Build A Bear images are well optimized though.
Potential reduce by 548.9 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 548.9 kB or 70% of the original size.
Potential reduce by 969.2 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. Buildabear.mx needs all CSS files to be minified and compressed as it can save up to 969.2 kB or 90% of the original size.
Number of requests can be reduced by 27 (28%)
98
71
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Build A Bear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
buildabear.mx
157 ms
buildabear.mx
948 ms
jquery-ui.min.css
265 ms
bootstrap.min.css
466 ms
bootstrap-theme.min.css
269 ms
jquery.fancybox.css
204 ms
font-awesome.min.css
271 ms
style.css
335 ms
layerslider.css
341 ms
css
63 ms
js_composer.css
993 ms
greensock.js
473 ms
jquery.js
533 ms
jquery-migrate.min.js
400 ms
layerslider.kreaturamedia.jquery.js
533 ms
layerslider.transitions.js
472 ms
jquery-1.11.3.min.js
470 ms
jquery-ui.min.js
674 ms
bootstrap.min.js
474 ms
jquery.jplayer.min.js
540 ms
jquery.fancybox.pack.js
475 ms
jquery.fancybox-media.js
538 ms
jquery.validate.min.js
541 ms
lib.js
542 ms
css
14 ms
wp-embed.min.js
605 ms
js_composer_front.js
606 ms
fonts.css
403 ms
wp-emoji-release.min.js
69 ms
mexico.png
116 ms
germany.png
116 ms
australia.png
117 ms
bahrain.png
118 ms
brazil.png
117 ms
canada.png
118 ms
denmark.png
153 ms
united-arab-emirates.png
154 ms
united-states-of-america.png
155 ms
france.png
156 ms
ireland.png
156 ms
japan.png
157 ms
norway.png
525 ms
united-kingdom.png
525 ms
singapore.png
526 ms
south-africa.png
527 ms
sweden.png
527 ms
thailand.png
528 ms
logo.png
531 ms
img1.png
529 ms
img2.png
528 ms
img3.png
532 ms
BABW-bannerhome-PIKACHUok.png
595 ms
BABW-bannerhome-BTSPok.png
726 ms
BABW-bannerhome-britto.jpg
593 ms
1443474674_babw-bannerhomesw.jpg
562 ms
1438121917_bannerexterior-chimuelo.jpg
533 ms
timthumb.php
532 ms
timthumb.php
535 ms
timthumb.php
533 ms
timthumb.php
563 ms
timthumb.php
563 ms
timthumb.php
598 ms
timthumb.php
611 ms
timthumb.php
1615 ms
sdk.js
528 ms
timthumb.php
655 ms
fontawesome-webfont.woff
620 ms
timthumb.php
566 ms
timthumb.php
574 ms
timthumb.php
625 ms
timthumb.php
635 ms
futurastd-bold-webfont-webfont.woff
638 ms
timthumb.php
650 ms
timthumb.php
1651 ms
timthumb.php
656 ms
timthumb.php
665 ms
timthumb.php
670 ms
skin.css
393 ms
timthumb.php
370 ms
timthumb.php
370 ms
1354725205_desc2b.png
369 ms
1354725239_desc3b.png
472 ms
1354725348_desc1b.png
486 ms
img10.png
429 ms
img14.png
431 ms
preloader.gif
494 ms
bg1.png
498 ms
bg2.jpg
555 ms
img4.png
555 ms
img5.png
568 ms
img6.png
568 ms
img7.png
571 ms
img8.png
582 ms
bg3.png
593 ms
137 ms
bg3.jpg
594 ms
xd_arbiter.php
275 ms
bg4.png
607 ms
bg5.png
620 ms
bg6.png
626 ms
blank.gif
145 ms
skin.png
180 ms
buildabear.mx SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buildabear.mx 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 Buildabear.mx 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.
buildabear.mx
Open Graph description is not detected on the main page of Build A Bear. 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: