Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

alares.es

Vivofácil | Tienda líder de prestación de servicios para particulares

Page Load Speed

5.3 sec in total

First Response

463 ms

Resources Loaded

4.5 sec

Page Rendered

325 ms

alares.es screenshot

About Website

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

Tienda para particulares para la contratación de prestación de servicios a domicilio, telefónico y online

Visit alares.es

Key Findings

We analyzed Alares.es page load time and found that the first response time was 463 ms and then it took 4.8 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

alares.es performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

alares.es

463 ms

style.css

494 ms

estilos.css

297 ms

cff-style.css

317 ms

font-awesome.min.css

8 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 74% of them (67 requests) were addressed to the original Alares.es, 11% (10 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Alares.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 569.8 kB (33%)

Content Size

1.7 MB

After Optimization

1.2 MB

In fact, the total size of Alares.es main page is 1.7 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. 40% of websites need less resources to load. Images take 976.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 50.0 kB

  • Original 63.3 kB
  • After minification 60.9 kB
  • After compression 13.3 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 50.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 10.4 kB

  • Original 976.5 kB
  • After minification 966.1 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. Alares images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 364.9 kB

  • Original 506.5 kB
  • After minification 460.6 kB
  • After compression 141.7 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 364.9 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 144.6 kB

  • Original 175.0 kB
  • After minification 144.5 kB
  • After compression 30.5 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. Alares.es needs all CSS files to be minified and compressed as it can save up to 144.6 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

89

After Optimization

36

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

Accessibility Review

alares.es accessibility score

82

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

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

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

alares.es best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

alares.es SEO score

93

Search Engine Optimization Advices

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alares.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 Alares.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 data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: