Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

decide.madrid.es

Decide Madrid: plataforma de participación ciudadana

Page Load Speed

5.2 sec in total

First Response

657 ms

Resources Loaded

4.3 sec

Page Rendered

193 ms

decide.madrid.es screenshot

About Website

Visit decide.madrid.es now to see the best up-to-date Decide Madrid content for Spain and also check out these interesting facts you probably never knew about decide.madrid.es

En la web de participación ciudadana Decide Madrid podrás proponer, apoyar, crear propuestas y decidir en qué gasta el Ayuntamiento su presupuesto.

Visit decide.madrid.es

Key Findings

We analyzed Decide.madrid.es page load time and found that the first response time was 657 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

decide.madrid.es performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.583

11/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

decide.madrid.es

657 ms

application-c188c632fdb2d3f2283f1beaeff91bf982dec4227862960ca1c894f9f92fdf7d.css

681 ms

application-0abeb1f5ae93e99c7d5e65edf09811518fa2293b8951ca754d6e3ab66e30bc05.js

1264 ms

ebOneTag.js

87 ms

visits

1932 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 88% of them (21 requests) were addressed to the original Decide.madrid.es, 4% (1 request) were made to Secure-ds.serving-sys.com and 4% (1 request) were made to Webanalytics01.madrid.es. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Decide.madrid.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.4 kB (68%)

Content Size

217.6 kB

After Optimization

69.3 kB

In fact, the total size of Decide.madrid.es main page is 217.6 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. 25% of websites need less resources to load. CSS take 179.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.9 kB

  • Original 15.9 kB
  • After minification 13.9 kB
  • After compression 5.0 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 2.0 kB, which is 13% 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 10.9 kB or 69% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 21.8 kB
  • After minification 21.8 kB
  • After compression 21.8 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

-76%

Potential reduce by 137.4 kB

  • Original 179.9 kB
  • After minification 178.7 kB
  • After compression 42.4 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. Decide.madrid.es needs all CSS files to be minified and compressed as it can save up to 137.4 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

23

After Optimization

23

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Decide Madrid. According to our analytics all requests are already optimized.

Accessibility Review

decide.madrid.es accessibility score

100

Accessibility Issues

Best Practices

decide.madrid.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

decide.madrid.es SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Decide.madrid.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Decide.madrid.es 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

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