Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

kansascity.legolanddiscoverycenter.com

Top Kid's Attraction | LEGOLAND Discovery Center Kansas City

Page Load Speed

4.6 sec in total

First Response

853 ms

Resources Loaded

3.1 sec

Page Rendered

554 ms

kansascity.legolanddiscoverycenter.com screenshot

About Website

Visit kansascity.legolanddiscoverycenter.com now to see the best up-to-date Kansas City LEGOLAND Discovery Center content for United States and also check out these interesting facts you probably never knew about kansascity.legolanddiscoverycenter.com

Play & Save all summer long with prices starting at $16.99. LEGOLAND Discovery Center Kansas City, at Crown Center is the ultimate indoor LEGO® playground. We have rides, LEGO® build & play zones, a 4...

Visit kansascity.legolanddiscoverycenter.com

Key Findings

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

Performance Metrics

kansascity.legolanddiscoverycenter.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

853 ms

gtm.js

75 ms

j.php

35 ms

lazysizes.min.-v-2.0.0-hotfix.5063-v.js

41 ms

style.-v-2.0.0-hotfix.5063-v.css

954 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Kansascity.legolanddiscoverycenter.com, 14% (6 requests) were made to Unpkg.com and 5% (2 requests) were made to Me-ldkansas.na.tickets.legolanddiscoverycenter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Legolanddiscoverycenter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.8 kB (42%)

Content Size

524.2 kB

After Optimization

303.4 kB

In fact, the total size of Kansascity.legolanddiscoverycenter.com main page is 524.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. 40% of websites need less resources to load. Javascripts take 199.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 166.3 kB

  • Original 193.8 kB
  • After minification 151.2 kB
  • After compression 27.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 42.6 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 166.3 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 4.0 kB

  • Original 43.0 kB
  • After minification 39.0 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. Kansas City LEGOLAND Discovery Center images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 28.8 kB

  • Original 199.7 kB
  • After minification 199.7 kB
  • After compression 170.9 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 28.8 kB or 14% of the original size.

CSS Optimization

-25%

Potential reduce by 21.6 kB

  • Original 87.7 kB
  • After minification 87.7 kB
  • After compression 66.0 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. Kansascity.legolanddiscoverycenter.com needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (55%)

Requests Now

31

After Optimization

14

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

Accessibility Review

kansascity.legolanddiscoverycenter.com accessibility score

89

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best Practices

kansascity.legolanddiscoverycenter.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

kansascity.legolanddiscoverycenter.com SEO score

74

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Kansascity.legolanddiscoverycenter.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 Kansascity.legolanddiscoverycenter.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 Kansas City LEGOLAND Discovery Center. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: