Tools & Wizards About Us
griante.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

griante.com

Griante - Lake Como / Lago di Como - Home

Page Load Speed

847 ms in total

First Response

161 ms

Resources Loaded

577 ms

Page Rendered

109 ms

griante.com screenshot

About Website

Welcome to griante.com homepage info - get ready to check Griante best content right away, or after learning these important things about griante.com

this is a website description...

Visit griante.com

Key Findings

We analyzed Griante.com page load time and found that the first response time was 161 ms and then it took 686 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

griante.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value3.8 s

85/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

griante.com

161 ms

analytics.js

21 ms

autotrack.js

69 ms

main.css

81 ms

menu.css

247 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 88% of them (35 requests) were addressed to the original Griante.com, 8% (3 requests) were made to Googletagmanager.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (247 ms) belongs to the original domain Griante.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 390.7 kB (53%)

Content Size

731.2 kB

After Optimization

340.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Griante.com main page is 731.2 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. 30% of websites need less resources to load. Javascripts take 461.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 10.0 kB

  • Original 13.2 kB
  • After minification 11.4 kB
  • After compression 3.2 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 1.8 kB, which is 14% 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 10.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 264 B

  • Original 211.4 kB
  • After minification 211.1 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. Griante images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 342.1 kB

  • Original 461.9 kB
  • After minification 386.8 kB
  • After compression 119.8 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 342.1 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 38.4 kB

  • Original 44.7 kB
  • After minification 34.3 kB
  • After compression 6.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. Griante.com needs all CSS files to be minified and compressed as it can save up to 38.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (57%)

Requests Now

35

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

griante.com

griante.com

161 ms

analytics.js

analytics.js

21 ms

autotrack.js

autotrack.js

69 ms

main.css

main.css

81 ms

menu.css

menu.css

247 ms

template_griante.css

template_griante.css

80 ms

menu_griante.css

menu_griante.css

37 ms

fonts.css

fonts.css

108 ms

content_griante.css

content_griante.css

56 ms

lightbox.css

lightbox.css

88 ms

mailchimp.css

mailchimp.css

102 ms

bookings.css

bookings.css

95 ms

main.js

main.js

108 ms

js_banner.php

js_banner.php

108 ms

main.js

main.js

119 ms

bookings-dependant.js

bookings-dependant.js

131 ms

bookings.js

bookings.js

150 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

176 ms

mootools-core-1.4.5-full-nocompat.js

mootools-core-1.4.5-full-nocompat.js

220 ms

lightbox.js

lightbox.js

177 ms

prototype.js

prototype.js

188 ms

mailing-list.js

mailing-list.js

164 ms

collect

collect

14 ms

js

js

64 ms

back_03.gif

back_03.gif

78 ms

griantelogo_large.gif

griantelogo_large.gif

78 ms

026.jpg

026.jpg

93 ms

feature_home_todo.jpg

feature_home_todo.jpg

83 ms

feature_home_villas.jpg

feature_home_villas.jpg

78 ms

vecchiatorre_01.jpg

vecchiatorre_01.jpg

78 ms

feature_home_seasons.jpg

feature_home_seasons.jpg

79 ms

feature_home_accommodations.jpg

feature_home_accommodations.jpg

80 ms

join.jpg

join.jpg

79 ms

gtm.js

gtm.js

75 ms

gtm.js

gtm.js

49 ms

loading.gif

loading.gif

24 ms

close.png

close.png

31 ms

aleo-light-webfont.woff

aleo-light-webfont.woff

64 ms

sourcesanspro-light-webfont.woff

sourcesanspro-light-webfont.woff

39 ms

aleo-regular-webfont.woff

aleo-regular-webfont.woff

55 ms

Accessibility Review

griante.com accessibility score

92

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

griante.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

griante.com SEO score

67

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Griante.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Griante.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

griante.com

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