Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

grande.property

Grande Property – global residential and commercial properties and investments

Page Load Speed

1.9 sec in total

First Response

177 ms

Resources Loaded

1.5 sec

Page Rendered

176 ms

grande.property screenshot

About Website

Visit grande.property now to see the best up-to-date Grande content for Hong Kong and also check out these interesting facts you probably never knew about grande.property

Grande Property - your reliable international real estate partner providing global real estate services with a comprehensive approach to buying, investing in,developing and managing new mixed-use deve...

Visit grande.property

Key Findings

We analyzed Grande.property page load time and found that the first response time was 177 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

grande.property performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value18.5 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.661

8/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

grande.property

177 ms

grande.property

218 ms

bootstrap.css

247 ms

style.css

199 ms

css

35 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 84% of them (31 requests) were addressed to the original Grande.property, 5% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (718 ms) belongs to the original domain Grande.property.

Page Optimization Overview & Recommendations

Page size can be reduced by 484.5 kB (10%)

Content Size

4.8 MB

After Optimization

4.3 MB

In fact, the total size of Grande.property main page is 4.8 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. 25% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.8 kB

  • Original 13.0 kB
  • After minification 9.0 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 4.0 kB, which is 31% 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 9.8 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 226.4 kB

  • Original 4.5 MB
  • After minification 4.3 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. Grande images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 123.4 kB

  • Original 166.1 kB
  • After minification 135.2 kB
  • After compression 42.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 123.4 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 124.9 kB

  • Original 147.1 kB
  • After minification 119.3 kB
  • After compression 22.2 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. Grande.property needs all CSS files to be minified and compressed as it can save up to 124.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (31%)

Requests Now

29

After Optimization

20

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

Accessibility Review

grande.property accessibility score

60

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

grande.property 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

grande.property SEO score

72

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

High

Image elements do not have [alt] attributes

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

    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 Grande.property 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 Grande.property 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

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