4.2 sec in total
302 ms
3.3 sec
659 ms
Visit iwantsomewhere.com now to see the best up-to-date Iwantsomewhere content for United States and also check out these interesting facts you probably never knew about iwantsomewhere.com
Foursquare finds special places. Create your wish list and enter to win at IWantSomewhere.com.
Visit iwantsomewhere.comWe analyzed Iwantsomewhere.com page load time and found that the first response time was 302 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
iwantsomewhere.com performance score
302 ms
69 ms
487 ms
160 ms
82 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 19% of them (10 requests) were addressed to the original Iwantsomewhere.com, 63% (34 requests) were made to Dear-foursquare.s3.amazonaws.com and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Dear-foursquare.s3.amazonaws.com.
Page size can be reduced by 1.9 MB (13%)
15.0 MB
13.1 MB
In fact, the total size of Iwantsomewhere.com main page is 15.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 14.1 MB which makes up the majority of the site volume.
Potential reduce by 51.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. 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 51.5 kB or 83% of the original size.
Potential reduce by 1.3 MB
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. Iwantsomewhere images are well optimized though.
Potential reduce by 385.6 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 385.6 kB or 59% of the original size.
Potential reduce by 194.3 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. Iwantsomewhere.com needs all CSS files to be minified and compressed as it can save up to 194.3 kB or 85% of the original size.
Number of requests can be reduced by 6 (12%)
49
43
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iwantsomewhere. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
iwantsomewhere.com
302 ms
css
69 ms
application-9057889d8ec8442b0f855a6d0bcad364.css
487 ms
header_scripts-b8c06597bf53f14ca229120189084ffe.js
160 ms
js
82 ms
footer_scripts-f30c2342ca40b60ec53d1e74cac91f02.js
627 ms
20151224115943.jpg
804 ms
12-25.png
709 ms
20151220150143.jpg
1041 ms
12-20.png
700 ms
20151219193740.jpg
1120 ms
12-19.png
744 ms
20151218142653.jpg
1305 ms
12-18.png
1088 ms
20151218011050.jpg
1298 ms
12-21.png
1060 ms
20151217120810.jpg
1503 ms
12-17.png
1265 ms
20151213215932.jpg
1546 ms
12-13.png
1430 ms
20151212235037.jpg
1550 ms
12-14.png
1596 ms
20151212171254.jpg
1684 ms
12-12.png
1714 ms
20151212140027.jpg
1876 ms
12-22.png
1832 ms
20151212054924.jpg
1816 ms
12-15.png
1809 ms
20151211173556.jpg
1974 ms
Screen_Shot_2015-12-12_at_5.36.27_PM.png
2005 ms
20151210001928.jpg
2099 ms
12-16.png
2030 ms
20151209155158.jpg
2187 ms
Screen_Shot_2015-12-11_at_1.25.31_PM.png
2081 ms
20151208190249.jpg
2270 ms
12-8.png
2224 ms
20151207185217.jpg
2237 ms
12-7.jpg
2282 ms
20151207170738.jpg
2420 ms
Screen_Shot_2015-12-10_at_2.03.02_PM.png
2387 ms
window.png
407 ms
logo.png
142 ms
preloader.png
144 ms
background-letter.jpg
538 ms
window-bg.jpg
632 ms
analytics.js
27 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
20 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
26 ms
9-wW4zu3WNoD5Fjka35JmybsRidxnYrfzLNRqJkHfFo.ttf
44 ms
fontawesome-webfont.woff
382 ms
collect
76 ms
common.js
33 ms
util.js
46 ms
geocoder.js
47 ms
iwantsomewhere.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iwantsomewhere.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 Iwantsomewhere.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.
iwantsomewhere.com
Open Graph data is detected on the main page of Iwantsomewhere. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: