Tools & Wizards About Us
getlego.me screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

getlego.me

레고 공홈 가격비교 - 2015100201

Page Load Speed

3.8 sec in total

First Response

1.2 sec

Resources Loaded

2.4 sec

Page Rendered

259 ms

getlego.me screenshot

About Website

Welcome to getlego.me homepage info - get ready to check Getlego best content right away, or after learning these important things about getlego.me

전세계 레고 공식 홈페이지의 가격비교, 많이 찾는 상품, 품절 등의 상태를 비교해보세요.

Visit getlego.me

Key Findings

We analyzed Getlego.me page load time and found that the first response time was 1.2 sec and then it took 2.6 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

getlego.me performance score

0

Network Requests Diagram

getlego.me

1222 ms

angular.js

18 ms

ui-bootstrap-tpls-0.13.0.js

42 ms

Chart.js

221 ms

angular-chart.js

233 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 8% of them (7 requests) were addressed to the original Getlego.me, 18% (15 requests) were made to Static.xx.fbcdn.net and 12% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Getlego.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 296.5 kB (13%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Getlego.me main page is 2.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.4 kB

  • Original 47.9 kB
  • After minification 40.1 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 7.8 kB, which is 16% 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 38.4 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 29.7 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. Getlego images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 145.2 kB

  • Original 251.6 kB
  • After minification 207.7 kB
  • After compression 106.5 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 145.2 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 83.3 kB

  • Original 100.7 kB
  • After minification 100.6 kB
  • After compression 17.5 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. Getlego.me needs all CSS files to be minified and compressed as it can save up to 83.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (56%)

Requests Now

79

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

getlego.me

getlego.me

1222 ms

angular.js

angular.js

18 ms

ui-bootstrap-tpls-0.13.0.js

ui-bootstrap-tpls-0.13.0.js

42 ms

Chart.js

Chart.js

221 ms

angular-chart.js

angular-chart.js

233 ms

home.js

home.js

231 ms

bootstrap.min.css

bootstrap.min.css

38 ms

angular-chart.css

angular-chart.css

239 ms

q

q

38 ms

adsbygoogle.js

adsbygoogle.js

36 ms

8005.js

8005.js

9 ms

popup.js

popup.js

4 ms

nifty.js

nifty.js

5 ms

colors.js

colors.js

7 ms

shop.png

shop.png

206 ms

ir

ir

12 ms

analytics.js

analytics.js

11 ms

sdk.js

sdk.js

9 ms

collect

collect

101 ms

ca-pub-2621045516895847.js

ca-pub-2621045516895847.js

190 ms

zrt_lookup.html

zrt_lookup.html

166 ms

show_ads_impl.js

show_ads_impl.js

106 ms

ad.json

ad.json

185 ms

list

list

286 ms

collect

collect

118 ms

126 ms

collect

collect

56 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

57 ms

ads

ads

232 ms

xd_arbiter.php

xd_arbiter.php

44 ms

xd_arbiter.php

xd_arbiter.php

58 ms

osd.js

osd.js

40 ms

ga-audiences

ga-audiences

42 ms

page.php

page.php

175 ms

8285636830827455167

8285636830827455167

66 ms

abg.js

abg.js

55 ms

m_js_controller.js

m_js_controller.js

68 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

66 ms

collect

collect

33 ms

Creator2015_305x40_Logo.png

Creator2015_305x40_Logo.png

56 ms

ir

ir

23 ms

10251

10251

78 ms

Simpsons_305x40_Logo.png

Simpsons_305x40_Logo.png

51 ms

71016

71016

243 ms

creator.jpg

creator.jpg

87 ms

10246

10246

79 ms

71006

71006

84 ms

starwars.jpg

starwars.jpg

68 ms

75059

75059

243 ms

10214

10214

246 ms

ir

ir

17 ms

ir

ir

17 ms

ir

ir

18 ms

ir

ir

30 ms

ir

ir

30 ms

LUdypCgtRlc.css

LUdypCgtRlc.css

72 ms

Hy2B8ciSPhU.css

Hy2B8ciSPhU.css

81 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

85 ms

YvxwM8R7ol8.js

YvxwM8R7ol8.js

99 ms

ihptErjAmMX.js

ihptErjAmMX.js

127 ms

1BQnIVjTFoC.js

1BQnIVjTFoC.js

128 ms

6PDLJFN-l6_.js

6PDLJFN-l6_.js

135 ms

cUsKAwzqrQw.js

cUsKAwzqrQw.js

141 ms

x_button_blue2.png

x_button_blue2.png

27 ms

s

s

23 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

31 ms

12717613_425880070942589_7663182627622832813_n.jpg

12717613_425880070942589_7663182627622832813_n.jpg

149 ms

12744419_425880017609261_3887662358619443876_n.jpg

12744419_425880017609261_3887662358619443876_n.jpg

16 ms

10168216_676481429075928_432582107_n.jpg

10168216_676481429075928_432582107_n.jpg

36 ms

12107901_786435951467462_7399780149195074351_n.jpg

12107901_786435951467462_7399780149195074351_n.jpg

18 ms

10314459_1028777777186820_5706062565833011940_n.jpg

10314459_1028777777186820_5706062565833011940_n.jpg

144 ms

12400975_968404616566560_3450618265334735922_n.jpg

12400975_968404616566560_3450618265334735922_n.jpg

17 ms

10409707_792482330819308_5593222804976717266_n.jpg

10409707_792482330819308_5593222804976717266_n.jpg

80 ms

10246256_829878867052397_4530372890638750436_n.jpg

10246256_829878867052397_4530372890638750436_n.jpg

94 ms

11377209_822772267805563_9026704830340138263_n.jpg

11377209_822772267805563_9026704830340138263_n.jpg

67 ms

12540536_1541127889542081_8100956839329499184_n.jpg

12540536_1541127889542081_8100956839329499184_n.jpg

37 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

14 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

13 ms

6GqoI2ZyIrf.png

6GqoI2ZyIrf.png

15 ms

R9a_DtVRZgv.js

R9a_DtVRZgv.js

13 ms

cUDgRFxaoIk.js

cUDgRFxaoIk.js

10 ms

0JBr1QHp8Gi.js

0JBr1QHp8Gi.js

11 ms

kDOzhTr2W91.js

kDOzhTr2W91.js

10 ms

ui

ui

15 ms

SEO Factors

getlego.me SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

getlego.me

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