Tools & Wizards About Us
qdtg.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

qdtg.com

天宫课堂

Page Load Speed

13.3 sec in total

First Response

685 ms

Resources Loaded

12.4 sec

Page Rendered

229 ms

qdtg.com screenshot

About Website

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

天宫课堂为建筑行业在职人士提供天宫DFC_BIM软件培训，内容含土建BIM、机电BIM、装饰BIM课程。BIM课程具有实操性、落地性，BIM课程免费听，网上报名学习。

Visit qdtg.com

Key Findings

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

qdtg.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.458

0/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

qdtg.com

685 ms

www.tgkw.com

3900 ms

all.css

262 ms

bootstrap.min.css

1400 ms

common.css

744 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Qdtg.com, 97% (30 requests) were made to Tgkw.com. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Tgkw.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (24%)

Content Size

6.2 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qdtg.com main page is 6.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. 30% of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 8.1 kB

  • Original 10.1 kB
  • After minification 5.1 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 5.0 kB, which is 50% 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 8.1 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 481.9 kB

  • Original 4.9 MB
  • After minification 4.4 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. Qdtg images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 309.6 kB

  • Original 456.5 kB
  • After minification 455.7 kB
  • After compression 146.9 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 309.6 kB or 68% of the original size.

CSS Optimization

-75%

Potential reduce by 663.1 kB

  • Original 879.5 kB
  • After minification 796.9 kB
  • After compression 216.4 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. Qdtg.com needs all CSS files to be minified and compressed as it can save up to 663.1 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (59%)

Requests Now

29

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qdtg.com

qdtg.com

685 ms

www.tgkw.com

www.tgkw.com

3900 ms

all.css

all.css

262 ms

bootstrap.min.css

bootstrap.min.css

1400 ms

common.css

common.css

744 ms

index.css

index.css

785 ms

jquery.min.js

jquery.min.js

1571 ms

popper.min.js

popper.min.js

1103 ms

bootstrap.min.js

bootstrap.min.js

1409 ms

layui.all.js

layui.all.js

3156 ms

common.js

common.js

1493 ms

index.js

index.js

1659 ms

banner_001.png

banner_001.png

4897 ms

banner5.0_web1.png

banner5.0_web1.png

6322 ms

banner5.0_web33.jpg

banner5.0_web33.jpg

4910 ms

banner5.0_web4.jpg

banner5.0_web4.jpg

4904 ms

banner_005.png

banner_005.png

7194 ms

banner_006.png

banner_006.png

6213 ms

study.png

study.png

5157 ms

index_item1_phone.png

index_item1_phone.png

5381 ms

index_item_web.png

index_item_web.png

5986 ms

index_item_2_3.png

index_item_2_3.png

6665 ms

css.css

css.css

5934 ms

css.css

css.css

7088 ms

css.css

css.css

6759 ms

css.css

css.css

6729 ms

css.css

css.css

6881 ms

css.css

css.css

7143 ms

laydate.css

laydate.css

276 ms

layer.css

layer.css

319 ms

code.css

code.css

247 ms

Accessibility Review

qdtg.com accessibility score

49

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

qdtg.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

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

    ZH

  • Encoding

    UTF-8

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

qdtg.com

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