Access aytovillablino.com. Web Oficial Ayuntamiento de Villablino, Valle de Laciana.

name

value

score

weighting

FCP (First Contentful Paint)

Value17.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value29.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,400 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value38.2 s

0/100

10%

www.aytovillablino.com

753 ms

wp-emoji-release.min.js

225 ms

embed-pdf-viewer.css

334 ms

style.min.css

443 ms

style.css

334 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 77% of them (107 requests) were addressed to the original Aytovillablino.com, 5% (7 requests) were made to Aemet.es and 4% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Accuweather.com.

Content Size

6.1 MB

After Optimization

2.9 MB

In fact, the total size of Aytovillablino.com main page is 6.1 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. Only a small number of websites need less resources to load. CSS take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 175.4 kB

Original 215.2 kB
After minification 210.7 kB
After compression 39.7 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 175.4 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 54.7 kB

Original 2.0 MB
After minification 1.9 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. Ayto Villablino images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 1.0 MB

Original 1.6 MB
After minification 1.5 MB
After compression 572.6 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 1.0 MB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 2.0 MB

Original 2.3 MB
After minification 2.3 MB
After compression 367.9 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. Aytovillablino.com needs all CSS files to be minified and compressed as it can save up to 2.0 MB or 84% of the original size.

Requests Now

128

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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.

High

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

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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 Aytovillablino.com 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 Aytovillablino.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.

Social Sharing Optimization

Open Graph data is detected on the main page of Ayto Villablino. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: