Tools & Wizards About Us
wittlebee.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wittlebee.com

Cute Kids Clothes & Shoes Online, Personalized from FabKids!

Page Load Speed

2.6 sec in total

First Response

95 ms

Resources Loaded

2 sec

Page Rendered

557 ms

wittlebee.com screenshot

About Website

Welcome to wittlebee.com homepage info - get ready to check Wittlebee best content right away, or after learning these important things about wittlebee.com

Shop online for cute kids clothes and shoes with FabKids. FabKids delivers high quality, ready-to-play boys and girls clothing & shoes every month!

Visit wittlebee.com

Key Findings

We analyzed Wittlebee.com page load time and found that the first response time was 95 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wittlebee.com performance score

0

Network Requests Diagram

95 ms

79 ms

index.cfm

152 ms

main-v2016032003.css

254 ms

scroller-v2016032003.css

93 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wittlebee.com, 6% (6 requests) were made to Fabkids.com and 5% (5 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (542 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 719.7 kB (29%)

Content Size

2.5 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wittlebee.com main page is 2.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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 37.6 kB

  • Original 50.2 kB
  • After minification 47.0 kB
  • After compression 12.5 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.6 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 9.9 kB

  • Original 1.5 MB
  • After minification 1.5 MB

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. Wittlebee images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 391.0 kB

  • Original 632.9 kB
  • After minification 627.9 kB
  • After compression 241.8 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 391.0 kB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 281.1 kB

  • Original 333.5 kB
  • After minification 258.0 kB
  • After compression 52.3 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. Wittlebee.com needs all CSS files to be minified and compressed as it can save up to 281.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (48%)

Requests Now

88

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

95 ms

79 ms

index.cfm

index.cfm

152 ms

main-v2016032003.css

main-v2016032003.css

254 ms

scroller-v2016032003.css

scroller-v2016032003.css

93 ms

merged.js

merged.js

138 ms

mixpanel.js

mixpanel.js

64 ms

login.js

login.js

65 ms

conversion.js

conversion.js

35 ms

hbb4rpw.js

hbb4rpw.js

124 ms

modernizr-custom.js

modernizr-custom.js

97 ms

5001_style.css

5001_style.css

244 ms

slick.css

slick.css

37 ms

jquery-2.1.4.min.js

jquery-2.1.4.min.js

51 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

62 ms

slick.min.js

slick.min.js

38 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

17 ms

metanav_dropdown_jf2.jpg

metanav_dropdown_jf2.jpg

40 ms

womens_dropdown_loggedout.jpg

womens_dropdown_loggedout.jpg

192 ms

banner_arrow.png

banner_arrow.png

101 ms

button.png

button.png

334 ms

mens_dropdown_loggedout.jpg

mens_dropdown_loggedout.jpg

192 ms

fabkids_logo.png

fabkids_logo.png

46 ms

banner--open-1.jpg

banner--open-1.jpg

46 ms

banner--open-2.jpg

banner--open-2.jpg

46 ms

banner--close-1.jpg

banner--close-1.jpg

45 ms

banner--close-2.jpg

banner--close-2.jpg

86 ms

masthead-1.jpg

masthead-1.jpg

311 ms

masthead-2.jpg

masthead-2.jpg

298 ms

kids.jpg

kids.jpg

235 ms

offer-1.jpg

offer-1.jpg

196 ms

as-easy-as.jpg

as-easy-as.jpg

196 ms

offer-2.jpg

offer-2.jpg

291 ms

product-1.jpg

product-1.jpg

232 ms

product-2.jpg

product-2.jpg

232 ms

product-3.jpg

product-3.jpg

287 ms

product-4.jpg

product-4.jpg

288 ms

product-5.jpg

product-5.jpg

292 ms

product-6.jpg

product-6.jpg

308 ms

product-7.jpg

product-7.jpg

308 ms

product-8.jpg

product-8.jpg

310 ms

product-9.jpg

product-9.jpg

311 ms

product-10.jpg

product-10.jpg

315 ms

prod-offer-1.jpg

prod-offer-1.jpg

332 ms

prod-offer-2.jpg

prod-offer-2.jpg

331 ms

prod-offer-3.jpg

prod-offer-3.jpg

333 ms

prod-offer-4.jpg

prod-offer-4.jpg

334 ms

membership.jpg

membership.jpg

367 ms

pinterest.png

pinterest.png

333 ms

visa_checkout_popup_banner-v2.jpg

visa_checkout_popup_banner-v2.jpg

360 ms

78 ms

j.php

j.php

23 ms

gpt.js

gpt.js

22 ms

55 ms

53 ms

51 ms

pubads_impl_82.js

pubads_impl_82.js

12 ms

v.gif

v.gif

9 ms

va-f9423035fc9f0fdad5f7654cfb9df14b.js

va-f9423035fc9f0fdad5f7654cfb9df14b.js

43 ms

opa-949357b71eda375b06a39eb1b86f4730.js

opa-949357b71eda375b06a39eb1b86f4730.js

46 ms

container.html

container.html

42 ms

www.fabkids.com

www.fabkids.com

117 ms

145 ms

gtm.js

gtm.js

67 ms

metanav_bg.jpg

metanav_bg.jpg

140 ms

metanav_tab_0715.png

metanav_tab_0715.png

133 ms

cX1RYZExRAFI02BUiSOd4etVJcYj3peZCMLFddQh6-Gff4AgggMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXt26.woff

cX1RYZExRAFI02BUiSOd4etVJcYj3peZCMLFddQh6-Gff4AgggMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXt26.woff

100 ms

RU3U1a0LoGoq0icj7XXP8WoYdhQklg1fR68NwtKLxK9ff5WcggMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgM.woff

RU3U1a0LoGoq0icj7XXP8WoYdhQklg1fR68NwtKLxK9ff5WcggMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtgM.woff

148 ms

3oTBzyiZ8Ncg1j8bC4Aiy3jwzTFJfemycNe0BM_hrH3ff4egggMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

3oTBzyiZ8Ncg1j8bC4Aiy3jwzTFJfemycNe0BM_hrH3ff4egggMdeMJ6Mk6fw6NuSh90iY83ZAlTifoRdhXtg3.woff

188 ms

IFcsbsaqqyilOeRX+Y6CyPmVkp11FKyb3SfgE82nvIAAAAeJxtxbkNgDAQRNGd5TCniOnC5nYIAb2QkNGfOwOEJuRLX09Uvu4grfzVvEMUiggxEqQwyJCjQIkKtbnOY3fWUkc72tOBjnSiM12opyvdHkWdHJsA

IFcsbsaqqyilOeRX+Y6CyPmVkp11FKyb3SfgE82nvIAAAAeJxtxbkNgDAQRNGd5TCniOnC5nYIAb2QkNGfOwOEJuRLX09Uvu4grfzVvEMUiggxEqQwyJCjQIkKtbnOY3fWUkc72tOBjnSiM12opyvdHkWdHJsA

19 ms

analytics.js

analytics.js

25 ms

conversion_async.js

conversion_async.js

25 ms

activityi;src=4402945;type=count651;cat=FabKi0;u=Desktop;u1=Desktop;ord=3943013525894;~oref=http%3A%2F%2Fwww.fabkids.com%2Findex.cfm%3Fwb%3D1

activityi;src=4402945;type=count651;cat=FabKi0;u=Desktop;u1=Desktop;ord=3943013525894;~oref=http%3A%2F%2Fwww.fabkids.com%2Findex.cfm%3Fwb%3D1

58 ms

ec.js

ec.js

33 ms

43 ms

45 ms

1405.js

1405.js

15 ms

widgets.js

widgets.js

11 ms

collect

collect

91 ms

89 ms

set.gif

set.gif

62 ms

86 ms

9d8a06d88c341ba9df27400188783513.js

9d8a06d88c341ba9df27400188783513.js

185 ms

button.png

button.png

74 ms

fbevents.js

fbevents.js

193 ms

bat.js

bat.js

212 ms

src=5050112;type=invmedia;cat=rvpdppul;ord=9781425278633.832

src=5050112;type=invmedia;cat=rvpdppul;ord=9781425278633.832

139 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

79 ms

1405.js

1405.js

66 ms

collect

collect

97 ms

p.gif

p.gif

149 ms

s

s

89 ms

u

u

75 ms

like.php

like.php

216 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

13 ms

ga-audiences

ga-audiences

26 ms

6 ms

jot

jot

81 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

480 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

542 ms

SEO Factors

wittlebee.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wittlebee.com 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 Wittlebee.com main page’s claimed encoding is . 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.

Social Sharing Optimization

wittlebee.com

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