37.3 sec in total
1.7 sec
31.1 sec
4.5 sec
Welcome to teaho.com homepage info - get ready to check Teaho best content right away, or after learning these important things about teaho.com
We are professional Shock absorber manufacturer and provide high quality of China Shock absorber. Save time and buy your Shock absorber thanks to our online form.
Visit teaho.comWe analyzed Teaho.com page load time and found that the first response time was 1.7 sec and then it took 35.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.
teaho.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value9.8 s
0/100
25%
Value6.4 s
40/100
10%
Value200 ms
90/100
30%
Value0
100/100
15%
Value6.3 s
60/100
10%
1680 ms
476 ms
180 ms
279 ms
566 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 76% of them (69 requests) were addressed to the original Teaho.com, 13% (12 requests) were made to Embed.tawk.to and 3% (3 requests) were made to Static.meiqia.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source V1.cnzz.com.
Page size can be reduced by 244.3 kB (35%)
702.7 kB
458.4 kB
In fact, the total size of Teaho.com main page is 702.7 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. 45% of websites need less resources to load. HTML takes 272.0 kB which makes up the majority of the site volume.
Potential reduce by 215.4 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 215.4 kB or 79% of the original size.
Potential reduce by 8.5 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. Teaho images are well optimized though.
Potential reduce by 18.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Teaho.com needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 16% of the original size.
Number of requests can be reduced by 31 (36%)
86
55
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teaho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
teaho.com
1680 ms
app.css
476 ms
global.css
180 ms
templet.css
279 ms
style.css
566 ms
app.6329a67e41b0d69a96b52fd0645feb5e.css
1332 ms
kefu.js
520 ms
js
90 ms
style.css
447 ms
animate.min.css
729 ms
widget.js
854 ms
meiqia.js
1795 ms
jquery.min.js
1469 ms
wow.min.js
906 ms
headroom.min.js
1363 ms
jquery.headroom.js
1317 ms
jiaodiantu.js
999 ms
jquery-2.1.4.min.js
1468 ms
website.js
1216 ms
area.js
1397 ms
style.js
1809 ms
bb.js
848 ms
cn.gif
318 ms
es.gif
381 ms
1-20052514335K33.png
2967 ms
header_ph_01.png
512 ms
1-220314141311V1.jpg
1213 ms
1-22031414121I35.jpg
1616 ms
1-20052509113b92.png
2030 ms
1-2105191F3443J.JPG
4078 ms
1-2105211I601H9.JPG
3143 ms
1-2105211J032N3.JPG
2687 ms
1-2005231K159218.jpg
861 ms
1-2005231K204162.jpg
1088 ms
1-2005231K20UO.jpg
1139 ms
1-2005231K213362.jpg
1435 ms
1-20052011402J62.jpg
2204 ms
1-2005231P03NG.png
1525 ms
1-200523161522Z1.png
1977 ms
1-200523161530913.png
1624 ms
1-2102201K102460.jpg
7057 ms
1-210Q11T132L3.jpg
14080 ms
1-21061GS115217.jpg
10111 ms
1-200525093PX38.png
10169 ms
1-200525093H5452.png
4835 ms
1-210H2153623207.jpg
4961 ms
1-210H21531431b.jpg
9061 ms
1-210H31H414462.jpg
14774 ms
1-2104301GJ41O.jpg
17364 ms
1-210H31326353T.jpg
11458 ms
1-210224094125107.jpg
15958 ms
1-210H2153PL04.jpg
15791 ms
1-210H2153SH54.jpg
13483 ms
join_icon_01.png
13564 ms
join_icon_02.png
13604 ms
z_stat.php
19730 ms
join_icon_03.png
13864 ms
join_icon_04.png
13931 ms
1-200619105612E7.jpg
16109 ms
1-1912301G1154Z.jpg
15916 ms
1-2005231Q52J06.jpg
14808 ms
1-2005231Q536100.jpg
15556 ms
footer_ph_01.png
15602 ms
analytics.js
143 ms
1f8phgdmd
206 ms
1-210223092KY48.jpg
6352 ms
1-2102241KG0591.jpg
7472 ms
1-200310155643249.jpg
4354 ms
icon_01.png
164 ms
hm.js
1785 ms
stripe.png
2635 ms
sync-cookie.html
267 ms
icon_05.png
502 ms
icon_11.png
194 ms
collect
24 ms
index.php
1941 ms
sprite.png
775 ms
hm.gif
339 ms
vendor-v2019.12.13.2.js
285 ms
app-v2019.12.13.2.js
70 ms
twk-arr-find-polyfill.js
188 ms
twk-object-values-polyfill.js
63 ms
twk-event-polyfill.js
73 ms
twk-entries-polyfill.js
188 ms
twk-iterator-polyfill.js
199 ms
twk-main.js
75 ms
twk-vendor.js
166 ms
twk-chunk-vendors.js
280 ms
twk-chunk-common.js
229 ms
twk-runtime.js
224 ms
twk-app.js
277 ms
teaho.com accessibility score
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
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.
teaho.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
teaho.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teaho.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Teaho.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.
teaho.com
Open Graph description is not detected on the main page of Teaho. 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: