Tools & Wizards About Us
cortijolaloma.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

cortijolaloma.com

Casas rurales Alpujarra, Cortijo en Pitres, Granada – Cortijo La Loma

Page Load Speed

5.8 sec in total

First Response

569 ms

Resources Loaded

4.9 sec

Page Rendered

324 ms

cortijolaloma.com screenshot

About Website

Welcome to cortijolaloma.com homepage info - get ready to check Cortijo La Loma best content right away, or after learning these important things about cortijolaloma.com

El Cortijo la Loma de la Alpujarra ofrece unas vistas impresionantes a las montañas de La Alpujarra y una piscina al aire libre. En el pueblo de Pitres

Visit cortijolaloma.com

Key Findings

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

Performance Metrics

cortijolaloma.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value29,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value44.3 s

0/100

10%

Network Requests Diagram

www.cortijolaloma.com

569 ms

language-selector.css

82 ms

shortcodes.css

162 ms

style.css

167 ms

orange.css

173 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 58% of them (51 requests) were addressed to the original Cortijolaloma.com, 11% (10 requests) were made to Maps.googleapis.com and 8% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Cortijolaloma.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (37%)

Content Size

3.9 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cortijolaloma.com main page is 3.9 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 30.5 kB

  • Original 38.4 kB
  • After minification 37.7 kB
  • After compression 7.9 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 30.5 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 133.3 kB

  • Original 2.0 MB
  • After minification 1.9 MB

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. Cortijo La Loma images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 1.1 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 504.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 1.1 MB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 136.6 kB

  • Original 162.1 kB
  • After minification 133.3 kB
  • After compression 25.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. Cortijolaloma.com needs all CSS files to be minified and compressed as it can save up to 136.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (56%)

Requests Now

82

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cortijo La Loma. 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 from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.cortijolaloma.com

www.cortijolaloma.com

569 ms

language-selector.css

language-selector.css

82 ms

shortcodes.css

shortcodes.css

162 ms

style.css

style.css

167 ms

orange.css

orange.css

173 ms

prettyPhoto.css

prettyPhoto.css

191 ms

styles.css

styles.css

193 ms

jquery.js

jquery.js

289 ms

jquery-migrate.min.js

jquery-migrate.min.js

242 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

243 ms

custom.js

custom.js

330 ms

cufon-yui.js

cufon-yui.js

246 ms

colaboratelight.js

colaboratelight.js

345 ms

sitepress.js

sitepress.js

329 ms

jquery-ui.css

jquery-ui.css

327 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

343 ms

jquery.form.min.js

jquery.form.min.js

381 ms

scripts.js

scripts.js

411 ms

wp-embed.min.js

wp-embed.min.js

410 ms

ui.datepicker.js

ui.datepicker.js

408 ms

ui.datepicker-es.js

ui.datepicker-es.js

439 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

315 ms

preloader.png

preloader.png

258 ms

transparent.gif

transparent.gif

258 ms

fondo.jpg

fondo.jpg

617 ms

header.png

header.png

307 ms

es.png

es.png

246 ms

en.png

en.png

246 ms

facebook.png

facebook.png

251 ms

black10.png

black10.png

249 ms

thumb.php

thumb.php

870 ms

thumb.php

thumb.php

1055 ms

thumb.php

thumb.php

1128 ms

thumb.php

thumb.php

883 ms

exterior005_r2_c15.jpg

exterior005_r2_c15.jpg

615 ms

exterior005_r2_c14.jpg

exterior005_r2_c14.jpg

883 ms

thumb.php

thumb.php

835 ms

image_shadow.png

image_shadow.png

866 ms

thumb.php

thumb.php

1052 ms

thumb.php

thumb.php

1052 ms

thumb.php

thumb.php

2073 ms

full.png

full.png

1260 ms

staged.png

staged.png

1193 ms

intro_bottom.png

intro_bottom.png

1192 ms

intro_title.png

intro_title.png

1191 ms

content_top.png

content_top.png

1192 ms

maps

maps

214 ms

line.gif

line.gif

1298 ms

outro.png

outro.png

1298 ms

black53.png

black53.png

1299 ms

nivo_arrows.png

nivo_arrows.png

1188 ms

nav_dots_sprite.png

nav_dots_sprite.png

1225 ms

embed

embed

38 ms

js

js

94 ms

init_embed.js

init_embed.js

46 ms

common.js

common.js

16 ms

util.js

util.js

54 ms

streetview.js

streetview.js

49 ms

google_white4.png

google_white4.png

14 ms

marker.js

marker.js

44 ms

imagery_viewer.js

imagery_viewer.js

94 ms

controls.js

controls.js

10 ms

GeoPhotoService.GetMetadata

GeoPhotoService.GetMetadata

84 ms

transparent.png

transparent.png

59 ms

css

css

274 ms

geocoder.js

geocoder.js

119 ms

sv4.png

sv4.png

222 ms

openhand_8_8.cur

openhand_8_8.cur

256 ms

mapcnt6.png

mapcnt6.png

146 ms

tmapctrl.png

tmapctrl.png

147 ms

cbk

cbk

44 ms

GeoPhotoService.GetMetadata

GeoPhotoService.GetMetadata

56 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

189 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

245 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

245 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

245 ms

cbk

cbk

87 ms

cbk

cbk

302 ms

cbk

cbk

251 ms

cbk

cbk

187 ms

cbk

cbk

299 ms

cbk

cbk

333 ms

cbk

cbk

92 ms

cbk

cbk

201 ms

cbk

cbk

330 ms

cbk

cbk

329 ms

cbk

cbk

364 ms

cbk

cbk

88 ms

Accessibility Review

cortijolaloma.com accessibility score

91

Accessibility Issues

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

cortijolaloma.com best practices score

67

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

Page has valid source maps

SEO Factors

cortijolaloma.com SEO score

90

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

High

Tap targets are not sized appropriately

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 Cortijolaloma.com 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 Cortijolaloma.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

cortijolaloma.com

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