Tools & Wizards About Us
grandain.it screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

grandain.it

Grandain

Page Load Speed

5.7 sec in total

First Response

908 ms

Resources Loaded

4 sec

Page Rendered

737 ms

grandain.it screenshot

About Website

Welcome to grandain.it homepage info - get ready to check Grandain best content right away, or after learning these important things about grandain.it

Visit grandain.it

Key Findings

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

Performance Metrics

grandain.it performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.358

30/100

15%

TTI (Time to Interactive)

Value6.8 s

56/100

10%

Network Requests Diagram

grandain.it

908 ms

www.grandain.com

57 ms

www.grandain.com

741 ms

style.min.css

444 ms

css

32 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Grandain.it, 64% (32 requests) were made to Grandain.com and 18% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Grandain.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.2 kB (5%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grandain.it main page is 2.2 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. 35% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 59.9 kB

  • Original 74.6 kB
  • After minification 70.2 kB
  • After compression 14.7 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 59.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 31.4 kB

  • Original 2.0 MB
  • After minification 2.0 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. Grandain images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 28 B

  • Original 8.8 kB
  • After minification 8.8 kB
  • After compression 8.7 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.

CSS Optimization

-33%

Potential reduce by 26.9 kB

  • Original 80.7 kB
  • After minification 80.7 kB
  • After compression 53.8 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. Grandain.it needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 33% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

grandain.it

grandain.it

908 ms

www.grandain.com

www.grandain.com

57 ms

www.grandain.com

www.grandain.com

741 ms

style.min.css

style.min.css

444 ms

css

css

32 ms

style.css

style.css

402 ms

font-awesome.min.css

font-awesome.min.css

26 ms

animate.css

animate.css

285 ms

css

css

50 ms

keyboard-links.css

keyboard-links.css

287 ms

style.css

style.css

37 ms

responsive.css

responsive.css

52 ms

jquery.min.js

jquery.min.js

64 ms

jquery-migrate.min.js

jquery-migrate.min.js

75 ms

lightslider.css

lightslider.css

15 ms

custom.js

custom.js

13 ms

navigation.js

navigation.js

25 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

30 ms

theia-sticky-sidebar.js

theia-sticky-sidebar.js

59 ms

SmoothScroll.js

SmoothScroll.js

44 ms

wow.min.js

wow.min.js

62 ms

iframe-api.js

iframe-api.js

70 ms

ultra-custom.js

ultra-custom.js

76 ms

lightslider.js

lightslider.js

80 ms

22d2bcc69f7c0ca645e8badee493cfe5

22d2bcc69f7c0ca645e8badee493cfe5

120 ms

1c47ee11623aff8baca76578883a137d-1400x850.jpg

1c47ee11623aff8baca76578883a137d-1400x850.jpg

106 ms

62e40790d66e40ccc7107a3271255beb-1400x850.jpg

62e40790d66e40ccc7107a3271255beb-1400x850.jpg

817 ms

e7ae5a5604338827ea8c67ee26e3b348-1400x850.jpg

e7ae5a5604338827ea8c67ee26e3b348-1400x850.jpg

316 ms

a5b24c11bb54b58b3b9402a7a100e07b-1400x850.jpg

a5b24c11bb54b58b3b9402a7a100e07b-1400x850.jpg

720 ms

ef6a0f4775d5d75b376fc646eca6567f-1400x850.jpg

ef6a0f4775d5d75b376fc646eca6567f-1400x850.jpg

798 ms

1eabec26962926e12098afd381d0cb5b-1400x850.jpg

1eabec26962926e12098afd381d0cb5b-1400x850.jpg

589 ms

2e7bcab3d1497b98f0c6b5f0f6b79abb-1400x850.jpg

2e7bcab3d1497b98f0c6b5f0f6b79abb-1400x850.jpg

888 ms

c6e61a4ebc6ab5ee9fc3426a79bb791b-1400x850.jpg

c6e61a4ebc6ab5ee9fc3426a79bb791b-1400x850.jpg

589 ms

e726cf2eb6c81b785b3a01222817b0b7-1280x850.jpg

e726cf2eb6c81b785b3a01222817b0b7-1280x850.jpg

1235 ms

9562b9519d6b6b23f761afedac2cdbfa-1400x850.jpg

9562b9519d6b6b23f761afedac2cdbfa-1400x850.jpg

861 ms

9d80e8087515567d211c5c7563ba4552

9d80e8087515567d211c5c7563ba4552

103 ms

74755e296f585b722a07c9af23a984ed

74755e296f585b722a07c9af23a984ed

103 ms

fc5c52a1bfab52fabfd0a961de8e25c5

fc5c52a1bfab52fabfd0a961de8e25c5

145 ms

6adc732ee2a4cf5060c5163df60891db

6adc732ee2a4cf5060c5163df60891db

148 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

74 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

82 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

100 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

108 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

108 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

108 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

107 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

108 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

106 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1220 ms

www-widgetapi.js

www-widgetapi.js

76 ms

Accessibility Review

grandain.it accessibility score

88

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

grandain.it best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

grandain.it SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    IT

  • Language Claimed

    IT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandain.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Grandain.it 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

grandain.it

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