2.4 sec in total
216 ms
1.6 sec
589 ms
Visit oldship.net now to see the best up-to-date Old Ship content and also check out these interesting facts you probably never knew about oldship.net
The Old Ship, Limehouse - Traditional East End pub with LGBT+ cabaret.
Visit oldship.netWe analyzed Oldship.net page load time and found that the first response time was 216 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
oldship.net performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value11.6 s
0/100
25%
Value7.0 s
32/100
10%
Value430 ms
64/100
30%
Value0.001
100/100
15%
Value9.4 s
30/100
10%
216 ms
61 ms
70 ms
89 ms
82 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 54% of them (31 requests) were addressed to the original Oldship.net, 26% (15 requests) were made to Pubevents.webeditors.co.uk and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (520 ms) belongs to the original domain Oldship.net.
Page size can be reduced by 82.6 kB (6%)
1.4 MB
1.3 MB
In fact, the total size of Oldship.net main page is 1.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 41.7 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 41.7 kB or 87% of the original size.
Potential reduce by 40.8 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. Old Ship images are well optimized though.
Potential reduce by 32 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 70 B
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. Oldship.net has all CSS files already compressed.
Number of requests can be reduced by 15 (32%)
47
32
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Old Ship. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
oldship.net
216 ms
bootstrap.min.css
61 ms
font-awesome.min.css
70 ms
style.css
89 ms
booze.css
82 ms
find-us-on-boozr-en.png
56 ms
email-decode.min.js
16 ms
booze.min.js
83 ms
main.js
76 ms
jquery.tweet.js
81 ms
js
100 ms
gmap3.min.js
79 ms
init.js
96 ms
jquery.gray.min.js
97 ms
form.js
97 ms
old_ship_white.png
98 ms
big-intro1.png
101 ms
mobile-intro.png
97 ms
news400x300.png
101 ms
footer-logo.png
104 ms
embed
495 ms
css
29 ms
css
41 ms
gray-scale.css
19 ms
marsha_mallow_photo.jpg
488 ms
nowhiring.jpg
427 ms
hero-background.jpg
490 ms
boozr.jpg
22 ms
cabaretisback.jpg
488 ms
nowpouring.jpg
23 ms
ajax-loader.gif
21 ms
mileselliot_photo.jpg
307 ms
auntieginger_photo.jpg
389 ms
saffronslayter_photo.jpg
390 ms
tiff_photo.jpg
308 ms
OLDSHIP-QUIZ-web_photo.jpg
309 ms
016B121F-9915-4A01-A410-AFF7E5B6F933_photo.webp
392 ms
rubyviolet_photo.jpg
391 ms
juliepaid_photo.jpg
390 ms
marielarae_photo.jpg
392 ms
imelda_photo.jpg
463 ms
full_mrsmoore_photo.jpg
464 ms
lola_photo.jpg
465 ms
sissylea_photo.jpg
466 ms
john_fell_photo.jpg
466 ms
Qw3GZR9MED_6PSuS_50nEaVrfzgEbHoEig.ttf
27 ms
TitilliumText400wt.svg
418 ms
TitilliumText800wt.svg
431 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
70 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
78 ms
fontawesome-webfont.woff
520 ms
Qw3AZR9MED_6PSuS_50nEaVrfzgEbH80jbs6.ttf
79 ms
slick.woff
360 ms
js
38 ms
TitilliumText400wt.ttf
401 ms
TitilliumText800wt.ttf
421 ms
oldship.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
oldship.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
oldship.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oldship.net 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 Oldship.net 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.
oldship.net
Open Graph description is not detected on the main page of Old Ship. 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: