3.7 sec in total
363 ms
3.1 sec
239 ms
Visit viewedinburgh.co.uk now to see the best up-to-date Viewedinburgh content and also check out these interesting facts you probably never knew about viewedinburgh.co.uk
Your local guide to Edinburgh, with reviews and recommendations for the best pubs and bars, restaurants, clubs, hotels, cinemas and what's on and offers in Edinburgh
Visit viewedinburgh.co.ukWe analyzed Viewedinburgh.co.uk page load time and found that the first response time was 363 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
viewedinburgh.co.uk performance score
363 ms
152 ms
115 ms
23 ms
49 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Viewedinburgh.co.uk, 19% (14 requests) were made to Cf.thumb-media.eu.viewcdn.com and 5% (4 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Api.keen.io.
Page size can be reduced by 554.6 kB (68%)
815.1 kB
260.5 kB
In fact, the total size of Viewedinburgh.co.uk main page is 815.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 491.8 kB which makes up the majority of the site volume.
Potential reduce by 100.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 100.9 kB or 84% of the original size.
Potential reduce by 2.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. Viewedinburgh images are well optimized though.
Potential reduce by 332.4 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 332.4 kB or 68% of the original size.
Potential reduce by 118.5 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. Viewedinburgh.co.uk needs all CSS files to be minified and compressed as it can save up to 118.5 kB or 89% of the original size.
Number of requests can be reduced by 43 (60%)
72
29
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viewedinburgh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
edinburgh
363 ms
keen.min.js
152 ms
client:platform.js
115 ms
analytics.js
23 ms
fbevents.js
49 ms
gpt.js
48 ms
collect
28 ms
pubads_impl_82.js
7 ms
154 ms
container.html
44 ms
collect
89 ms
view_logo_main.gif
342 ms
view_venue_img_default.png
121 ms
lab.min.js
235 ms
uQayDQNkaPDIqFULgsppTtnqQfr4mDwHWlg7IBZgu1m.jpg
324 ms
uQayDQNkaPDIqFULgsppTtnqQfr4mDwHWlg7IBZgu1m.jpg
371 ms
vzLbbQ7oZoeCx8fjsMcvlvy7xWaCjSDd1FpgKGKwpSk.jpg
931 ms
84poudArDOUCERwRoLAvqw2LRc6RC8Tl6ENAY17CoD2.jpg
265 ms
NrOJkY2nndxnqq5gKcanS3U6juS2j4ffYzeiyHowsXd.jpg
375 ms
view_img_default_hotel.png
314 ms
LNTYbB5HMIG5kDMXGkaluotoVoYbIA6rhKgfcqKijQZ.jpg
384 ms
lEehz8thX2uZJGgMW7EEUILdy2WwytpP2LoVEtaByGt.jpg
402 ms
I7heeX3zRNnaLEbuNQ4C1MfbmhGZSCo2q9cbKcKPVHN.jpg
410 ms
view_img_default_restaurant.png
372 ms
cCENEDKYfUJnwdInercB2vVLVjlskAZvLyaVOmHdcx8.jpg
514 ms
cBsK4eYiezkxu7Y1t3F3QO3wTAFMpIdYD2mN5SAcSbh.jpg
515 ms
XllBtTYbxQ5doGkdGkesVIA3oRn6QGFma23ymnd5Ko1.jpg
515 ms
view_icon_google_signin.gif
254 ms
view_icon_fb_signin.gif
255 ms
view_icon_home.gif
224 ms
search_button_loader.gif
230 ms
view_stars.png
313 ms
view_link_arrow_med.png
326 ms
view_icon_cat_venuetype.gif
308 ms
view_link_arrow_sml.png
368 ms
site.base.min.1.css
338 ms
site.home.min.1.css
506 ms
cb=gapi.loaded_0
19 ms
jsapi
138 ms
postmessageRelay
30 ms
3193398744-postmessagerelay.js
24 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
3 ms
31 ms
ui+en,table+en.css
29 ms
webfontloader,format+en,default+en,ui+en,table+en,corechart+en.I.js
199 ms
view_stars_sml.png
107 ms
view_badge_firstreview_60.png
105 ms
view_icon_google_panel.gif
108 ms
view_icon_fb_panel.gif
83 ms
view_icon_google_loginbar.gif
128 ms
view_icon_fb_loginbar.gif
88 ms
view_icon_fb_signin_bar.gif
165 ms
view_icon_twitter_signin_bar.gif
262 ms
view_icon_google_signin_bar.gif
191 ms
view_footer_appstore.gif
192 ms
view_logo_kandc.png
194 ms
pageviews
1709 ms
jquery.min.js
8 ms
site.fun.1.1.js
197 ms
site.min.1.2.js
306 ms
jquery.autocomplete.min.js
264 ms
site.towns.min.1.js
266 ms
site.towns.areas.min.1.js
280 ms
jquery.modal.min.js
277 ms
jquery.validate.min.js
356 ms
placeholders.min.js
357 ms
jquery.template.min.js
412 ms
adservices
86 ms
widgets.js
14 ms
sdk.js
6 ms
39 ms
xd_arbiter.php
17 ms
xd_arbiter.php
22 ms
viewedinburgh.co.uk SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viewedinburgh.co.uk can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Viewedinburgh.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.
viewedinburgh.co.uk
Open Graph description is not detected on the main page of Viewedinburgh. 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: