Tools & Wizards About Us
datamar.com.br screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

datamar.com.br

Ferramentas de Inteligência de Mercado - Datamar

Page Load Speed

4 sec in total

First Response

208 ms

Resources Loaded

2.6 sec

Page Rendered

1.2 sec

datamar.com.br screenshot

About Website

Welcome to datamar.com.br homepage info - get ready to check Datamar best content for Turkey right away, or after learning these important things about datamar.com.br

A Datamar fornece inteligência de dados para o comércio exterior marítimo na América do Sul. Ferramentas de inteligência de mercado e análise de dados para decisões de comércio e logística.

Visit datamar.com.br

Key Findings

We analyzed Datamar.com.br page load time and found that the first response time was 208 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

datamar.com.br performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value8,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value2.013

0/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

datamar.com.br

208 ms

27 ms

autoptimize_single_7f50f9a16e58906545cacf2d10276583.js

1494 ms

js

120 ms

autoptimize_single_3fd2afa98866679439097f4ab102fe0a.css

1242 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 10% of them (9 requests) were addressed to the original Datamar.com.br, 78% (68 requests) were made to Sp-ao.shortpixel.ai and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Sp-ao.shortpixel.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 221.8 kB (43%)

Content Size

513.9 kB

After Optimization

292.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Datamar.com.br main page is 513.9 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. 50% of websites need less resources to load. Javascripts take 351.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 119.8 kB

  • Original 143.7 kB
  • After minification 143.5 kB
  • After compression 23.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 119.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 19.2 kB
  • After minification 19.2 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. Datamar images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 102.0 kB

  • Original 351.0 kB
  • After minification 351.0 kB
  • After compression 249.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 102.0 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (88%)

Requests Now

84

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datamar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

datamar.com.br

datamar.com.br

208 ms

27 ms

autoptimize_single_7f50f9a16e58906545cacf2d10276583.js

autoptimize_single_7f50f9a16e58906545cacf2d10276583.js

1494 ms

js

js

120 ms

autoptimize_single_3fd2afa98866679439097f4ab102fe0a.css

autoptimize_single_3fd2afa98866679439097f4ab102fe0a.css

1242 ms

autoptimize_single_20e8490fab0dcf7557a5c8b54494db6f.css

autoptimize_single_20e8490fab0dcf7557a5c8b54494db6f.css

237 ms

autoptimize_single_359aca8a88b2331aa34ac505acad9911.css

autoptimize_single_359aca8a88b2331aa34ac505acad9911.css

1425 ms

autoptimize_single_55322baf997c94f44087594534d86d22.css

autoptimize_single_55322baf997c94f44087594534d86d22.css

284 ms

autoptimize_single_3eadb1753cb73307449cac69b2e03fad.css

autoptimize_single_3eadb1753cb73307449cac69b2e03fad.css

251 ms

countrySelect.min.css

countrySelect.min.css

428 ms

autoptimize_single_80af15eda6f6398b78dfa7b32e63334e.css

autoptimize_single_80af15eda6f6398b78dfa7b32e63334e.css

339 ms

autoptimize_single_13fa49bdc237df7eeaff052c5d6eeb84.css

autoptimize_single_13fa49bdc237df7eeaff052c5d6eeb84.css

480 ms

autoptimize_single_4f10a733c743cb907bc019cd7d9e595a.css

autoptimize_single_4f10a733c743cb907bc019cd7d9e595a.css

538 ms

autoptimize_single_6f7efc3e226db758a6f97ee01246a0ec.css

autoptimize_single_6f7efc3e226db758a6f97ee01246a0ec.css

569 ms

autoptimize_single_9c353baa15ce00f99e56504bfc9bd0db.css

autoptimize_single_9c353baa15ce00f99e56504bfc9bd0db.css

636 ms

swiper-bundle.min.css

swiper-bundle.min.css

680 ms

autoptimize_single_e999bbc0d9361bd47b71927f1d86235d.css

autoptimize_single_e999bbc0d9361bd47b71927f1d86235d.css

716 ms

autoptimize_single_88192010272bbaa6523212903aaf90cb.js

autoptimize_single_88192010272bbaa6523212903aaf90cb.js

683 ms

autoptimize_single_2ba875e02f8da2c1260e11d46ef54188.js

autoptimize_single_2ba875e02f8da2c1260e11d46ef54188.js

681 ms

autoptimize_single_1194b54884263d41f879beb9b52926e7.js

autoptimize_single_1194b54884263d41f879beb9b52926e7.js

730 ms

autoptimize_single_417fd72151d97841fd64376f3fff943e.js

autoptimize_single_417fd72151d97841fd64376f3fff943e.js

726 ms

autoptimize_single_9112fc545a4c9d72e84c6c0094909df7.js

autoptimize_single_9112fc545a4c9d72e84c6c0094909df7.js

758 ms

instantpage.min.js

instantpage.min.js

48 ms

getSeal

getSeal

353 ms

lazysizes.min.js

lazysizes.min.js

911 ms

autoptimize_single_99465e5f69c7398186d8d7aafbd65749.css

autoptimize_single_99465e5f69c7398186d8d7aafbd65749.css

863 ms

autoptimize_single_891497a9178f55b4a865d81b8b49433b.css

autoptimize_single_891497a9178f55b4a865d81b8b49433b.css

987 ms

autoptimize_single_3d964288093e68febb80bb13ecbe6e6e.css

autoptimize_single_3d964288093e68febb80bb13ecbe6e6e.css

1019 ms

autoptimize_single_43c6878f3a15b847c93b71de12a87910.css

autoptimize_single_43c6878f3a15b847c93b71de12a87910.css

1070 ms

autoptimize_single_b1f5fae4f844304f4bcf3f7978a9b63a.css

autoptimize_single_b1f5fae4f844304f4bcf3f7978a9b63a.css

1116 ms

autoptimize_single_89e09d6c498cb14c782344325cad6928.css

autoptimize_single_89e09d6c498cb14c782344325cad6928.css

1191 ms

autoptimize_single_246b919e2f942727f655d25a8773b4fa.css

autoptimize_single_246b919e2f942727f655d25a8773b4fa.css

1298 ms

autoptimize_single_526e4d33ba0119782544fff1c5afbf0f.css

autoptimize_single_526e4d33ba0119782544fff1c5afbf0f.css

1258 ms

autoptimize_single_bf4df41121ebd37bed3a11b2d81d7b2f.css

autoptimize_single_bf4df41121ebd37bed3a11b2d81d7b2f.css

1479 ms

autoptimize_single_87616d2a1cc2637c27612b94f6a96ed6.css

autoptimize_single_87616d2a1cc2637c27612b94f6a96ed6.css

1482 ms

autoptimize_single_d9e35a1aac12390fa65a05bb76d83028.css

autoptimize_single_d9e35a1aac12390fa65a05bb76d83028.css

1482 ms

autoptimize_single_8095f0a4275f2c5214899c2a47ac61af.css

autoptimize_single_8095f0a4275f2c5214899c2a47ac61af.css

1482 ms

autoptimize_single_2d6f2d71d4c211ea3b000cbe2be0b05d.css

autoptimize_single_2d6f2d71d4c211ea3b000cbe2be0b05d.css

1619 ms

autoptimize_single_24c211bf4b150027cbcf4f60381d2573.css

autoptimize_single_24c211bf4b150027cbcf4f60381d2573.css

1665 ms

autoptimize_single_1926964513feb2ffba9f1b97d91a1052.css

autoptimize_single_1926964513feb2ffba9f1b97d91a1052.css

1618 ms

autoptimize_single_a09f595986066b97ccfb95ae8928c910.css

autoptimize_single_a09f595986066b97ccfb95ae8928c910.css

1664 ms

api.js

api.js

98 ms

scc-c2.min.js

scc-c2.min.js

6 ms

tti.min.js

tti.min.js

6 ms

autoptimize_single_26b4f0c3c1bcf76291fa4952fb7f04fb.css

autoptimize_single_26b4f0c3c1bcf76291fa4952fb7f04fb.css

1433 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1418 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1533 ms

wp-polyfill.min.js

wp-polyfill.min.js

1444 ms

hooks.min.js

hooks.min.js

1383 ms

i18n.min.js

i18n.min.js

1352 ms

autoptimize_single_efc27e253fae1b7b891fb5a40e687768.js

autoptimize_single_efc27e253fae1b7b891fb5a40e687768.js

1148 ms

autoptimize_single_0b1719adf5fa7231cb1a1b54cf11a50e.js

autoptimize_single_0b1719adf5fa7231cb1a1b54cf11a50e.js

1289 ms

autoptimize_single_a56436c9e214ef323a2a3581d13dffe9.js

autoptimize_single_a56436c9e214ef323a2a3581d13dffe9.js

1053 ms

swiper-bundle.min.js

swiper-bundle.min.js

1009 ms

autoptimize_single_cd02ee8ec86ea1b7e0fffd8de78b8879.js

autoptimize_single_cd02ee8ec86ea1b7e0fffd8de78b8879.js

1007 ms

autoptimize_single_f96ccb705fb55aef9add3e34635f9854.js

autoptimize_single_f96ccb705fb55aef9add3e34635f9854.js

1124 ms

autoptimize_single_bd65a089628796a46aeed8fa6e722557.js

autoptimize_single_bd65a089628796a46aeed8fa6e722557.js

1068 ms

autoptimize_single_191c6cc14fa37dd3f6ea910c895a9bca.js

autoptimize_single_191c6cc14fa37dd3f6ea910c895a9bca.js

1111 ms

autoptimize_single_11bc9f0dbe87a648a40a2216447e260d.js

autoptimize_single_11bc9f0dbe87a648a40a2216447e260d.js

1079 ms

autoptimize_single_d569099795fce09f3a9cbbe46bc824f7.js

autoptimize_single_d569099795fce09f3a9cbbe46bc824f7.js

1068 ms

autoptimize_single_10da64a073b109155ef442dcf8e2a863.js

autoptimize_single_10da64a073b109155ef442dcf8e2a863.js

999 ms

autoptimize_single_9613d4249c5a8c66061bada734e73235.js

autoptimize_single_9613d4249c5a8c66061bada734e73235.js

949 ms

language-switcher-arrow_black.svg

language-switcher-arrow_black.svg

60 ms

Map-of-South-America-Blue-Transparent-min-e1715081248983-min-4.png

Map-of-South-America-Blue-Transparent-min-e1715081248983-min-4.png

65 ms

logo_black.svg

logo_black.svg

62 ms

phone.svg

phone.svg

345 ms

whatsapp.svg

whatsapp.svg

350 ms

insight.min.js

insight.min.js

77 ms

trusted-source_line.svg

trusted-source_line.svg

313 ms

trade-data-system_list-item.svg

trade-data-system_list-item.svg

318 ms

trade-data-system_arrow.svg

trade-data-system_arrow.svg

319 ms

intro_arrow.svg

intro_arrow.svg

321 ms

features_underline.svg

features_underline.svg

325 ms

play.svg

play.svg

322 ms

numbers_underline.svg

numbers_underline.svg

662 ms

slider_arrow.svg

slider_arrow.svg

324 ms

insight_tag_errors.gif

insight_tag_errors.gif

40 ms

whatsapp.png

whatsapp.png

501 ms

logo_black_big.svg

logo_black_big.svg

22 ms

logo_white.svg

logo_white.svg

182 ms

slider_arrow_purple.svg

slider_arrow_purple.svg

180 ms

faq_expand.svg

faq_expand.svg

183 ms

mail.svg

mail.svg

351 ms

siteseal_gd_3_h_d_m.gif

siteseal_gd_3_h_d_m.gif

88 ms

recaptcha__en.js

recaptcha__en.js

39 ms

picturefill.min.js

picturefill.min.js

20 ms

js

js

67 ms

Accessibility Review

datamar.com.br accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Form elements do not have associated labels

Best Practices

datamar.com.br best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

datamar.com.br SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datamar.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Datamar.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.

Social Sharing Optimization

datamar.com.br

Open Graph data is detected on the main page of Datamar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: