Tools & Wizards About Us
gree.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

gree.com

珠海格力电器股份有限公司网站

Page Load Speed

10.9 sec in total

First Response

935 ms

Resources Loaded

9.6 sec

Page Rendered

336 ms

gree.com screenshot

About Website

Click here to check amazing Gree content for China. Otherwise, check out these important facts you probably never knew about gree.com

珠海格力电器股份有限公司是一家集研发、生产、销售、服务于一体的国际化家电企业，拥有格力、TOSOT、晶弘三大品牌，主营家用空调、中央空调、空气能热水器、手机、生活电器、冰箱等产品。

Visit gree.com

Key Findings

We analyzed Gree.com page load time and found that the first response time was 935 ms and then it took 10 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

gree.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.731

6/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

gree.com

935 ms

jquery.min.js

449 ms

bootstrap.css

869 ms

gree.init.css

653 ms

gree.layout.css

699 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 82% of them (72 requests) were addressed to the original Gree.com, 8% (7 requests) were made to Img.t.sinajs.cn and 2% (2 requests) were made to Widget.weibo.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Gree.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 325.7 kB (7%)

Content Size

4.6 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gree.com main page is 4.6 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 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 51.7 kB

  • Original 59.0 kB
  • After minification 34.9 kB
  • After compression 7.3 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 24.1 kB, which is 41% 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 51.7 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 201.5 kB

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

JavaScript Optimization

-24%

Potential reduce by 40.0 kB

  • Original 163.3 kB
  • After minification 163.3 kB
  • After compression 123.4 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 40.0 kB or 24% of the original size.

CSS Optimization

-47%

Potential reduce by 32.4 kB

  • Original 68.9 kB
  • After minification 68.9 kB
  • After compression 36.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. Gree.com needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (24%)

Requests Now

86

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gree.com

gree.com

935 ms

jquery.min.js

jquery.min.js

449 ms

bootstrap.css

bootstrap.css

869 ms

gree.init.css

gree.init.css

653 ms

gree.layout.css

gree.layout.css

699 ms

bootstrap.min.js

bootstrap.min.js

659 ms

gree.init.js

gree.init.js

1104 ms

gree.common.js

gree.common.js

696 ms

gree.layout.js

gree.layout.js

879 ms

gree.index.js

gree.index.js

879 ms

index.php

index.php

891 ms

logo.png

logo.png

225 ms

collapse-def.png

collapse-def.png

220 ms

310x310.jpg

310x310.jpg

660 ms

icon_Air-Conditioner-02@2x.png

icon_Air-Conditioner-02@2x.png

221 ms

icon_Home-central-air-conditioning-02@2x.png

icon_Home-central-air-conditioning-02@2x.png

219 ms

icon_home-devices-02@2x.png

icon_home-devices-02@2x.png

217 ms

icon_refrigerator-02@2x.png

icon_refrigerator-02@2x.png

434 ms

icon_washing-machine-02@2x.png

icon_washing-machine-02@2x.png

437 ms

icon_Water-heater-02@2x.png

icon_Water-heater-02@2x.png

439 ms

icon_Smart-product-02@2x.png

icon_Smart-product-02@2x.png

441 ms

icon_Zero-carbon-02@2x.png

icon_Zero-carbon-02@2x.png

447 ms

a-2.png

a-2.png

1080 ms

icon_Water-purifier-02@2x.png

icon_Water-purifier-02@2x.png

652 ms

icon_Industrial%20products-02@2x.png

icon_Industrial%20products-02@2x.png

658 ms

znly.png

znly.png

661 ms

jump-def.png

jump-def.png

669 ms

search-def.png

search-def.png

869 ms

jumpBuy.jpg

jumpBuy.jpg

877 ms

jumpShop.jpg

jumpShop.jpg

879 ms

video-imgView.png

video-imgView.png

882 ms

000.png

000.png

892 ms

unsound.png

unsound.png

1086 ms

yessound.png

yessound.png

1096 ms

%E9%A6%96%E9%A1%B5banner-%E7%AC%AC%E4%BA%8C%E4%BB%A3%E6%A0%BC%E5%8A%9B%E5%86%B7%E9%85%B7%E5%A4%96%E6%9C%BA%E4%B8%BB%E7%94%BB%E9%9D%A2%201920x940.jpg

%E9%A6%96%E9%A1%B5banner-%E7%AC%AC%E4%BA%8C%E4%BB%A3%E6%A0%BC%E5%8A%9B%E5%86%B7%E9%85%B7%E5%A4%96%E6%9C%BA%E4%B8%BB%E7%94%BB%E9%9D%A2%201920x940.jpg

1757 ms

%E5%A5%BD%E7%94%B5%E5%99%A8%E6%A0%BC%E5%8A%9B%E9%80%A0%E4%B8%BBkv.jpg

%E5%A5%BD%E7%94%B5%E5%99%A8%E6%A0%BC%E5%8A%9B%E9%80%A0%E4%B8%BBkv.jpg

3736 ms

516%E5%86%B0%E7%AE%B1banner-1920%C3%97940.jpg

516%E5%86%B0%E7%AE%B1banner-1920%C3%97940.jpg

5955 ms

%E7%8C%8E%E6%89%8B%E5%87%80%E5%8C%96%E5%99%A8banner-1920%C3%97940(1).jpg

%E7%8C%8E%E6%89%8B%E5%87%80%E5%8C%96%E5%99%A8banner-1920%C3%97940(1).jpg

2592 ms

icon_New%20product-02@2x.png

icon_New%20product-02@2x.png

1303 ms

%E6%A0%BC%E5%8A%9B%E2%80%A2%E8%87%B3%E5%B0%8A-%E5%AE%98%E7%BD%91%E5%B9%BF%E5%91%8A%E4%BD%8D%E5%9B%BE%E7%89%87%20342x695PX.jpg

%E6%A0%BC%E5%8A%9B%E2%80%A2%E8%87%B3%E5%B0%8A-%E5%AE%98%E7%BD%91%E5%B9%BF%E5%91%8A%E4%BD%8D%E5%9B%BE%E7%89%87%20342x695PX.jpg

1753 ms

%E7%94%B5%E9%A3%8E%E6%89%87.jpg

%E7%94%B5%E9%A3%8E%E6%89%87.jpg

1737 ms

%E5%B0%8F%E7%8C%8E%E6%89%8B.jpg

%E5%B0%8F%E7%8C%8E%E6%89%8B.jpg

2171 ms

03.jpg

03.jpg

1976 ms

022.jpg

022.jpg

2197 ms

icon_View@2x.png

icon_View@2x.png

2196 ms

1.jpeg

1.jpeg

2394 ms

hm.js

hm.js

936 ms

mall.png

mall.png

2334 ms

address.png

address.png

2204 ms

logo_kinghome-02.png

logo_kinghome-02.png

2397 ms

logo_TOSOT-02.png

logo_TOSOT-02.png

2419 ms

logo_Intelligent%20equipment-02.png

logo_Intelligent%20equipment-02.png

2419 ms

logo_Iamda-02.png

logo_Iamda-02.png

2588 ms

logo_KB-02.png

logo_KB-02.png

2398 ms

logo_RCGO-02.png

logo_RCGO-02.png

2422 ms

logo_wuhu-02.png

logo_wuhu-02.png

2420 ms

logo_electrician-02.png

logo_electrician-02.png

2588 ms

logo_JD-02.png

logo_JD-02.png

2604 ms

logo_Mold-02.png

logo_Mold-02.png

2426 ms

logo_LY.png

logo_LY.png

2422 ms

logo_gltxny.png

logo_gltxny.png

2588 ms

logo_gljd.png

logo_gljd.png

2607 ms

ls.png

ls.png

2628 ms

wechat.png

wechat.png

2430 ms

gyzpgfwx.jpg

gyzpgfwx.jpg

2805 ms

baidu.png

baidu.png

2609 ms

glgfwxfwh.jpg

glgfwxfwh.jpg

2634 ms

index.php

index.php

964 ms

glgfdyh.jpg

glgfdyh.jpg

2634 ms

hm.gif

hm.gif

305 ms

glsc.jpg

glsc.jpg

2628 ms

glznjj.jpg

glznjj.jpg

2658 ms

jhbxewm.jpg

jhbxewm.jpg

2652 ms

%E6%A0%BC%E5%8A%9B%E5%86%B7%E9%93%BE%E6%9C%8D%E5%8A%A1%E5%8F%B7.jpg

%E6%A0%BC%E5%8A%9B%E5%86%B7%E9%93%BE%E6%9C%8D%E5%8A%A1%E5%8F%B7.jpg

2595 ms

weibo.png

weibo.png

2187 ms

beian.png

beian.png

2204 ms

weiboShow.css

weiboShow.css

1235 ms

skin_default.css

skin_default.css

1725 ms

gaea_1_20.js

gaea_1_20.js

907 ms

show.js

show.js

947 ms

suda.js

suda.js

979 ms

6d314616ly8hdnkcqzjtnj20k00k0mxi.jpg

6d314616ly8hdnkcqzjtnj20k00k0mxi.jpg

868 ms

icon_user.png

icon_user.png

284 ms

btns_bg.png

btns_bg.png

1079 ms

icon_follow.png

icon_follow.png

299 ms

bg_trans.png

bg_trans.png

3453 ms

icon_tips.png

icon_tips.png

290 ms

tmp.gif

tmp.gif

1131 ms

Accessibility Review

gree.com accessibility score

78

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

gree.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gree.com SEO score

71

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gree.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Gree.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

gree.com

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