Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

yesterland.com

Yesterland - Disneyland History & Other Disney Park History

Page Load Speed

1.1 sec in total

First Response

74 ms

Resources Loaded

532 ms

Page Rendered

505 ms

yesterland.com screenshot

About Website

Visit yesterland.com now to see the best up-to-date Yesterland content for United States and also check out these interesting facts you probably never knew about yesterland.com

Yesterland, a Theme Park on the Web, featuring Discontinued Disneyland Attractions

Visit yesterland.com

Key Findings

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

Performance Metrics

yesterland.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value370 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

yesterland.com

74 ms

yesterland.com

224 ms

gppstub.js

159 ms

boise.js

154 ms

abilene.js

185 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 44% of them (15 requests) were addressed to the original Yesterland.com, 26% (9 requests) were made to Ezojs.com and 6% (2 requests) were made to The.gatekeeperconsent.com. The less responsive or slowest element that took the longest time to load (224 ms) belongs to the original domain Yesterland.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.4 kB (50%)

Content Size

171.8 kB

After Optimization

86.4 kB

In fact, the total size of Yesterland.com main page is 171.8 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. HTML takes 94.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 71.1 kB

  • Original 94.0 kB
  • After minification 90.3 kB
  • After compression 22.9 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 71.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 111 B

  • Original 23.1 kB
  • After minification 23.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. Yesterland images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 14.2 kB

  • Original 54.7 kB
  • After minification 54.7 kB
  • After compression 40.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 14.2 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (72%)

Requests Now

32

After Optimization

9

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

Accessibility Review

yesterland.com accessibility score

80

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

Best Practices

yesterland.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

yesterland.com SEO score

79

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yesterland.com 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 Yesterland.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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