1.5 sec in total
76 ms
1.3 sec
165 ms
Click here to check amazing Hey Whats That content for United States. Otherwise, check out these important facts you probably never knew about heywhatsthat.com
Compute summits visible from any location worldwide
Visit heywhatsthat.comWe analyzed Heywhatsthat.com page load time and found that the first response time was 76 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
heywhatsthat.com performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value10.5 s
0/100
25%
Value10.7 s
7/100
10%
Value4,100 ms
1/100
30%
Value0.678
8/100
15%
Value19.5 s
2/100
10%
76 ms
114 ms
20 ms
46 ms
58 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 24% of them (27 requests) were addressed to the original Heywhatsthat.com, 27% (31 requests) were made to Maps.google.com and 7% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (375 ms) relates to the external source Twitter-badges.s3.amazonaws.com.
Page size can be reduced by 569.1 kB (49%)
1.2 MB
602.5 kB
In fact, the total size of Heywhatsthat.com main page is 1.2 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. 65% of websites need less resources to load. Javascripts take 657.9 kB which makes up the majority of the site volume.
Potential reduce by 110.2 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 110.2 kB or 77% of the original size.
Potential reduce by 21.2 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. Hey Whats That images are well optimized though.
Potential reduce by 437.7 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 437.7 kB or 67% of the original size.
Number of requests can be reduced by 60 (56%)
108
48
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hey Whats That. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and as a result speed up the page load time.
heywhatsthat.com
76 ms
www.heywhatsthat.com
114 ms
js
20 ms
utils-angle-request6.js
46 ms
mapcontrols.js
58 ms
show_ads.js
5 ms
ga.js
55 ms
plusone.js
139 ms
t_mini-a.png
375 ms
ca-pub-2630458079197795.js
115 ms
zrt_lookup.html
105 ms
show_ads_impl.js
59 ms
hwt-logo-293-58.jpg
50 ms
dollarsign.png
51 ms
leftarrow.png
105 ms
rightarrow.png
104 ms
__utm.gif
70 ms
ads
186 ms
osd.js
12 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_1
29 ms
fastbutton
87 ms
like.php
203 ms
postmessageRelay
65 ms
cb=gapi.loaded_0
20 ms
cb=gapi.loaded_1
18 ms
3193398744-postmessagerelay.js
36 ms
rpc:shindig_random.js
44 ms
cb=gapi.loaded_0
4 ms
0_z1Bt97DI.jpg
127 ms
a.gif
54 ms
bcs0
51 ms
creative_add_on.js
148 ms
qeKvIRsJabD.js
295 ms
LVx-xkvaJ0b.png
352 ms
surly.js
47 ms
dvtp_src.js
39 ms
ba.html
14 ms
dvtp_src_internal26.js
14 ms
4.gif
55 ms
2532.js
51 ms
t2tv7.html
55 ms
visit.js
49 ms
avs583.js
5 ms
query.js
47 ms
event.jpg
49 ms
query.js
66 ms
box_19_top-right.png
42 ms
ci.png
34 ms
common.js
30 ms
map.js
28 ms
util.js
54 ms
marker.js
21 ms
points.cgi
54 ms
result.json
136 ms
get-data.cgi
53 ms
lclpsd-blue.png
49 ms
event.gif
49 ms
onion.js
30 ms
ViewportInfoService.GetViewportInfo
44 ms
stats.js
16 ms
controls.js
11 ms
transparent.png
44 ms
css
42 ms
infowindow.js
28 ms
google4.png
59 ms
mapcnt6.png
60 ms
sv5.png
59 ms
overlay.js
44 ms
cloakmN43W069.png
26 ms
cloakmN43W070.png
46 ms
cloakmN44W069.png
46 ms
cloakmN44W070.png
68 ms
image0.png
45 ms
image1.png
46 ms
image2.png
71 ms
image3.png
71 ms
image4.png
71 ms
image5.png
72 ms
image6.png
85 ms
image7.png
89 ms
profile-click.png
88 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
13 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
29 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
30 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
30 ms
tmapctrl.png
27 ms
cb_scout5.png
30 ms
tmapctrl4.png
29 ms
imgs8.png
29 ms
ViewportInfoService.GetViewportInfo
39 ms
orchid-x.png
47 ms
summit.png
47 ms
vt
11 ms
vt
11 ms
vt
9 ms
vt
11 ms
vt
10 ms
vt
11 ms
vt
10 ms
vt
14 ms
vt
13 ms
vt
13 ms
vt
13 ms
vt
13 ms
vt
14 ms
vt
16 ms
vt
15 ms
vt
18 ms
vt
16 ms
vt
17 ms
vt
17 ms
vt
18 ms
vt
14 ms
heywhatsthat.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
heywhatsthat.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
heywhatsthat.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heywhatsthat.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 Heywhatsthat.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.
heywhatsthat.com
Open Graph description is not detected on the main page of Hey Whats That. 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: