Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

elespinar.es

Inicio - Ayuntamiento de El Espinar - elespinar.es - Municipio de El Espinar - Segovia - España

Page Load Speed

19.1 sec in total

First Response

333 ms

Resources Loaded

18.8 sec

Page Rendered

2 ms

About Website

Welcome to elespinar.es homepage info - get ready to check El Espinar best content for Spain right away, or after learning these important things about elespinar.es

Página web del Ayuntamiento del Municipio de El Espinar con información sobre sus núcleos: El Espinar, San Rafael, Los Ángeles de San Rafael, La Estación de El Espinar, Gudillos y Prados

Visit elespinar.es

Key Findings

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

Performance Metrics

elespinar.es performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value35.0 s

0/100

25%

SI (Speed Index)

Value38.6 s

0/100

10%

TBT (Total Blocking Time)

Value4,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value52.1 s

0/100

10%

Network Requests Diagram

elespinar.es

333 ms

www.elespinar.es

4403 ms

widgetkit-408f7555.css

237 ms

mootools-core.js

628 ms

core.js

265 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 77% of them (57 requests) were addressed to the original Elespinar.es, 8% (6 requests) were made to Aemet.es and 7% (5 requests) were made to Bandomovil.com. The less responsive or slowest element that took the longest time to load (10.8 sec) relates to the external source Bandomovil.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.8 kB (12%)

Content Size

1.5 MB

After Optimization

1.3 MB

In fact, the total size of Elespinar.es main page is 1.5 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 43.4 kB

  • Original 54.3 kB
  • After minification 48.5 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 5.8 kB, which is 11% 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 43.4 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 106.4 kB

  • Original 1.1 MB
  • After minification 1.0 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. El Espinar images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.4 kB

  • Original 262.3 kB
  • After minification 262.1 kB
  • After compression 253.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

-59%

Potential reduce by 21.6 kB

  • Original 36.5 kB
  • After minification 34.5 kB
  • After compression 14.8 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. Elespinar.es needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (31%)

Requests Now

70

After Optimization

48

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

Accessibility Review

elespinar.es accessibility score

76

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

elespinar.es best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

elespinar.es SEO score

54

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

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 Elespinar.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 Elespinar.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 El Espinar. 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: