Report Summary

  • 15

    Performance

    Renders faster than
    27% 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

  • 72

    SEO

    Google-friendlier than
    31% of websites

embalses.net

Embalses.net - Estado de los Embalses, pantanos y presas de España

Page Load Speed

1.8 sec in total

First Response

246 ms

Resources Loaded

1.4 sec

Page Rendered

207 ms

embalses.net screenshot

About Website

Welcome to embalses.net homepage info - get ready to check Embalses best content for Spain right away, or after learning these important things about embalses.net

Consulta el nivel de los embalses de españa, la capacidad de los pantanos, el estado actual de los embalses, cual es la situacion de los embalses y grandes presas, comprueba los pantanos de tu provinc...

Visit embalses.net

Key Findings

We analyzed Embalses.net page load time and found that the first response time was 246 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

embalses.net performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

24/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value5,040 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.494

17/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

embalses.net

246 ms

www.embalses.net

569 ms

embalses.css

191 ms

js

58 ms

cookieconsent.min.js

38 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 46% of them (12 requests) were addressed to the original Embalses.net, 8% (2 requests) were made to Googletagmanager.com and 8% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (569 ms) belongs to the original domain Embalses.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.2 kB (28%)

Content Size

430.5 kB

After Optimization

311.3 kB

In fact, the total size of Embalses.net main page is 430.5 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. 30% of websites need less resources to load. Javascripts take 289.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 80.5 kB

  • Original 99.1 kB
  • After minification 71.2 kB
  • After compression 18.6 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 27.9 kB, which is 28% 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 80.5 kB or 81% of the original size.

Image Optimization

-15%

Potential reduce by 5.9 kB

  • Original 38.5 kB
  • After minification 32.6 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. Obviously, Embalses needs image optimization as it can save up to 5.9 kB 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

-11%

Potential reduce by 32.2 kB

  • Original 289.7 kB
  • After minification 289.7 kB
  • After compression 257.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 32.2 kB or 11% of the original size.

CSS Optimization

-19%

Potential reduce by 602 B

  • Original 3.2 kB
  • After minification 3.2 kB
  • After compression 2.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. Embalses.net needs all CSS files to be minified and compressed as it can save up to 602 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (33%)

Requests Now

24

After Optimization

16

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

Accessibility Review

embalses.net 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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

embalses.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

embalses.net SEO score

72

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 doesn't use 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 Embalses.net 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 Embalses.net 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 data is detected on the main page of Embalses. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: