5.5 sec in total
2 sec
3.2 sec
353 ms
Click here to check amazing Discovered In Kathmandu content. Otherwise, check out these important facts you probably never knew about discoveredinkathmandu.co.uk
Visit discoveredinkathmandu.co.ukWe analyzed Discoveredinkathmandu.co.uk page load time and found that the first response time was 2 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
discoveredinkathmandu.co.uk performance score
1975 ms
10 ms
56 ms
81 ms
116 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 30% of them (27 requests) were addressed to the original Discoveredinkathmandu.co.uk, 9% (8 requests) were made to Cm.g.doubleclick.net and 7% (6 requests) were made to Px.owneriq.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Discoveredinkathmandu.co.uk.
Page size can be reduced by 1.2 MB (63%)
1.9 MB
698.0 kB
In fact, the total size of Discoveredinkathmandu.co.uk main page is 1.9 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 215.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 215.0 kB or 90% of the original size.
Potential reduce by 24.1 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. Discovered In Kathmandu images are well optimized though.
Potential reduce by 846.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 846.6 kB or 76% of the original size.
Potential reduce by 97.8 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. Discoveredinkathmandu.co.uk needs all CSS files to be minified and compressed as it can save up to 97.8 kB or 82% of the original size.
Number of requests can be reduced by 53 (73%)
73
20
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Discovered In Kathmandu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
discoveredinkathmandu.co.uk
1975 ms
shareaholic.js
10 ms
style.min.css
56 ms
style-mobile.min.css
81 ms
jquery-ui-1.10.3.custom.css
116 ms
bwg_frontend.css
122 ms
font-awesome.css
117 ms
jquery.mCustomScrollbar.css
109 ms
jquery.js
188 ms
jquery-migrate.min.js
126 ms
bwg_frontend.js
162 ms
jquery.mCustomScrollbar.concat.min.js
168 ms
jquery.fullscreen-0.4.1.js
176 ms
bwg_gallery_box.js
177 ms
weaverjslib.min.js
208 ms
devicepx-jetpack.js
7 ms
jquery.ui.core.min.js
239 ms
jquery.ui.widget.min.js
239 ms
jquery.ui.position.min.js
242 ms
jquery.ui.tooltip.min.js
242 ms
4418f074ba6f9f7f64e4efb37a1c02db.json
139 ms
gr.png
59 ms
header1.jpg
249 ms
image-5-300x225.jpg
245 ms
image-8-300x225.jpg
246 ms
15.jpg
451 ms
BUY-BOOK-NOW.gif
246 ms
BUY-THE-BOOK-FROM-AMAZON1.gif
121 ms
facebook-logo1.jpg
246 ms
search_button.gif
247 ms
shrMain.min.js
15 ms
jquery.min.js
57 ms
analytics.js
99 ms
pageview.gif
44 ms
app.js
10 ms
vglnk.js
26 ms
partners.js
45 ms
angular.min.js
35 ms
pixel.gif
9 ms
pixel.gif
7 ms
sholic.js
7 ms
usermatch
112 ms
beacon.js
34 ms
cms-sh2c.html
111 ms
eexelate.js
27 ms
27 ms
sharing-caring.png
42 ms
usermatch
43 ms
ping_match.gif
33 ms
ep
34 ms
ep
30 ms
2964
20 ms
gr
151 ms
casale
151 ms
175 ms
pixel
220 ms
i.gif
219 ms
blank.html
168 ms
pixel
109 ms
103 ms
shareaholic-icons.woff
25 ms
pixel
207 ms
graph.facebook.com
227 ms
count.json
168 ms
rs
58 ms
pixel
84 ms
crum
142 ms
net.php
39 ms
pixel
113 ms
casale
29 ms
cfcm.ashx
28 ms
generic
78 ms
pixel
50 ms
crum
88 ms
pixelssl.htm
130 ms
cse
307 ms
pixel
80 ms
pixel
77 ms
m
51 ms
xrefid.xgi
13 ms
match-result
41 ms
crum
24 ms
pixel.gif
9 ms
pixel.gif
7 ms
crum
15 ms
ddcssl.htm
145 ms
ping
31 ms
ermcm
7 ms
xrefid.xgi
7 ms
domains
57 ms
crum
10 ms
discoveredinkathmandu.co.uk SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discoveredinkathmandu.co.uk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Discoveredinkathmandu.co.uk 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.
discoveredinkathmandu.co.uk
Open Graph description is not detected on the main page of Discovered In Kathmandu. 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: