18 sec in total
7 sec
10 sec
1.1 sec
Welcome to pisos.afys.cat homepage info - get ready to check Pisos AFYS best content for Spain right away, or after learning these important things about pisos.afys.cat
Immobiliària AFYS con multitud de propiedades, pisos , chalet , casas, villas en todas las zonas y localidades, incluyendo toda la provincia de Barcelona
Visit pisos.afys.catWe analyzed Pisos.afys.cat page load time and found that the first response time was 7 sec and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pisos.afys.cat performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value10.7 s
0/100
25%
Value10.3 s
8/100
10%
Value470 ms
61/100
30%
Value0.627
9/100
15%
Value11.4 s
19/100
10%
6971 ms
373 ms
247 ms
259 ms
263 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 66% of them (75 requests) were addressed to the original Pisos.afys.cat, 17% (19 requests) were made to Maps.googleapis.com and 7% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Pisos.afys.cat.
Page size can be reduced by 1.2 MB (44%)
2.7 MB
1.5 MB
In fact, the total size of Pisos.afys.cat main page is 2.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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 190.4 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 41.7 kB, which is 20% 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 190.4 kB or 91% of the original size.
Potential reduce by 102.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. Pisos AFYS images are well optimized though.
Potential reduce by 679.3 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 679.3 kB or 71% of the original size.
Potential reduce by 230.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. Pisos.afys.cat needs all CSS files to be minified and compressed as it can save up to 230.5 kB or 86% of the original size.
Number of requests can be reduced by 53 (50%)
107
54
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pisos AFYS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
pisos.afys.cat
6971 ms
jquery.min.js
373 ms
jqueryCookieGuard.1.0.min.js
247 ms
reset.css
259 ms
auxiliar.css
263 ms
noticias.css
263 ms
auxiliarficha.css
278 ms
detalle.css
392 ms
reauxiliar.css
393 ms
responsive.css
393 ms
settings.css
395 ms
bootstrap.css
555 ms
font-awesome.min.css
489 ms
css
26 ms
placeholders.min.js
499 ms
bootstrap.min.js
515 ms
bootstrap-datepicker.js
523 ms
datepicker.css
521 ms
jquery-easing-1.3.js
606 ms
jquery-transit-modified.js
622 ms
layerslider.transitions.js
645 ms
layerslider.kreaturamedia.jquery.js
661 ms
carrusel.min.js
678 ms
jquery.carouFredSel-6.0.4-packed.js
704 ms
funciones.js
725 ms
cargafotos.js
744 ms
buscador.js
773 ms
calculadora.js
779 ms
jquery.themepunch.revolution.min.js
940 ms
jquery.flexslider.js
844 ms
googleplano.php
224 ms
bandera_11.png
223 ms
bandera_05.png
219 ms
bandera_07.png
221 ms
bandera_09.png
213 ms
bandera_10.png
220 ms
bandera_06.png
301 ms
bandera_15.png
304 ms
bandera_04.png
301 ms
bandera_03.png
301 ms
bandera_02.png
303 ms
bandera_16.png
302 ms
bandera_12.png
401 ms
bandera_01.png
390 ms
logo.png
528 ms
tel.png
415 ms
img_21122015140025.jpg
796 ms
img_21122015140051.jpg
989 ms
img_21122015140306.jpg
1101 ms
sombra.png
570 ms
radio.png
587 ms
large_left2.png
797 ms
large_right2.png
755 ms
large_left.png
794 ms
large_right.png
921 ms
noimage.png
943 ms
realicons.png
984 ms
noimage.jpg
923 ms
mapa.png
1247 ms
lista.png
1075 ms
siguiente.png
1193 ms
ultimo.png
1188 ms
generaCaptcha.php
1195 ms
loading.gif
1246 ms
rss2.jpg
1255 ms
2-1.jpg
699 ms
facebook.jpg
1050 ms
2-1.jpg
633 ms
3-1.jpg
681 ms
2-1.jpg
579 ms
2-1.jpg
734 ms
js
151 ms
twitter.jpg
1047 ms
google.jpg
1077 ms
youtube.jpg
1154 ms
bullet.png
1162 ms
bullet2.png
1208 ms
BfQP1MR3mJNaumtWa4Tizg.ttf
17 ms
fontawesome-webfont.woff
1483 ms
loader.gif
1080 ms
timer.png
1105 ms
common.js
34 ms
util.js
103 ms
geocoder.js
34 ms
map.js
52 ms
marker.js
49 ms
StaticMapService.GetMapImage
255 ms
onion.js
25 ms
ViewportInfoService.GetViewportInfo
45 ms
stats.js
41 ms
controls.js
53 ms
transparent.png
138 ms
css
149 ms
vt
192 ms
vt
95 ms
vt
100 ms
vt
94 ms
vt
95 ms
vt
74 ms
vt
139 ms
izquierda.png
291 ms
derecha.png
358 ms
spotlight-poi.png
17 ms
google4.png
42 ms
mapcnt6.png
43 ms
tmapctrl.png
39 ms
cb_scout5.png
42 ms
tmapctrl4.png
40 ms
imgs8.png
41 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
50 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
53 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
69 ms
AuthenticationService.Authenticate
265 ms
pisos.afys.cat accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
ARIA
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.
Impact
Issue
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pisos.afys.cat best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
pisos.afys.cat SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pisos.afys.cat can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Pisos.afys.cat 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.
pisos.afys.cat
Open Graph description is not detected on the main page of Pisos AFYS. 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: