5.5 sec in total
325 ms
2.9 sec
2.2 sec
Welcome to grosstonnage.com homepage info - get ready to check Grosstonnage best content right away, or after learning these important things about grosstonnage.com
Maritime traffic on a live map. Past, current and future ship positions for almost every vessel in the world. Plus port information and APIs.
Visit grosstonnage.comWe analyzed Grosstonnage.com page load time and found that the first response time was 325 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
grosstonnage.com performance score
name
value
score
weighting
Value12.2 s
0/100
10%
Value12.5 s
0/100
25%
Value19.9 s
0/100
10%
Value18,510 ms
0/100
30%
Value0.001
100/100
15%
Value33.1 s
0/100
10%
325 ms
1161 ms
49 ms
69 ms
146 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Grosstonnage.com, 70% (43 requests) were made to Static.fleetmon.com and 16% (10 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Fleetmon.com.
Page size can be reduced by 115.5 kB (13%)
884.8 kB
769.3 kB
In fact, the total size of Grosstonnage.com main page is 884.8 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. 65% of websites need less resources to load. Images take 702.3 kB which makes up the majority of the site volume.
Potential reduce by 102.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 102.7 kB or 72% of the original size.
Potential reduce by 12.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. Grosstonnage images are well optimized though.
Potential reduce by 35 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. Grosstonnage.com has all CSS files already compressed.
Number of requests can be reduced by 28 (51%)
55
27
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grosstonnage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
grosstonnage.com
325 ms
www.fleetmon.com
1161 ms
bootstrap.min.css
49 ms
uikit.min.css
69 ms
fleetmon-core-styles.css
146 ms
fleetmon-extend.css
158 ms
index.css
166 ms
359 ms
8c5bd711f0.js
95 ms
jquery.min.js
91 ms
handlebars.min.js
90 ms
bootstrap.min.js
95 ms
uikit.min.js
94 ms
fleetmon-core-scripts.js
184 ms
fleetmon-extend.js
184 ms
index.js
184 ms
outdatedbrowser.min.css
35 ms
adsbygoogle.js
107 ms
cookieconsent.min.js
41 ms
outdatedbrowser.min.js
30 ms
cookieconsent.min.css
23 ms
fleetmon-logo-slogan-light.svg
377 ms
fleetmon-logo-slogan-light.svg
370 ms
FleetMon-San-Francisco-Satellite_Still-Mobile.jpg
74 ms
Hero-FleetMon-Data-Shop-Background-1920px.jpg
124 ms
slide-data-shop-tanker-vessel.jpg
74 ms
slide-data-shop-container-vessel.jpg
108 ms
slide-data-shop-passenger-vessel.jpg
106 ms
news-background.gif
107 ms
winners-cup-photo-week.svg
107 ms
highspeed_vessel_moving.svg
116 ms
tanker_vessel_moving.svg
109 ms
yacht_vessel_moving.svg
120 ms
cargo_vessel_moving.svg
122 ms
made-with-love-in-germany.svg
119 ms
ru.svg
125 ms
cargo.svg
124 ms
pa.svg
126 ms
kr.svg
131 ms
tug.svg
128 ms
mh.svg
129 ms
unknown.svg
129 ms
it.svg
144 ms
passenger.svg
133 ms
be.svg
136 ms
tanker.svg
135 ms
us.svg
131 ms
highspeed.svg
136 ms
fleetmon-logo-slogan-dark.svg
139 ms
fleetmon-logo-signet.svg
138 ms
dax-regular-webfont.woff
113 ms
dax-medium-webfont.woff
111 ms
dax-mediumitalic-webfont.woff
112 ms
dax-italic-webfont.woff
112 ms
fleetmon-logo-slogan-light.svg
184 ms
FleetMon-Explorer-Hamburg-Traffic.jpg
13 ms
df89233d4db011eb84fb5b60e0eaa779.png
160 ms
Hero-FleetMon-Developer-Tools-Background@2x-201809_02.jpg
14 ms
FleetMon-Developer-Tools-IDE@2x.jpg
14 ms
e8348d76345d0c9f6c21e1f679f49346.jpg
160 ms
analytics.min.js
179 ms
grosstonnage.com 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
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
grosstonnage.com 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
grosstonnage.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Grosstonnage.com 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 Grosstonnage.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.
grosstonnage.com
Open Graph description is not detected on the main page of Grosstonnage. 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: