5.5 sec in total
637 ms
4.3 sec
524 ms
Welcome to fossick.com homepage info - get ready to check Fossick best content right away, or after learning these important things about fossick.com
Independent accommodation reviews - discover great places to stay in Australia or New Zealand through our independent reviews, large maps and loads of filters.
Visit fossick.comWe analyzed Fossick.com page load time and found that the first response time was 637 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fossick.com performance score
637 ms
522 ms
505 ms
691 ms
976 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Fossick.com, 19% (23 requests) were made to Maps.google.com and 15% (18 requests) were made to Asset1.www.fossick.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Asset0.www.fossick.com.
Page size can be reduced by 755.6 kB (31%)
2.4 MB
1.7 MB
In fact, the total size of Fossick.com main page is 2.4 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 97.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 97.9 kB or 83% of the original size.
Potential reduce by 52.5 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. Fossick images are well optimized though.
Potential reduce by 474.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 474.0 kB or 66% of the original size.
Potential reduce by 131.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. Fossick.com needs all CSS files to be minified and compressed as it can save up to 131.3 kB or 82% of the original size.
Number of requests can be reduced by 33 (30%)
110
77
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fossick. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
fossick.com
637 ms
www.fossick.com
522 ms
head.load.min-820e974f46789d6994be60de00e8fedb.js
505 ms
application-14c2865df15256f764f6f42a2afda6b7.css
691 ms
application-f0a132c08a9908269b15ac89b8b0401b.js
976 ms
js
33 ms
homepage.js
549 ms
homepage.js
410 ms
ga.js
73 ms
bg_body2-1ca72fcff26ea3712ff38c4c87b08c07.png
233 ms
btn-small-claimfreelisting-3b8207cc7cae711889d3a2e2aad4265d.png
233 ms
header-related-logo-wotif-9f26e748c457ec07f2ac28a4702bda34.png
232 ms
header-related-logo-bookingcom-2276463a1cd8db95c02b9301cbc2c434.png
230 ms
header-related-logo-travelbug-ead193d777d4aea940b607e4cff40c2d.png
532 ms
header-related-logo-hotelscombined-48c902ed1e8c183332fb036ff872e159.png
532 ms
header-related-logo-vroom-8b7e4e3630a0c7c923103201b0b97553.png
530 ms
header-related-logo-worldnomads-579e51550c1b7b60f813c7b650b01f18.png
538 ms
image-rotorua.png
1016 ms
icon-facebook-c9c355f27423cbab959208c75c6a6e5a.png
528 ms
fossick-logo-34d44f2c1d63c4ce216167aebfbf01b1.png
529 ms
btn-small-login-6c88315f34a4867c4a6634a9cb641a17.png
528 ms
home-getstarted-button-search-3682d4f7f2fa0eb24735e29f3e3f5859.png
527 ms
icon-twitter-9ed321f84aa2d57b515cf8bb27b318f3.png
528 ms
all.js
111 ms
hd_nav-h3-bg-921aa4aba3a404e22df4d33dd84b3fea.png
756 ms
bg_nav-level2-expanded-f9ace31887c90deace61b20c709d9b99.png
476 ms
bg_nav-level2-collapsed-531dec7c41acebab4bab786e3c7270ec.png
477 ms
hd_nav-li-bg-8300f8d1c29b2d956c3a8c7d99459cbe.png
693 ms
bg-head-nav-submenu-about-social-8a82e4acc5898bdb37b2cfc715d38652.png
683 ms
home-getstart-heading-bg-ea00200bad082887a3c10bbbe04f5ede.png
688 ms
bg-head-nav-submenu-bg-4faf22dda10efaf3fbb0ceddd4a60d7b.jpg
795 ms
home-getstarted-bg-2e8e51d1fb79e0f288c233200cf735bc.png
488 ms
bg_header-about2-59f05798d44038a678a51958c070e55c.png
680 ms
bg_nav-level2-overlay-sp-27e23322ad299846572d815b636df707.png
485 ms
bg_header3-b82498f41eb07f02bc1111a02e60f968.jpg
679 ms
bg_nav-level2-overlay-nz-bb3597b6a6a34d5d99dc434445cf2d2b.png
486 ms
bg_nav-level2-overlay-au-954c4a46d5ce091b380f08ede717df6c.png
682 ms
bg-head-nav-submenu-business-i8a8-48396a87cddf476409619ef5cba514a3.png
879 ms
chunkfive-webfont-2e1b3d2c6bb5df311633de9c5903c9ba.woff
627 ms
home-getstarted-button-writeareview-8dca4a59e34b5dd5b3b87bb6fe08087d.png
625 ms
icon-add-reviews-dee355151fe156599d65179e1cb3000b.png
626 ms
icon-contribute-84451f11a5392de87c6c717a1c6aae78.png
812 ms
bg-wood-7e40f0199ed909191a98e6b3e62e8511.png
955 ms
bg-latest-reviews-88be91212b8695889f27c98465cac977.png
1950 ms
page-clip-baf32a499b100d1cc6d17ca7c80f9f2b.png
528 ms
bg-how-it-works-a84c13387f8050852b6913ac920c20bf.png
1527 ms
icon-search-locations-3d2c449f804e67ebeb47bad285c3a0fc.png
731 ms
free-to-list-tag-b31cb14e5042e99abc45f1cfc94b7713.png
1515 ms
footer-images-f91661e57347af30e8e1450cdfefcb97.png
1169 ms
win_green_box-ab83b5d30cd68f4669e5667ebd4b6b08.png
413 ms
home-getstarted-browse-label-bg-8d7c9d3045eb230243e430b0ab633cb5.png
610 ms
icon-maps-a9a9689f7cf90d6e8ecd9652f4bc8107.png
612 ms
tape-546f69a7aee650b0eacada6508815ef3.png
730 ms
__utm.gif
48 ms
306 ms
common.js
144 ms
map.js
144 ms
__utm.gif
138 ms
xd_arbiter.php
207 ms
xd_arbiter.php
375 ms
header-related-icon-arrow-right-be652dc6a78d3c57a2ccde33dd03f765.png
672 ms
header-related-recommend-groups-bg-9b142274e7ffc9d60d82b21e217f429c.png
396 ms
util.js
94 ms
onion.js
94 ms
openhand_8_8.cur
84 ms
ViewportInfoService.GetViewportInfo
169 ms
stats.js
53 ms
kh
56 ms
kh
53 ms
controls.js
34 ms
transparent.png
130 ms
kh
128 ms
kh
133 ms
kh
136 ms
kh
126 ms
kh
124 ms
kh
139 ms
kh
126 ms
kh
125 ms
kh
126 ms
kh
133 ms
kh
127 ms
kh
138 ms
css
91 ms
like.php
180 ms
google4.png
78 ms
marker.js
72 ms
mapcnt6.png
126 ms
sv5.png
127 ms
vt
108 ms
qeKvIRsJabD.js
205 ms
vt
91 ms
vt
89 ms
vt
87 ms
vt
89 ms
vt
89 ms
vt
90 ms
vt
99 ms
vt
97 ms
vt
93 ms
vt
102 ms
vt
115 ms
vt
98 ms
vt
99 ms
tmapctrl.png
86 ms
cb_scout5.png
86 ms
tmapctrl4.png
81 ms
imgs8.png
82 ms
google_white5.png
81 ms
LVx-xkvaJ0b.png
162 ms
vt
112 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
63 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
78 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
78 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
78 ms
AuthenticationService.Authenticate
52 ms
__utm.gif
4 ms
nr-100.js
43 ms
fossick.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 Fossick.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 Fossick.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.
fossick.com
Open Graph description is not detected on the main page of Fossick. 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: