Tools & Wizards About Us
cartodata.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

cartodata.com

CartoData - Photogrammetry, Cartography & Geospatial Solutions

Page Load Speed

2.9 sec in total

First Response

119 ms

Resources Loaded

2.2 sec

Page Rendered

511 ms

cartodata.com screenshot

About Website

Click here to check amazing Carto Data content for Mexico. Otherwise, check out these important facts you probably never knew about cartodata.com

CartoData provides photogrammetry, cartography & geospatial services using high end technology such as Nano-satellites, LiDAR, vertical and oblique aerial photography, drones, terrestrial panoramas an...

Visit cartodata.com

Key Findings

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

Performance Metrics

cartodata.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value62.3 s

0/100

25%

SI (Speed Index)

Value28.3 s

0/100

10%

TBT (Total Blocking Time)

Value2,230 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value48.8 s

0/100

10%

Network Requests Diagram

www.cartodata.com

119 ms

73 ms

a5ff7.css

69 ms

b5a03.css

141 ms

css

38 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 57% of them (51 requests) were addressed to the original Cartodata.com, 19% (17 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Cartodata.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (14%)

Content Size

12.3 MB

After Optimization

10.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cartodata.com main page is 12.3 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. Only a small number of websites need less resources to load. Images take 11.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 62.2 kB

  • Original 79.0 kB
  • After minification 72.8 kB
  • After compression 16.8 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 62.2 kB or 79% of the original size.

Image Optimization

-15%

Potential reduce by 1.7 MB

  • Original 11.5 MB
  • After minification 9.8 MB

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. Obviously, Carto Data needs image optimization as it can save up to 1.7 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.9 kB

  • Original 488.8 kB
  • After minification 488.8 kB
  • After compression 485.9 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.

CSS Optimization

-0%

Potential reduce by 16 B

  • Original 197.7 kB
  • After minification 197.7 kB
  • After compression 197.7 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. Cartodata.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (37%)

Requests Now

65

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.cartodata.com

www.cartodata.com

119 ms

73 ms

a5ff7.css

a5ff7.css

69 ms

b5a03.css

b5a03.css

141 ms

css

css

38 ms

css

css

58 ms

478cc.css

478cc.css

183 ms

86373.js

86373.js

182 ms

086cb.js

086cb.js

111 ms

css

css

62 ms

4a5ce.css

4a5ce.css

109 ms

6gm6r8v9ui.jsonp

6gm6r8v9ui.jsonp

15 ms

E-v1.js

E-v1.js

23 ms

55841.js

55841.js

331 ms

7c44a.js

7c44a.js

152 ms

38838.js

38838.js

222 ms

sdk.js

sdk.js

155 ms

ss.js

ss.js

274 ms

i8vSoZroHcY

i8vSoZroHcY

310 ms

CartoData_contact_whatsapp_button.png

CartoData_contact_whatsapp_button.png

246 ms

global.png

global.png

164 ms

AAMAAQDGAAoAAQAAAAAAABDUAAAAJDBjMTMxMmMzLTFhZTAtNGY2Mi05MDNmLWRiNjIwYjExZWEyYw.png

AAMAAQDGAAoAAQAAAAAAABDUAAAAJDBjMTMxMmMzLTFhZTAtNGY2Mi05MDNmLWRiNjIwYjExZWEyYw.png

854 ms

cartodata_informacion_transparente.jpg

cartodata_informacion_transparente.jpg

160 ms

cartodata-tecnologia-mas-avanzada.png

cartodata-tecnologia-mas-avanzada.png

163 ms

cartografia_bkg_slider.jpg

cartografia_bkg_slider.jpg

306 ms

cartodata__cartografia.png

cartodata__cartografia.png

378 ms

oblix_bkg_slider.jpg

oblix_bkg_slider.jpg

246 ms

cartodata__oblix.png

cartodata__oblix.png

322 ms

LiDAR_bkg_slider.jpg

LiDAR_bkg_slider.jpg

303 ms

cartodata_LiDAR.png

cartodata_LiDAR.png

633 ms

Vision360_bkg_slider.jpg

Vision360_bkg_slider.jpg

520 ms

cartodata_vision360.png

cartodata_vision360.png

636 ms

AU4_bkg_slider.jpg

AU4_bkg_slider.jpg

376 ms

cartodata_AU4.png

cartodata_AU4.png

634 ms

eCarto_bkg_slider.jpg

eCarto_bkg_slider.jpg

632 ms

cartodata_eCarto.png

cartodata_eCarto.png

639 ms

CartoData_what_do-we_do.png

CartoData_what_do-we_do.png

634 ms

CartoData_que_hacemos_diagrama-adquisicion-procesamiento-analisis-disponibilizacion-informacion-cartografica___mob.png

CartoData_que_hacemos_diagrama-adquisicion-procesamiento-analisis-disponibilizacion-informacion-cartografica___mob.png

634 ms

aviones.jpg

aviones.jpg

684 ms

cartodata_empodera_ciudades.png

cartodata_empodera_ciudades.png

636 ms

cartodata_empodera_seguimiento_obra.png

cartodata_empodera_seguimiento_obra.png

638 ms

cartodata_empodera_agricultores.png

cartodata_empodera_agricultores.png

638 ms

mineria.png

mineria.png

685 ms

grup_cartodata.jpg

grup_cartodata.jpg

704 ms

linkedin.png

linkedin.png

1194 ms

twitter.png

twitter.png

1197 ms

instagram.png

instagram.png

301 ms

youtube.png

youtube.png

302 ms

whatsapp.svg

whatsapp.svg

685 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

153 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

234 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

235 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

245 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

245 ms

modules.ttf

modules.ttf

572 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

140 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

141 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

138 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

140 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

141 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

183 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

181 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

142 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

141 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

180 ms

analytics.js

analytics.js

84 ms

sdk.js

sdk.js

27 ms

CartoData_contact_call_button.png

CartoData_contact_call_button.png

549 ms

collect

collect

73 ms

CartoData_contact_mail_button.png

CartoData_contact_mail_button.png

513 ms

logo_CartoData_2.png

logo_CartoData_2.png

514 ms

facebook.png

facebook.png

504 ms

CartoData_contact_whatsapp_button.png

CartoData_contact_whatsapp_button.png

500 ms

js

js

333 ms

www-player.css

www-player.css

21 ms

www-embed-player.js

www-embed-player.js

48 ms

base.js

base.js

77 ms

instagram.png

instagram.png

439 ms

youtube.png

youtube.png

547 ms

koi

koi

291 ms

ad_status.js

ad_status.js

190 ms

Xal8RkuvyCiU6W_GOvwH_DuhE1BN-1S9Ky9af2kVVy4.js

Xal8RkuvyCiU6W_GOvwH_DuhE1BN-1S9Ky9af2kVVy4.js

164 ms

embed.js

embed.js

78 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

18 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

18 ms

id

id

36 ms

Create

Create

103 ms

GenerateIT

GenerateIT

15 ms

linkedin.png

linkedin.png

37 ms

twitter.png

twitter.png

38 ms

Accessibility Review

cartodata.com accessibility score

72

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

cartodata.com best practices score

75

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

cartodata.com SEO score

81

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cartodata.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 Cartodata.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.

Social Sharing Optimization

cartodata.com

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