3.8 sec in total
1.2 sec
2.1 sec
577 ms
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.comWe analyzed Yesterland.com 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 a poor result, as 50% of websites can load faster.
yesterland.com performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value2.8 s
82/100
25%
Value4.2 s
78/100
10%
Value2,050 ms
7/100
30%
Value0
100/100
15%
Value11.9 s
17/100
10%
1183 ms
931 ms
966 ms
951 ms
5 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 28% of them (16 requests) were addressed to the original Yesterland.com, 18% (10 requests) were made to Static.xx.fbcdn.net and 12% (7 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Yesterland.com.
Page size can be reduced by 61.2 kB (33%)
187.0 kB
125.7 kB
In fact, the total size of Yesterland.com main page is 187.0 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. 45% of websites need less resources to load. Images take 78.9 kB which makes up the majority of the site volume.
Potential reduce by 48.0 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 48.0 kB or 79% of the original size.
Potential reduce by 2.3 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.
Potential reduce by 10.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 10.9 kB or 23% of the original size.
Number of requests can be reduced by 27 (48%)
56
29
The browser has sent 56 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 15 to 1 for JavaScripts and as a result speed up the page load time.
yesterland.com
1183 ms
yl-bg-new.png
931 ms
neweryestersign.png
966 ms
dot.gif
951 ms
show_ads.js
5 ms
ymainstreet.gif
943 ms
ytomorrowland.gif
953 ms
yfantasyland.gif
143 ms
yfrontierland.gif
150 ms
ca-pub-4178848007043723.js
32 ms
zrt_lookup.html
31 ms
show_ads_impl.js
62 ms
ybearcountry.gif
119 ms
yneworleanssquare.gif
157 ms
yadventureland.gif
170 ms
yseasonal.gif
195 ms
ycaladventure.gif
219 ms
Logo_25wht.gif
82 ms
quant.js
72 ms
urchin.js
75 ms
werner2.gif
206 ms
i26x25g.gif
229 ms
write2yester.gif
253 ms
likebox.php
220 ms
ads
226 ms
pixel;r=1746402182;a=p-40L2YsTFRCGIM;fpan=1;fpa=P0-1307661303-1456761939268;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456761939267;tzo=-180;ref=;url=http%3A%2F%2Fyesterland.com%2F;ogl=
12 ms
__utm.gif
26 ms
osd.js
6 ms
ads
200 ms
ads
165 ms
ads
103 ms
roNeOY-tz5Y.css
186 ms
UHhaxo8Cs3k.css
220 ms
_rx8naC75Dy.js
298 ms
x5F9OMjKyLw.js
363 ms
ICDbTSzjQEg.js
297 ms
TTCre3391I0.js
322 ms
abg.js
37 ms
13573616654761589142
17 ms
s
12 ms
redir.html
58 ms
m_js_controller.js
12 ms
googlelogo_color_112x36dp.png
56 ms
x_button_blue2.png
36 ms
iframe.html
34 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
2 ms
1932450_10152279062798118_1572483910_n.jpg
60 ms
1013942_10151663663758118_1606715275_n.jpg
60 ms
11817273_111300299219249_2603395481850756769_n.jpg
59 ms
11406972_1136577159693059_5130078467198355908_n.jpg
60 ms
1619653_10203486953358648_500234925_n.jpg
61 ms
11709515_10153429459871407_3597153120550351246_n.jpg
56 ms
11221273_10203820306067225_8297576947751834030_n.jpg
60 ms
wL6VQj7Ab77.png
53 ms
s7jcwEQH7Sx.png
53 ms
I6-MnjEovm5.js
42 ms
vlXaquuXMrr.js
81 ms
yesterland.com accessibility score
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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
yesterland.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
yesterland.com SEO score
EN
N/A
N/A
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 . 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.
yesterland.com
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: