51.9 sec in total
8 sec
43.7 sec
182 ms
Welcome to longtantea.com homepage info - get ready to check Longtantea best content right away, or after learning these important things about longtantea.com
龙潭茶叶,龙潭茶叶有限公司
Visit longtantea.comWe analyzed Longtantea.com page load time and found that the first response time was 8 sec and then it took 43.9 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 were 25 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
longtantea.com performance score
7976 ms
2762 ms
5277 ms
1148 ms
6899 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 86% of them (32 requests) were addressed to the original Longtantea.com, 11% (4 requests) were made to Hm.baidu.com and 3% (1 request) were made to Eiv.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Longtantea.com.
Page size can be reduced by 356.8 kB (76%)
467.3 kB
110.5 kB
In fact, the total size of Longtantea.com main page is 467.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 305.3 kB which makes up the majority of the site volume.
Potential reduce by 12.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. This page needs HTML code to be minified as it can gain 1.8 kB, which is 11% 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 12.1 kB or 75% of the original size.
Potential reduce by 241.2 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. Obviously, Longtantea needs image optimization as it can save up to 241.2 kB or 79% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 86.7 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 86.7 kB or 69% of the original size.
Potential reduce by 16.8 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. Longtantea.com needs all CSS files to be minified and compressed as it can save up to 16.8 kB or 83% of the original size.
Number of requests can be reduced by 5 (45%)
11
6
The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Longtantea. 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.
longtantea.com
7976 ms
news.js
2762 ms
uaredirect.js
5277 ms
base.css
1148 ms
style.css
6899 ms
jquery.js
20151 ms
jquery.smallslider.js
20152 ms
common.js
6395 ms
g000.jpg
20151 ms
g001.jpg
20152 ms
g002.jpg
20151 ms
swfobject.js
13995 ms
sh1.png
19712 ms
sh3.png
19712 ms
lth.jpg
19712 ms
h2.png
19712 ms
sxy.png
19713 ms
h1.png
19712 ms
zs.png
19713 ms
sh2.png
19713 ms
network%20.png
19713 ms
fw.png
19712 ms
store.png
19713 ms
qr.png
19713 ms
qr.jpg
20268 ms
weibo.png
20269 ms
weibomax.png
20269 ms
flogo2.png
20269 ms
flogo1.png
20269 ms
sh4.png
20269 ms
gswj_icon2.jpg
20268 ms
logo.jpg
19962 ms
h.js
556 ms
hm.gif
267 ms
h.js
1142 ms
21.gif
789 ms
hm.gif
309 ms
longtantea.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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
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
longtantea.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
longtantea.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
![]()
N/A
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Longtantea.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Longtantea.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.
longtantea.com
Open Graph description is not detected on the main page of Longtantea. 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: