5.2 sec in total
455 ms
3.9 sec
825 ms
Click here to check amazing Living content. Otherwise, check out these important facts you probably never knew about living.es
Somos expertos en el arte de alquilar, vender y comprar casas de lujo en Barcelona. Descubre y únete a una colección de locales, pisos y casas singulares.
Visit living.esWe analyzed Living.es page load time and found that the first response time was 455 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
living.es performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value4.9 s
28/100
25%
Value8.2 s
20/100
10%
Value1,330 ms
17/100
30%
Value0.056
98/100
15%
Value16.9 s
5/100
10%
455 ms
800 ms
15 ms
482 ms
337 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 62% of them (41 requests) were addressed to the original Living.es, 5% (3 requests) were made to Google.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Living.es.
Page size can be reduced by 84.9 kB (18%)
480.8 kB
395.9 kB
In fact, the total size of Living.es main page is 480.8 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. 55% of websites need less resources to load. Javascripts take 293.4 kB which makes up the majority of the site volume.
Potential reduce by 80.1 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 20.9 kB, which is 21% 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.1 kB or 80% of the original size.
Potential reduce by 4.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. This website has mostly compressed JavaScripts.
Potential reduce by 200 B
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. Living.es has all CSS files already compressed.
Number of requests can be reduced by 31 (53%)
59
28
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Living. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
living.es
455 ms
www.living.es
800 ms
tp.widget.bootstrap.min.js
15 ms
style.min.css
482 ms
living-logo.svg
337 ms
video-home.webp
360 ms
vistas.svg
334 ms
oasis.svg
343 ms
arte.svg
346 ms
academic.svg
354 ms
city-life.svg
492 ms
business.svg
493 ms
panot.webp
685 ms
dossier.webp
705 ms
grafica.webp
828 ms
prop0.webp
1077 ms
prop1.webp
1119 ms
prop2.webp
1344 ms
prop3.webp
1025 ms
comodidad.webp
940 ms
icon_stars_5.svg
947 ms
icon_stars_4_5.svg
1058 ms
jquery.min.js
30 ms
main.min.js
1080 ms
webcomponents-loader.js
1138 ms
homeSearch.js
1177 ms
coreValidarForm.js
1197 ms
oficinas.js
1199 ms
form-listado.js
1229 ms
coreCookies.js
1253 ms
element.js
56 ms
js
59 ms
custom-elements-es5-adapter.js
1295 ms
21862.js
487 ms
logo-white.svg
1317 ms
icon-search.svg
902 ms
home_img1.webp
928 ms
consultor.webp
1066 ms
montserrat-regular.woff
1173 ms
montserrat-medium.woff
943 ms
montserrat-bold.woff
1198 ms
donpiso.woff
964 ms
fa-brands-400.ttf
976 ms
webcomponents-sd-ce-pf.js
420 ms
gtm.js
111 ms
analytics.js
79 ms
fbevents.js
91 ms
prop0.webp
517 ms
prop3.webp
129 ms
collect
56 ms
collect
117 ms
70 ms
collect
367 ms
uwt.js
319 ms
insight.min.js
320 ms
bat.js
307 ms
axew5oj3j8
346 ms
aca1fa55-13c4-4e4b-94d7-7d2cf17d5286
721 ms
js
67 ms
collect
27 ms
313 ms
ga-audiences
311 ms
adsct
178 ms
adsct
95 ms
ga-audiences
27 ms
clarity.js
28 ms
living.es accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
living.es 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
living.es 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Living.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 Living.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.
living.es
Open Graph data is detected on the main page of Living. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: