15 sec in total
819 ms
13.6 sec
623 ms
Welcome to qdtianzhu.com homepage info - get ready to check Qdtianzhu best content right away, or after learning these important things about qdtianzhu.com
青岛天铸环保设备有限公司产品门类已拓展至:浇注设备、环保除尘设备、熔化工部成套设备、砂处理设备、清理混砂设备及电动平车等六大类130多种产品,主要产品电炉加料车、烤包器、喂丝球化包、电动铁水包、底漏钢水包、浇铸线除尘、电炉龙卷风吸尘罩、电炉除尘器、打磨除尘器、轨道电动平车。
Visit qdtianzhu.comWe analyzed Qdtianzhu.com page load time and found that the first response time was 819 ms and then it took 14.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
qdtianzhu.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value6.8 s
7/100
25%
Value6.5 s
39/100
10%
Value200 ms
89/100
30%
Value0
100/100
15%
Value4.9 s
78/100
10%
819 ms
571 ms
961 ms
576 ms
385 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 97% of them (90 requests) were addressed to the original Qdtianzhu.com, 2% (2 requests) were made to Cdn.webfont.youziku.com and 1% (1 request) were made to Che0.com. The less responsive or slowest element that took the longest time to load (8.4 sec) belongs to the original domain Qdtianzhu.com.
Page size can be reduced by 1.9 MB (57%)
3.3 MB
1.4 MB
In fact, the total size of Qdtianzhu.com main page is 3.3 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. 55% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 18.1 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 18.1 kB or 77% of the original size.
Potential reduce by 1.8 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. Obviously, Qdtianzhu needs image optimization as it can save up to 1.8 MB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 75.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 75.4 kB or 43% of the original size.
Potential reduce by 7.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. Qdtianzhu.com needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 40% of the original size.
Number of requests can be reduced by 9 (15%)
61
52
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qdtianzhu. 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 as a result speed up the page load time.
qdtianzhu.com
819 ms
style.css
571 ms
jquery-1.9.1.min.js
961 ms
parallax.js
576 ms
shijian.js
385 ms
youziku.api.min.js
397 ms
jquery.rotate.min.js
561 ms
282.css
775 ms
3004.js
1210 ms
7823.js
751 ms
a.js
575 ms
colorbox.css
582 ms
jquery.colorbox.js
944 ms
css.js
440 ms
youziku.lib.min.js
842 ms
kf.png
189 ms
kf1.png
194 ms
open_btn1.png
193 ms
nav_bg.png
190 ms
close_btn.png
191 ms
nav1.png
190 ms
logo_m.png
373 ms
loading.gif
377 ms
b1_01.png
564 ms
b1_02.png
382 ms
b1_03.png
384 ms
yd.png
391 ms
vdimgck.php
582 ms
sprite.png
540 ms
b1_bg.jpg
1030 ms
qdtianzhu.com
608 ms
n_h1.png
594 ms
tm.png
726 ms
con_bg.png
726 ms
b1_01.png
770 ms
b1_02.png
891 ms
b1_03.png
892 ms
b1_03_btn.png
923 ms
b1_04.png
961 ms
b1_bg.jpg
957 ms
b2_01.png
1079 ms
b2_03.png
1078 ms
b2_04.png
1117 ms
b2_05.png
1146 ms
b2_06.png
1157 ms
b2_bg.jpg
1684 ms
sprite.png
1266 ms
youziku.lib.min.js
958 ms
b2_bg.jpg
2939 ms
b2_02.png
193 ms
b2_03.png
4498 ms
b2_05.png
189 ms
b2_07.png
192 ms
b2_09.png
376 ms
b3_01.png
375 ms
b3_bg.jpg
379 ms
b3_bg.jpg
204 ms
b3_j_2.jpg
190 ms
b3_j_3.jpg
192 ms
b3_j_4.jpg
189 ms
b3_j_5.jpg
377 ms
b3_05.png
378 ms
b3_j_6.jpg
382 ms
b3_j_1.jpg
395 ms
b4_01.png
566 ms
b4_02.png
567 ms
b4_bg.jpg
570 ms
b4_bg.jpg
2491 ms
b4_01.png
8387 ms
b4_03.png
191 ms
b4_05.png
189 ms
b4_05_1.png
378 ms
b4_05_2.png
381 ms
b4_05_3.png
566 ms
b5_01.png
572 ms
b5_bg.jpg
754 ms
b5_ico.png
760 ms
b5_bg.jpg
1819 ms
b5_01.png
4740 ms
b3_02.png
1608 ms
b5_03.png
2007 ms
b5_05.png
1932 ms
b5_07.png
2010 ms
b6_01.png
2123 ms
b6_arrow.png
2199 ms
b6_bg.jpg
2200 ms
b6_ico.png
2315 ms
b6_img.png
2388 ms
b6_03.png
407 ms
b6_04.png
205 ms
b7_bg.jpg
192 ms
b7_sprite.png
379 ms
map.jpg
407 ms
qdtianzhu.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
qdtianzhu.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
qdtianzhu.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qdtianzhu.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 Qdtianzhu.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.
qdtianzhu.com
Open Graph description is not detected on the main page of Qdtianzhu. 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: