Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 54

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

glaer.com

Glaer光蓝官网 - 中国领先的电子商务解决方案提供商 - 北京光蓝网络科技有限公司

Page Load Speed

33.8 sec in total

First Response

1.5 sec

Resources Loaded

32 sec

Page Rendered

306 ms

glaer.com screenshot

About Website

Visit glaer.com now to see the best up-to-date Glaer content for China and also check out these interesting facts you probably never knew about glaer.com

Glaer光蓝网络是中国领先的电子商务解决方案提供商,专注于为央企、上市公司、500强及各行业领头企业提供特色定制的大中型电子商务平台解决方案。是电商网站建设、电商网站开发、电商平台建设、电商系统开发的专业机构。我们围绕B2B系统进行开发运营服务,主要范围是B2B网站建设、B2B系统建设、B2B系统开发、电子商务系统开发、电子商务网站开发等。选择电商网站建设开发,就在光蓝网络。

Visit glaer.com

Key Findings

We analyzed Glaer.com page load time and found that the first response time was 1.5 sec and then it took 32.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

glaer.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

4/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value1,850 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value15.0 s

8/100

10%

Network Requests Diagram

glaer.com

1528 ms

www.glaer.com

5964 ms

jquery.min.js

6923 ms

main.css

2830 ms

common.js

966 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 77% of them (44 requests) were addressed to the original Glaer.com, 5% (3 requests) were made to Hm.baidu.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (19.6 sec) belongs to the original domain Glaer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.8 kB (36%)

Content Size

540.4 kB

After Optimization

346.6 kB

In fact, the total size of Glaer.com main page is 540.4 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. 25% of websites need less resources to load. Images take 284.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 26.6 kB

  • Original 33.6 kB
  • After minification 31.4 kB
  • After compression 7.0 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 26.6 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 20.7 kB

  • Original 284.5 kB
  • After minification 263.8 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. Glaer images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 126.8 kB

  • Original 198.1 kB
  • After minification 196.7 kB
  • After compression 71.2 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 126.8 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 19.6 kB

  • Original 24.3 kB
  • After minification 20.6 kB
  • After compression 4.6 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. Glaer.com needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (27%)

Requests Now

52

After Optimization

38

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glaer. 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 as a result speed up the page load time.

Accessibility Review

glaer.com accessibility score

48

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

glaer.com best practices score

54

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

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Uses deprecated APIs

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

glaer.com SEO score

77

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

High

robots.txt is not valid

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 uses legible font sizes

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 Glaer.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 Glaer.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

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