8 sec in total
360 ms
6.9 sec
810 ms
Visit hubbardandbell.com now to see the best up-to-date Hubbardandbell content for United Kingdom and also check out these interesting facts you probably never knew about hubbardandbell.com
A neighbourhood restaurant in The Hoxton, Holborn with a focus on local seasonal ingredients and great wines for all.
Visit hubbardandbell.comWe analyzed Hubbardandbell.com page load time and found that the first response time was 360 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hubbardandbell.com performance score
360 ms
507 ms
244 ms
178 ms
10 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 25% of them (27 requests) were addressed to the original Hubbardandbell.com, 33% (35 requests) were made to Maps.googleapis.com and 14% (15 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Hubbardandbell.com.
Page size can be reduced by 711.5 kB (8%)
8.5 MB
7.8 MB
In fact, the total size of Hubbardandbell.com main page is 8.5 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 7.5 MB which makes up the majority of the site volume.
Potential reduce by 81.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 81.9 kB or 87% of the original size.
Potential reduce by 37.7 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. Hubbardandbell images are well optimized though.
Potential reduce by 555.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 555.0 kB or 67% of the original size.
Potential reduce by 36.9 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. Hubbardandbell.com needs all CSS files to be minified and compressed as it can save up to 36.9 kB or 77% of the original size.
Number of requests can be reduced by 32 (35%)
92
60
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hubbardandbell. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hubbardandbell.com
360 ms
www.hubbardandbell.com
507 ms
bsk4dwd.js
244 ms
application-cfb62356dde8f23c5bcfb4612e851ff1.css
178 ms
jquery.min.js
10 ms
application-ba112e9904c30b50fc52373561995aaa.js
178 ms
default.aspx
499 ms
js
121 ms
17db
175 ms
footer.css
386 ms
Hubbard_Bell_102.jpg
1587 ms
Hubbard_Bell_006.jpg
991 ms
Lobby_Reception_041.jpg
1417 ms
hubs2.png
278 ms
nav-logo-x2-07885c16a3e556820948572450fba117.png
190 ms
feast_v2_RTP2-012345_copy.jpg
1107 ms
Coffee_Bar_043.jpg
1024 ms
Lobby_Window_006.jpg
1114 ms
Bar_125.jpg
1742 ms
Hubbard_Bell_085.jpg
1775 ms
Lobby_Reception_076.jpg
1906 ms
Lobby_Reception_023.jpg
2121 ms
cocktails14.jpg
2520 ms
Bar_Lobby_003.jpg
4274 ms
Exterior_021.jpg
2722 ms
Exterior_030.jpg
2952 ms
Lobby_Reception_069.jpg
2793 ms
hubs.png
2298 ms
ot_short.css
272 ms
abZFRmIHTVuqMPKTChMiNAgrHJAcMHMfTF5UsdwwzDbffHhUggMWeMI6MK6f5Mb.eot
31 ms
2e-t8CJULNm1PIRWBzlJlU13lYhzsYkZdpI8cgkKtfIffOeUggMWeMI6MK6f5MS.eot
57 ms
s0213919619563
8 ms
banner.jpg
643 ms
sh-footer.png
479 ms
twitter-icon-x2-694f6ae289e0ddf65a1256d49157a3d8.png
2139 ms
facebook-icon-x2-db9d3ed33aa28e45f1cdea91479189de.png
2330 ms
instagram-icon-x2-5f765f36e5d7c8339b10792f773fdffd.png
2349 ms
ga.js
175 ms
jquery-ui-1.8.11.custom.min.js
75 ms
thickbox.js
74 ms
thickbox.css
299 ms
jquery-ui-1.8.5.custom.css
287 ms
prev-1cb7a664d1a29d613dfc99451b9e0a4a.png
2335 ms
next-7b3c1b9289b23f1d7b71f7174bfae6c0.png
2354 ms
E0bhR_plR50hYo6ATxcCn3V_KbeHMYZq-fD8iZuoLOIff5-oggMWeMI6MK6f5M9.eot
73 ms
AQTMc9l1OBWyqH45xprB20RlJPZpzUhjqXQKAXKpQwwffFnMggMWeMI6MK6f5Mt.eot
73 ms
Vp90f7_efVMpmV14DOguOHNqxM9cNkrjf5jTqfjLsIJffFDMggMWeMI6MK6f5gI.eot
129 ms
uvhMBwPYqtGiyuIhiz_Qdd54K9QApdA-5Uw02q4BxPwffF1MggMWeMI6MK6f5Mb.eot
130 ms
jvThT0OLBJQwptWIvEh1mfpdXSNiGCCHmL82a7ruubwffFzMggMWeMI6MK6f5MS.eot
140 ms
owqrav6-bPDI5eJ3j6GxrXaAfuUOPzYTGN7L3QQ4es9ffFKUgsMWeMI6MK6f5Mt.eot
140 ms
6GEaFeX6bNc0n3l-BAONRbjUgScL9vkHqkDpWSEyFfGffFfUgsMWeMI6MK6f5gI.eot
199 ms
3L6z36UcfOEJAc4ikEYUNg_U_rC0DQrU8A3hPduAPRJffFpUgsMWeMI6MK6f5Mb.eot
201 ms
qa7S5BL5IC6dJFCqnRv6Ya2tiGdJ9G0EtORvV1TrijSffwrUgsMWeMI6MK6f5MS.eot
198 ms
oIa9Yp9NzizxzntnDmrzCfNonAoDsntEu9ur8i_bmECffF7UgsMWeMI6MK6f5MX.eot
199 ms
Sh5o-4YFwxFGfS4zzhFiUnAqlyZ8hk_KCw8WuA-wqdjffFcUgsMWeMI6MK6f5Mw.eot
200 ms
__utm.gif
67 ms
jquery.scrollTo-min.js
77 ms
loading-animation.gif
21 ms
ba-postmessage.js
75 ms
CookieCheck.aspx
102 ms
ui-bg_flat_75_ffffff_40x100.png
135 ms
ScriptHandler.ashx
193 ms
CookieCheck.aspx
110 ms
common.js
19 ms
map.js
38 ms
util.js
71 ms
marker.js
70 ms
onion.js
19 ms
stats.js
39 ms
controls.js
33 ms
ViewportInfoService.GetViewportInfo
101 ms
transparent.png
73 ms
css
129 ms
google4.png
56 ms
mapcnt6.png
74 ms
sv5.png
74 ms
spotlight-poi.png
73 ms
tmapctrl.png
70 ms
cb_scout5.png
83 ms
tmapctrl4.png
115 ms
imgs8.png
81 ms
vt
115 ms
vt
91 ms
vt
104 ms
vt
100 ms
vt
109 ms
vt
113 ms
vt
153 ms
vt
168 ms
vt
185 ms
vt
190 ms
vt
184 ms
vt
185 ms
vt
230 ms
vt
238 ms
vt
248 ms
vt
266 ms
vt
260 ms
vt
274 ms
vt
305 ms
vt
322 ms
vt
333 ms
vt
332 ms
vt
335 ms
vt
350 ms
vt
434 ms
AuthenticationService.Authenticate
211 ms
hubbardandbell.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 Hubbardandbell.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 Hubbardandbell.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.
hubbardandbell.com
Open Graph description is not detected on the main page of Hubbardandbell. 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: