10 sec in total
111 ms
9.6 sec
275 ms
Click here to check amazing Guia Maritimo content for Brazil. Otherwise, check out these important facts you probably never knew about guiamaritimo.com.br
Transporte Marítimo, Vai importar ou exportar? Aqui você encontra Empresas de Comércio Exterior e Logística, de Agentes Marítimos ao Transportador Rodoviário. Veja também Notícias sobre Logística, Mar...
Visit guiamaritimo.com.brWe analyzed Guiamaritimo.com.br page load time and found that the first response time was 111 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
guiamaritimo.com.br performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value15.6 s
0/100
25%
Value15.1 s
1/100
10%
Value1,200 ms
20/100
30%
Value0.025
100/100
15%
Value14.5 s
9/100
10%
111 ms
437 ms
74 ms
57 ms
33 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 83% of them (128 requests) were addressed to the original Guiamaritimo.com.br, 5% (8 requests) were made to Google.com and 3% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Guiamaritimo.com.br.
Page size can be reduced by 121.9 kB (8%)
1.6 MB
1.5 MB
In fact, the total size of Guiamaritimo.com.br main page is 1.6 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 822.4 kB which makes up the majority of the site volume.
Potential reduce by 81.5 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. This page needs HTML code to be minified as it can gain 11.3 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 81.5 kB or 80% of the original size.
Potential reduce by 15.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. Guia Maritimo images are well optimized though.
Potential reduce by 14.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.1 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. Guiamaritimo.com.br needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 25% of the original size.
Number of requests can be reduced by 59 (40%)
149
90
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guia Maritimo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
guiamaritimo.com.br
111 ms
www.guiamaritimo.com.br
437 ms
gtm.js
74 ms
api.js
57 ms
slick.css
33 ms
select2.min.css
42 ms
jquery.mCustomScrollbar.min.css
43 ms
gridstack.min.css
42 ms
material-forms.css
42 ms
grid-sys.css
40 ms
side-nav.css
43 ms
main-nav.css
47 ms
mobile-menu.css
48 ms
list.css
47 ms
mail-share-form.css
48 ms
main.css
48 ms
style.css
792 ms
style.css
1999 ms
style.css
2000 ms
style.css
1999 ms
style.css
2001 ms
style.css
2001 ms
style.css
799 ms
js
84 ms
js
97 ms
jquery.min.js
812 ms
jquery-ui.min.js
828 ms
underscore-min.js
836 ms
gridstack.min.js
844 ms
materialize.min.js
853 ms
jquery.mCustomScrollbar.concat.min.js
860 ms
select2.full.min.js
869 ms
slick.js
877 ms
js
146 ms
slick.min.js
884 ms
grid-sys.js
892 ms
main.js
1801 ms
view.js
1809 ms
view.js
1816 ms
view.js
1824 ms
view.js
1832 ms
recaptcha__pt_br.js
51 ms
css
87 ms
logo.png
45 ms
notices-icon.png
45 ms
articles-icon.png
7057 ms
service-guide-icon.png
7057 ms
events-icon.png
7057 ms
utilities-icon.png
7058 ms
linkedin-icon.svg
767 ms
twitter-icon.svg
7054 ms
facebook-icon.svg
775 ms
home-icon.svg
783 ms
news-icon.svg
792 ms
articles-icon.svg
798 ms
services-icon.svg
806 ms
events-icon.svg
814 ms
iconRevistas.svg
822 ms
utilities-icon.svg
831 ms
zarpar-icon.svg
840 ms
70-52-237-0.jpg
847 ms
70-52-180-0.jpg
855 ms
70-52-237-0.jpg
1764 ms
70-52-237-0.jpg
1771 ms
70-52-237-0.jpg
1779 ms
70-52-131-0.jpg
1786 ms
100-74-453-0.jpg
1795 ms
100-74-0-0.jpg
1802 ms
100-74-235-0.jpg
1809 ms
100-74-235-0.jpg
1816 ms
100-74-235-0.jpg
1823 ms
100-74-235-0.jpg
1830 ms
100-74-175-0.jpg
1838 ms
100-74-215-0.jpg
1845 ms
100-74-235-0.jpg
2816 ms
100-74-130-0.jpg
2824 ms
100-74-235-0.jpg
2830 ms
100-74-235-0.jpg
2837 ms
sdk.js
89 ms
100-74-130-0.jpg
2806 ms
100-74-130-0.jpg
2812 ms
js
45 ms
159 ms
100-74-130-0.jpg
2740 ms
cse.js
305 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
294 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
327 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
328 ms
sdk.js
135 ms
analytics.js
241 ms
78 ms
cse_element__pt_pt.js
74 ms
default+pt_PT.css
59 ms
default.css
56 ms
collect
39 ms
collect
63 ms
async-ads.js
23 ms
branding.png
20 ms
clear.png
15 ms
nav_logo114.png
15 ms
afr.php
33 ms
afr.php
37 ms
afr.php
34 ms
linkedin-icon.svg
2077 ms
twitter-icon.svg
2081 ms
facebook-icon.svg
2086 ms
home-icon.svg
2087 ms
news-icon.svg
2088 ms
articles-icon.svg
3001 ms
services-icon.svg
3008 ms
events-icon.svg
3008 ms
iconRevistas.svg
3006 ms
utilities-icon.svg
3005 ms
zarpar-icon.svg
3005 ms
close-icon.svg
3007 ms
mobile-menu-trigger-icon.svg
2104 ms
cover-icon.svg
2106 ms
mobile-search-icon.svg
2107 ms
100-74-0-0.jpg
2108 ms
100-74-235-0.jpg
3016 ms
100-74-130-0.jpg
3016 ms
clock-icon.png
3017 ms
100-74-235-0.jpg
3017 ms
100-74-235-0.jpg
3018 ms
100-74-27-0.jpg
3016 ms
100-74-235-0.jpg
3017 ms
100-74-235-0.jpg
3017 ms
100-74-235-0.jpg
2052 ms
100-74-344-0.jpg
2053 ms
100-74-235-0.jpg
2989 ms
100-74-235-0.jpg
2990 ms
close-icon.svg
2989 ms
mobile-menu-trigger-icon.svg
2989 ms
cover-icon.svg
2989 ms
mobile-search-icon.svg
2987 ms
phocus-sign.png
2987 ms
mobile-top-bg.png
2988 ms
aside-bg.png
2990 ms
670-480-225-0.jpg
3000 ms
670-480-168-0.jpg
2101 ms
670-480-225-0.jpg
2110 ms
670-480-225-0.jpg
2955 ms
670-480-225-0.jpg
2963 ms
670-480-121-0.jpg
2971 ms
404-border.png
2972 ms
alert-icon.png
2972 ms
mobile-arrow-left.png
2972 ms
mobile-arrow-right.png
2973 ms
63bc38805b7f9dcce126523c0601388c.gif
24 ms
lg.php
22 ms
857de3e473d74b91557724953b8d460d.jpg
916 ms
lg.php
17 ms
effb6e5b490f01b964e3db7c91d8198e.jpg
896 ms
lg.php
23 ms
guiamaritimo.com.br 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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
guiamaritimo.com.br 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
Page has valid source maps
guiamaritimo.com.br SEO score
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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guiamaritimo.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Guiamaritimo.com.br 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.
guiamaritimo.com.br
Open Graph data is detected on the main page of Guia Maritimo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: