Tools & Wizards About Us
buildabear.no screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

buildabear.no

Page Load Speed

1.2 sec in total

First Response

84 ms

Resources Loaded

982 ms

Page Rendered

104 ms

buildabear.no screenshot

About Website

Visit buildabear.no now to see the best up-to-date Buildabear content for Norway and also check out these interesting facts you probably never knew about buildabear.no

Create your very own Teddy Bear and other stuffed animals at the Build-A-Bear Workshop! You can choose, stuff, stitch, fluff and dress your new furry friend. Each Teddy Bear and stuffed animal will ha...

Visit buildabear.no

Key Findings

We analyzed Buildabear.no page load time and found that the first response time was 84 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

buildabear.no performance score

0

Network Requests Diagram

buildabear.no

84 ms

11700007

162 ms

css

24 ms

jquery.min.js

10 ms

modernizr-2.7.1.min.js

11 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Buildabear.no, 55% (36 requests) were made to Buildabear.co.uk and 6% (4 requests) were made to Gateway.answerscloud.com. The less responsive or slowest element that took the longest time to load (434 ms) relates to the external source Buildabear.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (71%)

Content Size

1.4 MB

After Optimization

419.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buildabear.no main page is 1.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. 60% of websites need less resources to load. Javascripts take 850.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 43.8 kB

  • Original 60.8 kB
  • After minification 53.6 kB
  • After compression 17.0 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 7.2 kB, which is 12% 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 43.8 kB or 72% of the original size.

Image Optimization

-15%

Potential reduce by 7.7 kB

  • Original 51.0 kB
  • After minification 43.3 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. Obviously, Buildabear needs image optimization as it can save up to 7.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 580.1 kB

  • Original 850.5 kB
  • After minification 754.3 kB
  • After compression 270.4 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 580.1 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 397.0 kB

  • Original 485.9 kB
  • After minification 425.9 kB
  • After compression 88.8 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.no needs all CSS files to be minified and compressed as it can save up to 397.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (75%)

Requests Now

61

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

buildabear.no

buildabear.no

84 ms

11700007

11700007

162 ms

css

css

24 ms

jquery.min.js

jquery.min.js

10 ms

modernizr-2.7.1.min.js

modernizr-2.7.1.min.js

11 ms

kenshoo.js

kenshoo.js

20 ms

jquery-ui-1.10.3.custom.min.css

jquery-ui-1.10.3.custom.min.css

136 ms

dressMe.css

dressMe.css

129 ms

reset.css

reset.css

136 ms

screen_new.css

screen_new.css

129 ms

style.css

style.css

137 ms

babw.responsive.css

babw.responsive.css

146 ms

fonts.css

fonts.css

201 ms

global.min.css

global.min.css

150 ms

babw.responsive.js

babw.responsive.js

204 ms

s_code_babw_uk.js

s_code_babw_uk.js

144 ms

tt-ef0d2e96b08cee59a3557ca2ddba84bd84b4dabd4e2f882122a291bffee0acdd.js

tt-ef0d2e96b08cee59a3557ca2ddba84bd84b4dabd4e2f882122a291bffee0acdd.js

65 ms

p13n.js

p13n.js

59 ms

pagestart.min.js

pagestart.min.js

155 ms

conversion.js

conversion.js

16 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

244 ms

common.js

common.js

297 ms

swfobject.js

swfobject.js

272 ms

jquery.form.js

jquery.form.js

241 ms

jquery.defaultvalue.js

jquery.defaultvalue.js

314 ms

jquery.jqtransform.js

jquery.jqtransform.js

302 ms

jquery.color-2.1.2.min.js

jquery.color-2.1.2.min.js

320 ms

jquery.tinypubsub.js

jquery.tinypubsub.js

332 ms

babw.common.js

babw.common.js

332 ms

babw.cart.modal.js

babw.cart.modal.js

350 ms

jquery.waitUntilExists.js

jquery.waitUntilExists.js

397 ms

patch.js

patch.js

404 ms

global.min.js

global.min.js

338 ms

babw.name.me.js

babw.name.me.js

429 ms

jquery.sha1.js

jquery.sha1.js

427 ms

jquery.agegate.js

jquery.agegate.js

434 ms

babw.smarterremarketer.js

babw.smarterremarketer.js

359 ms

entry.js

entry.js

70 ms

e.gif

e.gif

57 ms

2bba9f

2bba9f

13 ms

ga.js

ga.js

38 ms

52000895.js

52000895.js

32 ms

buildabearuk.js

buildabearuk.js

32 ms

gateway.min.js

gateway.min.js

91 ms

94 ms

91 ms

workshop-logo-full.png

workshop-logo-full.png

142 ms

2BBA9F_F_0.woff

2BBA9F_F_0.woff

409 ms

p13n_generated.js

p13n_generated.js

60 ms

3725310.html

3725310.html

46 ms

__utm.gif

__utm.gif

31 ms

2BBA9F_C_0.woff

2BBA9F_C_0.woff

367 ms

foresee_trigger.js

foresee_trigger.js

42 ms

43 ms

src=5228803;type=invmedia;cat=juanf7gj;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=5007383115589.619

src=5228803;type=invmedia;cat=juanf7gj;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=5007383115589.619

65 ms

19 ms

23 ms

s58389835148118

s58389835148118

37 ms

loading.gif

loading.gif

115 ms

bg.png

bg.png

80 ms

SmarterHandler.ashx

SmarterHandler.ashx

60 ms

src=5228803;type=invmedia;cat=juanf7gj;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1645295473281.2942

src=5228803;type=invmedia;cat=juanf7gj;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1645295473281.2942

37 ms

nr-885.min.js

nr-885.min.js

23 ms

frameWorker.html

frameWorker.html

23 ms

0a6195046c

0a6195046c

45 ms

foresee_frame_controller.js

foresee_frame_controller.js

22 ms

SEO Factors

buildabear.no SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buildabear.no 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 Buildabear.no 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

buildabear.no

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