Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

legocity.com

Your LEGO® City. No Limits. - LEGO® US

Page Load Speed

2.1 sec in total

First Response

50 ms

Resources Loaded

1.9 sec

Page Rendered

191 ms

legocity.com screenshot

About Website

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

Meet the daredevil LEGO® City citizens filming their efforts to create the most gravity-defying stunts ever!

Visit legocity.com

Key Findings

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

Performance Metrics

legocity.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value3,710 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value21.4 s

1/100

10%

Network Requests Diagram

legocity.com

50 ms

kids-city

309 ms

polyfills-c67a75d1b6f99dc8.js

379 ms

webpack-b5c9f9d2678f0cf3.js

521 ms

framework-2d1b4be3204c8e00.js

519 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Legocity.com, 71% (12 requests) were made to Lego.com and 24% (4 requests) were made to Assets.lego.com. The less responsive or slowest element that took the longest time to load (582 ms) relates to the external source Lego.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 177.2 kB (81%)

Content Size

219.1 kB

After Optimization

41.8 kB

In fact, the total size of Legocity.com main page is 219.1 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. 65% of websites need less resources to load. HTML takes 211.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 175.9 kB

  • Original 211.4 kB
  • After minification 211.4 kB
  • After compression 35.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 175.9 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 276 B

  • Original 2.4 kB
  • After minification 2.1 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, LEGO City needs image optimization as it can save up to 276 B or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 1.1 kB

  • Original 5.3 kB
  • After minification 5.3 kB
  • After compression 4.2 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 1.1 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (82%)

Requests Now

11

After Optimization

2

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEGO City. 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 as a result speed up the page load time.

Accessibility Review

legocity.com accessibility score

100

Accessibility Issues

Best Practices

legocity.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

legocity.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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 Legocity.com 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 Legocity.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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: