4.1 sec in total
94 ms
3.8 sec
258 ms
Visit whatwasthere.com now to see the best up-to-date Whatwasthere content for United States and also check out these interesting facts you probably never knew about whatwasthere.com
WhatWasThere ties historical photos to Google Maps, allowing you to tour familiar streets to see how they appeared in the past.
Visit whatwasthere.comWe analyzed Whatwasthere.com page load time and found that the first response time was 94 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
whatwasthere.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value7.0 s
6/100
25%
Value4.8 s
67/100
10%
Value700 ms
43/100
30%
Value0.171
70/100
15%
Value8.4 s
39/100
10%
94 ms
129 ms
392 ms
66 ms
197 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 34% of them (37 requests) were addressed to the original Whatwasthere.com, 43% (46 requests) were made to Maps.googleapis.com and 6% (6 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Whatwasthere.com.
Page size can be reduced by 472.7 kB (27%)
1.7 MB
1.3 MB
In fact, the total size of Whatwasthere.com main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 49.7 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 49.7 kB or 83% of the original size.
Potential reduce by 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. Whatwasthere images are well optimized though.
Potential reduce by 390.0 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 390.0 kB or 63% of the original size.
Potential reduce by 10.1 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. Whatwasthere.com needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 71% of the original size.
Number of requests can be reduced by 27 (26%)
102
75
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatwasthere. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
whatwasthere.com
94 ms
www.whatwasthere.com
129 ms
global.min.css
392 ms
jquery.min.js
66 ms
jquery-ui-1.8.10.custom.min.js
197 ms
js
50 ms
utils.min.js
460 ms
konami.min.js
89 ms
home.min.css
98 ms
all.js
158 ms
webtrends.min.js
574 ms
topNavBg.png
52 ms
followUsH.gif
53 ms
facebookNav.png
50 ms
twitterNav.png
53 ms
iphoneIcon.png
120 ms
photoBox.png
662 ms
Photo_81541.jpg
85 ms
Photo_81540.jpg
84 ms
Photo_81539.jpg
95 ms
Photo_81538.jpg
138 ms
Photo_81537.jpg
132 ms
Photo_81536.jpg
138 ms
Photo_81535.jpg
161 ms
Photo_81534.JPG
171 ms
logo.png
253 ms
nav.png
128 ms
orangeBg.png
138 ms
blank.gif
151 ms
teaserBg.png
179 ms
makeHistoryH.gif
180 ms
uploadBtn.png
598 ms
browseTeaserTopBg.png
219 ms
browseCopy.png
597 ms
goBtn.png
611 ms
browseTeaserBottomBg.png
248 ms
theLatestH.gif
281 ms
skylineRepeatBg.png
283 ms
skyline.png
3080 ms
introText.png
657 ms
242 ms
xd_arbiter.php
145 ms
xd_arbiter.php
249 ms
wtid.js
77 ms
ga.js
24 ms
204 ms
117 ms
__utm.gif
26 ms
dcs.gif
64 ms
common.js
20 ms
map.js
40 ms
util.js
25 ms
onion.js
23 ms
openhand_8_8.cur
59 ms
like.php
234 ms
ViewportInfoService.GetViewportInfo
100 ms
stats.js
43 ms
controls.js
37 ms
transparent.png
67 ms
css
60 ms
google4.png
81 ms
mapcnt6.png
93 ms
vt
60 ms
vt
104 ms
vt
99 ms
vt
76 ms
vt
81 ms
vt
76 ms
vt
116 ms
vt
128 ms
vt
124 ms
vt
139 ms
vt
165 ms
vt
143 ms
vt
171 ms
vt
172 ms
vt
195 ms
vt
196 ms
vt
192 ms
vt
221 ms
vt
215 ms
vt
227 ms
vt
254 ms
vt
259 ms
vt
251 ms
vt
263 ms
vt
260 ms
vt
294 ms
vt
305 ms
vt
299 ms
vt
314 ms
vt
317 ms
vt
306 ms
vt
359 ms
vt
355 ms
vt
362 ms
vt
356 ms
vt
372 ms
tmapctrl.png
26 ms
tmapctrl4.png
25 ms
vpc6VNjRPXV.js
299 ms
LVx-xkvaJ0b.png
331 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
19 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
27 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
47 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
47 ms
vt
341 ms
AuthenticationService.Authenticate
14 ms
whatwasthere.com accessibility score
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
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
Form elements do not have associated labels
Links do not have a discernible name
whatwasthere.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
whatwasthere.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatwasthere.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 Whatwasthere.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.
whatwasthere.com
Open Graph description is not detected on the main page of Whatwasthere. 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: