1.9 sec in total
114 ms
1.3 sec
516 ms
Visit uboat.net now to see the best up-to-date U Boat content for United States and also check out these interesting facts you probably never knew about uboat.net
The U-boat War in World War Two (1939-1945) and World War One (1914-1918). Over 30,000 pages on the officers, the boats, technology and the Allied efforts to counter the U-boat threat.
Visit uboat.netWe analyzed Uboat.net page load time and found that the first response time was 114 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
uboat.net performance score
name
value
score
weighting
Value1.5 s
97/100
10%
Value3.4 s
67/100
25%
Value2.9 s
95/100
10%
Value470 ms
61/100
30%
Value0.024
100/100
15%
Value6.4 s
60/100
10%
114 ms
28 ms
5 ms
6 ms
294 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 40% of them (12 requests) were addressed to the original Uboat.net, 17% (5 requests) were made to Pagead2.googlesyndication.com and 13% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (556 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 64.6 kB (44%)
146.6 kB
82.0 kB
In fact, the total size of Uboat.net main page is 146.6 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. 45% of websites need less resources to load. Javascripts take 67.5 kB which makes up the majority of the site volume.
Potential reduce by 11.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 11.0 kB or 66% of the original size.
Potential reduce by 1.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. U Boat images are well optimized though.
Potential reduce by 32.1 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 32.1 kB or 48% of the original size.
Potential reduce by 20.4 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. Uboat.net needs all CSS files to be minified and compressed as it can save up to 20.4 kB or 85% of the original size.
Number of requests can be reduced by 7 (25%)
28
21
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of U Boat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
uboat.net
114 ms
main.css
28 ms
adsbygoogle.js
5 ms
show_ads.js
6 ms
analytics.js
294 ms
Logo_25wht.gif
231 ms
zrt_lookup.html
556 ms
show_ads_impl.js
170 ms
header_970.gif
170 ms
rss_18.gif
518 ms
twitter_newbird_18.gif
517 ms
fiebig_gunther.jpg
517 ms
front_emblem.gif
516 ms
0987223186.jpg
517 ms
u1277e_s.jpg
517 ms
Elbe-II_1945_westbox-innen_s.jpg
534 ms
m0010270conning-tower-hatch_s.jpg
535 ms
ca-pub-1101670507446460.js
488 ms
ads
267 ms
ads
235 ms
collect
37 ms
osd.js
36 ms
print.css
17 ms
m_js_controller.js
41 ms
abg.js
131 ms
favicon
187 ms
googlelogo_color_112x36dp.png
168 ms
nessie_icon_tiamat_white.png
136 ms
s
79 ms
x_button_blue2.png
50 ms
uboat.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-*] attributes do not match their roles
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
Form elements do not have associated labels
Links do not have a discernible name
uboat.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
uboat.net SEO score
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 Uboat.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 Uboat.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.
uboat.net
Open Graph description is not detected on the main page of U Boat. 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: