2.5 sec in total
24 ms
1.2 sec
1.3 sec
Welcome to cartodb.com homepage info - get ready to check CARTO Db best content for United States right away, or after learning these important things about cartodb.com
Cloud-native location intelligence platform for spatial analytics. Analyze, visualize, and develop apps with your spatial data at a limitless scale.
Visit cartodb.comWe analyzed Cartodb.com page load time and found that the first response time was 24 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
cartodb.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value9.6 s
0/100
25%
Value4.3 s
75/100
10%
Value1,210 ms
20/100
30%
Value0
100/100
15%
Value15.8 s
6/100
10%
24 ms
99 ms
102 ms
108 ms
95 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Cartodb.com, 53% (33 requests) were made to Cartodb-libs.global.ssl.fastly.net and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (331 ms) relates to the external source Js.hsforms.net.
Page size can be reduced by 662.8 kB (12%)
5.6 MB
5.0 MB
In fact, the total size of Cartodb.com main page is 5.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 82.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 82.8 kB or 81% of the original size.
Potential reduce by 4.8 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. CARTO Db images are well optimized though.
Potential reduce by 575.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 575.1 kB or 55% of the original size.
Potential reduce by 94 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. Cartodb.com has all CSS files already compressed.
Number of requests can be reduced by 24 (46%)
52
28
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CARTO Db. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cartodb.com
24 ms
cartodb.com
99 ms
cartodb.css
102 ms
css
108 ms
vendor.f90ccd42.css
95 ms
main.fe234f4c.css
94 ms
356960264.js
150 ms
v2.js
331 ms
cartodb.js
115 ms
vendor.70b8b4c9.js
104 ms
main.e31fa2e3.js
104 ms
widgets.js
142 ms
conversion.js
99 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
55 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
75 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
63 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
73 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
82 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
86 ms
1920.0bac6db4.jpg
221 ms
1920.b885cd38.jpg
208 ms
1920.ec6c06f2.jpg
214 ms
unicef.00d31498.png
45 ms
google.ee518cf0.png
45 ms
nyc.0b721a16.png
44 ms
twitter.5c241b12.png
46 ms
axa_winterthur.73089a0a.png
46 ms
bbva.559dc40f.png
47 ms
ingdirect.f9807563.png
47 ms
editor.aa28fd4a.png
47 ms
insights.df7d5ba5.gif
217 ms
customize.031794d9.png
210 ms
data_01.8659eef7.png
48 ms
data_02.ec9e2cd9.png
203 ms
data_03.5b2d3c95.png
206 ms
introducing@2x.5983f475.png
211 ms
placeholder.082766c0.png
208 ms
banking-and-finance.1a3a9e34.jpg
207 ms
vulnerability.a5e1c5f0.png
226 ms
la.428dd32a.png
211 ms
jll.37274dc8.png
215 ms
mamatamap.a93141a1.png
216 ms
mamata.39d4fc21.jpg
211 ms
MWC16.bb92dd7f.jpg
212 ms
map.3b9d4188.svg
216 ms
carto-icons.9181b561.woff
178 ms
trackingCode.js
267 ms
loader0.js
267 ms
analytics.js
163 ms
136 ms
474999.js
275 ms
2ed2a125-0e48-4d52-a03c-a1cb90f0433b
160 ms
94b0e72d-70e9-45b3-a694-0543ca004024
154 ms
106 ms
collect
59 ms
9369-171-10-7255.js
50 ms
inspectlet.js
63 ms
__ptq.gif
126 ms
__ptq.gif
109 ms
__ptq.gif
110 ms
application2.js
157 ms
712137870
87 ms
cartodb.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cartodb.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
cartodb.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
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cartodb.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Cartodb.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.
cartodb.com
Open Graph data is detected on the main page of CARTO Db. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: