Tools & Wizards About Us
search-ko.lego.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

search-ko.lego.com

LEGO.com Search Results

Page Load Speed

1.9 sec in total

First Response

598 ms

Resources Loaded

1.2 sec

Page Rendered

95 ms

search-ko.lego.com screenshot

About Website

Click here to check amazing Search Ko LEGO content for United States. Otherwise, check out these important facts you probably never knew about search-ko.lego.com

Visit search-ko.lego.com

Key Findings

We analyzed Search-ko.lego.com page load time and found that the first response time was 598 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

search-ko.lego.com performance score

0

Network Requests Diagram

search-ko.lego.com

598 ms

jquery.min.js

29 ms

jquery-ui.min.js

46 ms

reset.css

231 ms

font-face-sansa.css

22 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Search-ko.lego.com, 55% (29 requests) were made to Cache.lego.com and 13% (7 requests) were made to A248.e.akamai.net. The less responsive or slowest element that took the longest time to load (598 ms) belongs to the original domain Search-ko.lego.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.9 kB (66%)

Content Size

393.2 kB

After Optimization

132.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Search-ko.lego.com main page is 393.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 188.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 23.7 kB

  • Original 31.3 kB
  • After minification 24.3 kB
  • After compression 7.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 6.9 kB, which is 22% 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 23.7 kB or 76% of the original size.

Image Optimization

-32%

Potential reduce by 10.8 kB

  • Original 33.7 kB
  • After minification 22.9 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, Search Ko LEGO needs image optimization as it can save up to 10.8 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 105.9 kB

  • Original 188.6 kB
  • After minification 178.7 kB
  • After compression 82.6 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 105.9 kB or 56% of the original size.

CSS Optimization

-86%

Potential reduce by 120.4 kB

  • Original 139.6 kB
  • After minification 112.6 kB
  • After compression 19.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. Search-ko.lego.com needs all CSS files to be minified and compressed as it can save up to 120.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (45%)

Requests Now

40

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

search-ko.lego.com

search-ko.lego.com

598 ms

jquery.min.js

jquery.min.js

29 ms

jquery-ui.min.js

jquery-ui.min.js

46 ms

reset.css

reset.css

231 ms

font-face-sansa.css

font-face-sansa.css

22 ms

lego-shop-base.css

lego-shop-base.css

240 ms

lego-shop-global-buttons.css

lego-shop-global-buttons.css

238 ms

lego_search_styles_kr.css

lego_search_styles_kr.css

190 ms

product-listing.css

product-listing.css

235 ms

lego_search_styles2.css

lego_search_styles2.css

37 ms

jquery.colorbox.js

jquery.colorbox.js

36 ms

colorbox-core.css

colorbox-core.css

36 ms

colorbox-presentation.css

colorbox-presentation.css

35 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

218 ms

foresee-trigger.js

foresee-trigger.js

7 ms

shop-search

shop-search

34 ms

default.aspx

default.aspx

43 ms

HeaderFooter.aspx

HeaderFooter.aspx

74 ms

shop-search

shop-search

44 ms

Search_KO.png

Search_KO.png

50 ms

top_search_submit.jpg

top_search_submit.jpg

18 ms

shop-search

shop-search

43 ms

top_search_bg.jpg

top_search_bg.jpg

22 ms

tab_bg_new.jpg

tab_bg_new.jpg

23 ms

tab_on_bg_new.jpg

tab_on_bg_new.jpg

24 ms

tab_on_left_cap_shop.jpg

tab_on_left_cap_shop.jpg

22 ms

tab_off_bg_new.jpg

tab_off_bg_new.jpg

22 ms

tab_left_cap_products.jpg

tab_left_cap_products.jpg

23 ms

search_main_bg_new.jpg

search_main_bg_new.jpg

24 ms

results_viewport_top_new.jpg

results_viewport_top_new.jpg

25 ms

195 ms

bg-arrow-down.png

bg-arrow-down.png

89 ms

results_viewport_btm_new.jpg

results_viewport_btm_new.jpg

45 ms

bg-product-thumb.png

bg-product-thumb.png

88 ms

reviews-bricks.png

reviews-bricks.png

105 ms

sansasoft-normal-webfont.woff

sansasoft-normal-webfont.woff

100 ms

sansasoft-semibold-webfont.woff

sansasoft-semibold-webfont.woff

98 ms

LEGOUserStats.1.js.ashx

LEGOUserStats.1.js.ashx

151 ms

sansasoft-bold-webfont.woff

sansasoft-bold-webfont.woff

90 ms

shop-search

shop-search

56 ms

shop-search

shop-search

189 ms

lego-logo-menu.svg

lego-logo-menu.svg

44 ms

global-nav-sprite.svg

global-nav-sprite.svg

21 ms

ubuntu-b.woff

ubuntu-b.woff

17 ms

ubuntu-m.woff

ubuntu-m.woff

18 ms

ubuntu-r.woff

ubuntu-r.woff

18 ms

ubuntu-l.woff

ubuntu-l.woff

16 ms

LEGOSiteStats.1.js.ashx

LEGOSiteStats.1.js.ashx

141 ms

modalCollection.png

modalCollection.png

4 ms

foresee-surveydef.js

foresee-surveydef.js

100 ms

lego.id.api.js

lego.id.api.js

142 ms

LegalTextService.ashx

LegalTextService.ashx

50 ms

s52408956610597

s52408956610597

10 ms

SEO Factors

search-ko.lego.com SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search-ko.lego.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Search-ko.lego.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

search-ko.lego.com

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