Tools & Wizards About Us
wawabebe.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wawabebe.com

와와베베

Page Load Speed

3.7 sec in total

First Response

398 ms

Resources Loaded

2.8 sec

Page Rendered

507 ms

wawabebe.com screenshot

About Website

Visit wawabebe.com now to see the best up-to-date Wawabebe content and also check out these interesting facts you probably never knew about wawabebe.com

핑크덕후 와와베베 핑크빛소품 캐릭터소품 전문

Visit wawabebe.com

Key Findings

We analyzed Wawabebe.com page load time and found that the first response time was 398 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wawabebe.com performance score

0

Network Requests Diagram

wawabebe.com

398 ms

www.wawabebe.com

500 ms

jquery-ui-1.8.5.custom.min.css

269 ms

jquery.bxslider.css

271 ms

skins.css

274 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Wawabebe.com, 44% (40 requests) were made to Hibult-static.websplanetdemo.com and 20% (18 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Hibult-static.websplanetdemo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 935.4 kB (30%)

Content Size

3.1 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wawabebe.com main page is 3.1 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 83.9 kB

  • Original 111.2 kB
  • After minification 109.9 kB
  • After compression 27.3 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 83.9 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 31.1 kB

  • Original 1.8 MB
  • After minification 1.8 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. Wawabebe images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 648.9 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 372.0 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 648.9 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 171.6 kB

  • Original 205.8 kB
  • After minification 191.6 kB
  • After compression 34.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. Wawabebe.com needs all CSS files to be minified and compressed as it can save up to 171.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (51%)

Requests Now

81

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wawabebe.com

wawabebe.com

398 ms

www.wawabebe.com

www.wawabebe.com

500 ms

jquery-ui-1.8.5.custom.min.css

jquery-ui-1.8.5.custom.min.css

269 ms

jquery.bxslider.css

jquery.bxslider.css

271 ms

skins.css

skins.css

274 ms

style.css

style.css

266 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

275 ms

concat_widget.min.css

concat_widget.min.css

388 ms

main.min.css

main.min.css

384 ms

skin_2176.min.css

skin_2176.min.css

386 ms

jquery.min.js

jquery.min.js

85 ms

jquery-ui.min.js

jquery-ui.min.js

105 ms

main.min.js

main.min.js

385 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

385 ms

skeleton.css

skeleton.css

385 ms

css

css

33 ms

wp-menu.js

wp-menu.js

500 ms

jQuery.circleMenu.js

jQuery.circleMenu.js

506 ms

addthis_widget.js

addthis_widget.js

72 ms

functions_stripped.js

functions_stripped.js

503 ms

iframe_api

iframe_api

49 ms

froogaloop2.min.js

froogaloop2.min.js

47 ms

jquery.fitvids.js

jquery.fitvids.js

511 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

580 ms

videoSlide.min.js

videoSlide.min.js

579 ms

w.imageslider.min.js

w.imageslider.min.js

613 ms

base64.js

base64.js

628 ms

w.line.min.js

w.line.min.js

626 ms

js

js

92 ms

w.gmap.min.js

w.gmap.min.js

645 ms

analytics.js

analytics.js

19 ms

collect

collect

24 ms

576212-wawabebe-fondo.w1900.jpg

576212-wawabebe-fondo.w1900.jpg

986 ms

642664---wawabebe-logo-en.png

642664---wawabebe-logo-en.png

757 ms

555449-boton-wawa.png

555449-boton-wawa.png

261 ms

642607--boton-about-us.png

642607--boton-about-us.png

262 ms

642602--boton-shopping.png

642602--boton-shopping.png

260 ms

642601--boton-how-to-buy.png

642601--boton-how-to-buy.png

261 ms

642600--boton-contact.png

642600--boton-contact.png

388 ms

576292--wawabebe-banner1.jpg

576292--wawabebe-banner1.jpg

1153 ms

576293--wawabebe-banner2.jpg

576293--wawabebe-banner2.jpg

1216 ms

576294--wawabebe-banner3.jpg

576294--wawabebe-banner3.jpg

1100 ms

576295--wawabebe-banner4.jpg

576295--wawabebe-banner4.jpg

1106 ms

576296--wawabebe-banner5.jpg

576296--wawabebe-banner5.jpg

995 ms

576297--wawabebe-banner6.w1024.jpg

576297--wawabebe-banner6.w1024.jpg

1223 ms

575955--wawa-bebe-marcas.png

575955--wawa-bebe-marcas.png

1116 ms

527763-iconos-02.png

527763-iconos-02.png

1220 ms

527762-iconos-01.png

527762-iconos-01.png

1226 ms

642088-boton-facebook-en.png

642088-boton-facebook-en.png

1235 ms

LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf

LeFlHvsZjXu2c3ZRgBq9nKCWcynf_cDxXwCLxiixG1c.ttf

27 ms

eCpfeMZI7q4jLksXVRWPQy3USBnSvpkopQaUR-2r7iU.ttf

eCpfeMZI7q4jLksXVRWPQy3USBnSvpkopQaUR-2r7iU.ttf

145 ms

www-widgetapi.js

www-widgetapi.js

122 ms

common.js

common.js

78 ms

map.js

map.js

108 ms

util.js

util.js

171 ms

marker.js

marker.js

170 ms

300lo.json

300lo.json

124 ms

counter.5524cceca805eb4b9b2b.js

counter.5524cceca805eb4b9b2b.js

49 ms

bx_loader.gif

bx_loader.gif

1057 ms

icons.woff

icons.woff

1117 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

178 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

106 ms

onion.js

onion.js

48 ms

openhand_8_8.cur

openhand_8_8.cur

110 ms

shares.json

shares.json

72 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

123 ms

stats.js

stats.js

62 ms

controls.js

controls.js

62 ms

spotlight-poi.png

spotlight-poi.png

55 ms

css

css

119 ms

transparent.png

transparent.png

94 ms

google4.png

google4.png

99 ms

mapcnt6.png

mapcnt6.png

97 ms

sv5.png

sv5.png

98 ms

vt

vt

20 ms

vt

vt

38 ms

vt

vt

14 ms

vt

vt

15 ms

vt

vt

52 ms

vt

vt

53 ms

vt

vt

53 ms

tmapctrl.png

tmapctrl.png

54 ms

cb_scout5.png

cb_scout5.png

86 ms

tmapctrl4.png

tmapctrl4.png

70 ms

imgs8.png

imgs8.png

85 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

62 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

81 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

105 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

106 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

224 ms

SEO Factors

wawabebe.com SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wawabebe.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed English language. Our system also found out that Wawabebe.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.

Social Sharing Optimization

wawabebe.com

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