Tools & Wizards About Us
map.fiware.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

map.fiware.org

CARTO | Location Intelligence & GIS for Cloud Natives

Page Load Speed

3.3 sec in total

First Response

421 ms

Resources Loaded

2.3 sec

Page Rendered

580 ms

map.fiware.org screenshot

About Website

Click here to check amazing Map Fiware content for Belgium. Otherwise, check out these important facts you probably never knew about map.fiware.org

Cloud-native location intelligence & GIS software for analysts, data scientists & developers solving geospatial problems with modern analytics stacks.

Visit map.fiware.org

Key Findings

We analyzed Map.fiware.org page load time and found that the first response time was 421 ms and then it took 2.9 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

map.fiware.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

map.fiware.org

421 ms

styles.min.css

202 ms

cartodb.css

45 ms

cartodb.js

143 ms

main.min.js

570 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 6% of them (9 requests) were addressed to the original Map.fiware.org, 28% (40 requests) were made to Cartocdn-ashbu.global.ssl.fastly.net and 10% (14 requests) were made to Cartodb-basemaps-c.global.ssl.fastly.net. The less responsive or slowest element that took the longest time to load (620 ms) relates to the external source Cartodb-basemaps-a.global.ssl.fastly.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 765.9 kB (54%)

Content Size

1.4 MB

After Optimization

644.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Map.fiware.org main page is 1.4 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. 45% of websites need less resources to load. Javascripts take 934.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 83.3 kB

  • Original 96.8 kB
  • After minification 95.7 kB
  • After compression 13.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. 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 83.3 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 21.1 kB

  • Original 365.3 kB
  • After minification 344.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. Map Fiware images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 661.4 kB

  • Original 934.8 kB
  • After minification 934.8 kB
  • After compression 273.4 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 661.4 kB or 71% of the original size.

CSS Optimization

-0%

Potential reduce by 62 B

  • Original 13.7 kB
  • After minification 13.7 kB
  • After compression 13.6 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. Map.fiware.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 75 (53%)

Requests Now

142

After Optimization

67

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

map.fiware.org

map.fiware.org

421 ms

styles.min.css

styles.min.css

202 ms

cartodb.css

cartodb.css

45 ms

cartodb.js

cartodb.js

143 ms

main.min.js

main.min.js

570 ms

fiware_img.svg

fiware_img.svg

469 ms

fiwaremaps_logo.svg

fiwaremaps_logo.svg

172 ms

cartodb_sprt_zoom.svg

cartodb_sprt_zoom.svg

165 ms

new_logo.png

new_logo.png

137 ms

CP_logo_geographica.svg

CP_logo_geographica.svg

166 ms

neotechstd-medium-webfont.woff

neotechstd-medium-webfont.woff

481 ms

analytics.js

analytics.js

13 ms

collect

collect

19 ms

11.png

11.png

202 ms

10.png

10.png

260 ms

11.png

11.png

208 ms

sql

sql

222 ms

11.png

11.png

225 ms

12.png

12.png

224 ms

11.png

11.png

620 ms

13.png

13.png

242 ms

9.png

9.png

308 ms

12.png

12.png

243 ms

9.png

9.png

243 ms

10.png

10.png

315 ms

10.png

10.png

316 ms

13.png

13.png

317 ms

13.png

13.png

366 ms

12.png

12.png

122 ms

10.png

10.png

137 ms

9.png

9.png

122 ms

11.png

11.png

137 ms

10.png

10.png

161 ms

13.png

13.png

137 ms

13.png

13.png

125 ms

12.png

12.png

135 ms

12.png

12.png

174 ms

9.png

9.png

161 ms

9.png

9.png

175 ms

10.png

10.png

123 ms

12.png

12.png

112 ms

9.png

9.png

127 ms

10.png

10.png

125 ms

12.png

12.png

541 ms

13.png

13.png

126 ms

9.png

9.png

157 ms

13.png

13.png

158 ms

11.png

11.png

170 ms

11.png

11.png

148 ms

viz.json

viz.json

128 ms

11.png

11.png

310 ms

10.png

10.png

133 ms

13.png

13.png

133 ms

12.png

12.png

114 ms

9.png

9.png

140 ms

new_logo.png

new_logo.png

110 ms

map

map

43 ms

neotechstd-medium-webfont.woff

neotechstd-medium-webfont.woff

424 ms

map

map

194 ms

loader.gif

loader.gif

28 ms

jsonp

jsonp

66 ms

other.png

other.png

41 ms

sql

sql

30 ms

11.png

11.png

233 ms

11.png

11.png

218 ms

10.png

10.png

240 ms

10.png

10.png

257 ms

12.png

12.png

245 ms

12.png

12.png

256 ms

11.png

11.png

261 ms

11.png

11.png

253 ms

10.png

10.png

257 ms

10.png

10.png

285 ms

12.png

12.png

283 ms

12.png

12.png

293 ms

9.png

9.png

294 ms

9.png

9.png

294 ms

13.png

13.png

297 ms

13.png

13.png

296 ms

9.png

9.png

297 ms

9.png

9.png

295 ms

11.png

11.png

303 ms

11.png

11.png

294 ms

13.png

13.png

312 ms

13.png

13.png

310 ms

10.png

10.png

304 ms

10.png

10.png

305 ms

12.png

12.png

305 ms

12.png

12.png

317 ms

9.png

9.png

333 ms

9.png

9.png

330 ms

13.png

13.png

336 ms

13.png

13.png

344 ms

11.png

11.png

333 ms

11.png

11.png

350 ms

10.png

10.png

349 ms

10.png

10.png

346 ms

12.png

12.png

353 ms

12.png

12.png

349 ms

11.png

11.png

131 ms

11.png

11.png

75 ms

10.png

10.png

110 ms

12.png

12.png

128 ms

11.png

11.png

73 ms

12.png

12.png

102 ms

9.png

9.png

72 ms

13.png

13.png

61 ms

11.png

11.png

97 ms

12.png

12.png

96 ms

10.png

10.png

97 ms

9.png

9.png

96 ms

13.png

13.png

99 ms

11.png

11.png

139 ms

10.png

10.png

115 ms

9.png

9.png

136 ms

13.png

13.png

137 ms

11.png

11.png

392 ms

10.png

10.png

147 ms

12.png

12.png

174 ms

9.png

9.png

175 ms

13.png

13.png

177 ms

10.png

10.png

87 ms

12.png

12.png

97 ms

9.png

9.png

139 ms

13.png

13.png

128 ms

12.png

12.png

97 ms

9.png

9.png

127 ms

13.png

13.png

152 ms

11.png

11.png

135 ms

10.png

10.png

147 ms

12.png

12.png

39 ms

10.png

10.png

30 ms

9.png

9.png

38 ms

13.png

13.png

36 ms

10.png

10.png

37 ms

9.png

9.png

80 ms

13.png

13.png

76 ms

11.png

11.png

75 ms

12.png

12.png

75 ms

map.fiware.org

map.fiware.org

238 ms

9.png

9.png

151 ms

9.png

9.png

156 ms

13.png

13.png

157 ms

neotechstd-medium-webfont.woff

neotechstd-medium-webfont.woff

569 ms

13.png

13.png

174 ms

Accessibility Review

map.fiware.org accessibility score

65

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

map.fiware.org 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

map.fiware.org SEO score

79

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

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

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 Map.fiware.org 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 Map.fiware.org 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

map.fiware.org

Open Graph description is not detected on the main page of Map Fiware. 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: