Tools & Wizards About Us
urbecan.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

urbecan.com

Pisos en La Orotava | Inmobiliarias La Orotava |Century 21 Urbecan

Page Load Speed

16 sec in total

First Response

692 ms

Resources Loaded

14.7 sec

Page Rendered

599 ms

urbecan.com screenshot

About Website

Click here to check amazing Urbecan content. Otherwise, check out these important facts you probably never knew about urbecan.com

Century 21 Urbecan con multitud de propiedades, pisos , chalet , casas, villas en todas las zonas y localidades, incluyendo toda la provincia de Sc De Tenerife

Visit urbecan.com

Key Findings

We analyzed Urbecan.com page load time and found that the first response time was 692 ms and then it took 15.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

urbecan.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

urbecan.com

692 ms

www.urbecan.com

9905 ms

jquery.min.js

395 ms

jqueryCookieGuard.1.0.min.js

259 ms

reset.css

278 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 59% of them (69 requests) were addressed to the original Urbecan.com, 25% (29 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (9.9 sec) belongs to the original domain Urbecan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (49%)

Content Size

2.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Urbecan.com main page is 2.4 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. Javascripts take 964.8 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 201.3 kB

  • Original 223.3 kB
  • After minification 180.3 kB
  • After compression 22.0 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 43.0 kB, which is 19% 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 201.3 kB or 90% of the original size.

Image Optimization

-7%

Potential reduce by 72.2 kB

  • Original 964.8 kB
  • After minification 892.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. Urbecan images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 677.4 kB

  • Original 964.8 kB
  • After minification 904.4 kB
  • After compression 287.5 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 677.4 kB or 70% of the original size.

CSS Optimization

-85%

Potential reduce by 219.2 kB

  • Original 256.5 kB
  • After minification 200.9 kB
  • After compression 37.3 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. Urbecan.com needs all CSS files to be minified and compressed as it can save up to 219.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (59%)

Requests Now

114

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

urbecan.com

urbecan.com

692 ms

www.urbecan.com

www.urbecan.com

9905 ms

jquery.min.js

jquery.min.js

395 ms

jqueryCookieGuard.1.0.min.js

jqueryCookieGuard.1.0.min.js

259 ms

reset.css

reset.css

278 ms

auxiliar.css

auxiliar.css

260 ms

auxiliarficha.css

auxiliarficha.css

265 ms

detalle.css

detalle.css

416 ms

responsive.css

responsive.css

500 ms

settings.css

settings.css

522 ms

bootstrap.css

bootstrap.css

626 ms

font-awesome.min.css

font-awesome.min.css

536 ms

css

css

25 ms

placeholders.min.js

placeholders.min.js

668 ms

bootstrap.min.js

bootstrap.min.js

678 ms

bootstrap-datepicker.js

bootstrap-datepicker.js

761 ms

datepicker.css

datepicker.css

773 ms

jquery-easing-1.3.js

jquery-easing-1.3.js

787 ms

jquery-transit-modified.js

jquery-transit-modified.js

901 ms

layerslider.transitions.js

layerslider.transitions.js

942 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

1142 ms

carrusel.min.js

carrusel.min.js

1011 ms

jquery.carouFredSel-6.0.4-packed.js

jquery.carouFredSel-6.0.4-packed.js

1042 ms

funciones.js

funciones.js

1051 ms

cargafotos.js

cargafotos.js

1163 ms

buscador.js

buscador.js

1216 ms

calculadora.js

calculadora.js

1268 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1454 ms

jquery.flexslider.js

jquery.flexslider.js

1316 ms

googleplano.php

googleplano.php

167 ms

bandera_11.png

bandera_11.png

280 ms

bandera_05.png

bandera_05.png

278 ms

bandera_07.png

bandera_07.png

277 ms

bandera_15.png

bandera_15.png

279 ms

bandera_04.png

bandera_04.png

278 ms

bandera_03.png

bandera_03.png

419 ms

bandera_02.png

bandera_02.png

526 ms

bandera_16.png

bandera_16.png

525 ms

bandera_12.png

bandera_12.png

528 ms

bandera_01.png

bandera_01.png

526 ms

logo4.gif

logo4.gif

578 ms

tel.png

tel.png

709 ms

15616648_ml.jpg

15616648_ml.jpg

1266 ms

7681089_ml.jpg

7681089_ml.jpg

1063 ms

12803584_ml.jpg

12803584_ml.jpg

1304 ms

imagen.jpg

imagen.jpg

1326 ms

sombra.png

sombra.png

819 ms

radio.png

radio.png

974 ms

large_left2.png

large_left2.png

1083 ms

large_right2.png

large_right2.png

1256 ms

large_left.png

large_left.png

1325 ms

large_right.png

large_right.png

1369 ms

noimage.png

noimage.png

1503 ms

realicons.png

realicons.png

1519 ms

mapa.png

mapa.png

1700 ms

lista.png

lista.png

1582 ms

siguiente.png

siguiente.png

1590 ms

ultimo.png

ultimo.png

1592 ms

logo.png

logo.png

1758 ms

generaCaptcha.php

generaCaptcha.php

1785 ms

loading.gif

loading.gif

1834 ms

rss2.jpg

rss2.jpg

2001 ms

1-1.jpg

1-1.jpg

637 ms

noimage.jpg

noimage.jpg

1900 ms

bullet.png

bullet.png

1895 ms

bullet2.png

bullet2.png

1915 ms

2-1.jpg

2-1.jpg

684 ms

1-1.jpg

1-1.jpg

910 ms

8-1.jpg

8-1.jpg

713 ms

3-1.jpg

3-1.jpg

622 ms

js

js

96 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2287 ms

loader.gif

loader.gif

1826 ms

timer.png

timer.png

2011 ms

nr-892.min.js

nr-892.min.js

70 ms

common.js

common.js

15 ms

util.js

util.js

25 ms

geocoder.js

geocoder.js

33 ms

map.js

map.js

26 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

55 ms

onion.js

onion.js

14 ms

openhand_8_8.cur

openhand_8_8.cur

57 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

269 ms

GeocodeService.Search

GeocodeService.Search

104 ms

stats.js

stats.js

19 ms

controls.js

controls.js

15 ms

6bb349bd3d

6bb349bd3d

76 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

28 ms

css

css

87 ms

transparent.png

transparent.png

34 ms

marker.js

marker.js

28 ms

google4.png

google4.png

32 ms

mapcnt6.png

mapcnt6.png

46 ms

tmapctrl.png

tmapctrl.png

37 ms

cb_scout5.png

cb_scout5.png

43 ms

tmapctrl4.png

tmapctrl4.png

42 ms

imgs8.png

imgs8.png

37 ms

vt

vt

15 ms

vt

vt

15 ms

vt

vt

15 ms

vt

vt

20 ms

vt

vt

19 ms

vt

vt

19 ms

vt

vt

17 ms

vt

vt

16 ms

vt

vt

28 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

82 ms

spotlight-poi.png

spotlight-poi.png

13 ms

vt

vt

39 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

30 ms

vt

vt

46 ms

vt

vt

36 ms

vt

vt

49 ms

vt

vt

41 ms

izquierda.png

izquierda.png

909 ms

derecha.png

derecha.png

927 ms

Accessibility Review

urbecan.com accessibility score

70

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

urbecan.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

urbecan.com SEO score

83

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

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Urbecan.com 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 Urbecan.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

urbecan.com

Open Graph description is not detected on the main page of Urbecan. 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: