Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

alpiso.net

Venta de pisos en Bilbao - alPiso.net - San Sebastian - Vitoria-Gasteiz - Pamplona - Euskadi - Navarra

Page Load Speed

2.8 sec in total

First Response

124 ms

Resources Loaded

2 sec

Page Rendered

676 ms

alpiso.net screenshot

About Website

Welcome to alpiso.net homepage info - get ready to check AlPiso best content right away, or after learning these important things about alpiso.net

Venta de pisos en Bilbao - alPiso.net - San Sebastian - Vitoria-Gasteiz - Pamplona - Euskadi - Navarra

Visit alpiso.net

Key Findings

We analyzed Alpiso.net page load time and found that the first response time was 124 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

alpiso.net performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value1.3 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

www.popfloor.co

124 ms

css

30 ms

bootstrap.css

144 ms

style.css

35 ms

dark.css

85 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Alpiso.net, 17% (8 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (868 ms) relates to the external source Popfloor.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (67%)

Content Size

1.7 MB

After Optimization

550.5 kB

In fact, the total size of Alpiso.net 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. 70% of websites need less resources to load. Javascripts take 697.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 29.9 kB

  • Original 34.7 kB
  • After minification 29.1 kB
  • After compression 4.8 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.6 kB, which is 16% 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 29.9 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 15.3 kB

  • Original 290.9 kB
  • After minification 275.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. AlPiso images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 507.1 kB

  • Original 697.7 kB
  • After minification 664.9 kB
  • After compression 190.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 507.1 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 580.9 kB

  • Original 660.4 kB
  • After minification 516.5 kB
  • After compression 79.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. Alpiso.net needs all CSS files to be minified and compressed as it can save up to 580.9 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

24

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

Accessibility Review

alpiso.net accessibility score

64

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

alpiso.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

SEO Factors

alpiso.net SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alpiso.net can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Alpiso.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 description is not detected on the main page of AlPiso. 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: