27.6 sec in total
1.4 sec
25.8 sec
405 ms
Welcome to jieyan990.com homepage info - get ready to check Jieyan 990 best content right away, or after learning these important things about jieyan990.com
Visit jieyan990.comWe analyzed Jieyan990.com page load time and found that the first response time was 1.4 sec and then it took 26.2 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.
jieyan990.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.616
10/100
15%
Value0
0/100
10%
1376 ms
502 ms
577 ms
289 ms
4002 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 17% of them (21 requests) were addressed to the original Jieyan990.com, 29% (36 requests) were made to G.alicdn.com and 27% (34 requests) were made to Img.alicdn.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Gskip.taobao.com.
Page size can be reduced by 202.1 kB (18%)
1.1 MB
891.9 kB
In fact, the total size of Jieyan990.com main page is 1.1 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. 50% of websites need less resources to load. Images take 809.7 kB which makes up the majority of the site volume.
Potential reduce by 21.5 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 21.5 kB or 78% of the original size.
Potential reduce by 5.4 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. Jieyan 990 images are well optimized though.
Potential reduce by 163.8 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 163.8 kB or 68% of the original size.
Potential reduce by 11.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. Jieyan990.com needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 78% of the original size.
Number of requests can be reduced by 51 (44%)
115
64
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jieyan 990. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
jieyan990.com
1376 ms
style.css
502 ms
style.css
577 ms
tb_search.php
289 ms
a002.jpg
4002 ms
8e16ddd1aee4484b6dc0e348486da974
1068 ms
2014.png
1432 ms
ad-2.jpg
2174 ms
ad-1.jpg
968 ms
ad-4.jpg
1624 ms
ad-3.jpg
1980 ms
ad-5.jpg
1601 ms
ad-6.jpg
2397 ms
ad-7.jpg
2172 ms
ad-8.jpg
3274 ms
ad-9.jpg
3274 ms
ad-10.jpg
3203 ms
group.png
480 ms
stat.php
2562 ms
ad-11.jpg
2816 ms
ad-12.jpg
4438 ms
ad-13.jpg
4492 ms
ad-14.jpg
4717 ms
ad-15.jpg
4597 ms
ad-16.jpg
4607 ms
www.taobao.com
35 ms
www.taobao.com
489 ms
T222JaXhxMXXXXXXXX-676897564.gif
763 ms
zhanzhang.png
3025 ms
world.taobao.com
840 ms
world.taobao.com
1548 ms
analytics.js
30 ms
gtm.js
134 ms
collect
84 ms
collect
139 ms
g.alicdn.com
561 ms
519 ms
layout-pc.css
549 ms
g.alicdn.com
656 ms
571 ms
572 ms
index.css
571 ms
493 ms
506 ms
642 ms
TB1fevlKXXXXXaaXVXXXXXXXXXX-34-34.gif
617 ms
TB1_CjqIpXXXXbOXFXXuAZJYXXX-180-180.png
615 ms
TB156oWHpXXXXXIapXX_cBKGXXX-32-48.png
613 ms
TB14PwNIVXXXXbTXpXXqhF6.FXX-901-45.png
702 ms
123 ms
49 ms
62 ms
57 ms
aplus_v2.js
77 ms
TB1Ak8ZIVXXXXX0XXXXQxPyJVXX-95-40.png
526 ms
TB1qC0rIVXXXXbjaXXXH0F6FVXX-150-62.png
611 ms
getipinfo
842 ms
TB1ksX7HVXXXXcwXpXXzlnMKpXX-26-221.png
576 ms
50 ms
125 ms
font_1451273740_187741.woff
656 ms
agp_heat.min.js
77 ms
166 ms
font_1445342161_704327.woff
464 ms
146 ms
161 ms
314 ms
405 ms
index.js
150 ms
142 ms
214 ms
font_1433225452_0164654.woff
395 ms
146 ms
169 ms
67 ms
TB12CdUKpXXXXXraXXXXXXXXXXX-34-34.png
116 ms
33 ms
135 ms
32 ms
36 ms
s.gif
65 ms
TB1qLxzMpXXXXbiXVXXXXXXXXXX-770-360.jpg
706 ms
avatar-60.png
64 ms
TB11ZZfIVXXXXbMXFXXEDhGGXXX-32-32.png
375 ms
TB18yVTKpXXXXcIXpXXtSM2_pXX-108-82.png
64 ms
TB1c80TKpXXXXcCXpXXtSM2_pXX-108-82.png
392 ms
TB19TgIHpXXXXbRXVXX_AQW0XXX-529-200.png
288 ms
doQuery.jsonp
2313 ms
102 ms
TB1AAJ1KpXXXXbtXXXXtSM2_pXX-108-82.png
363 ms
TB1p5xbMpXXXXX9apXXXXXXXXXX-185-180.jpg
257 ms
TB13TLPMXXXXXaXXVXXXXXXXXXX-185-180.jpg
148 ms
TB1uvVsLXXXXXXcaXXXXXXXXXXX-108-82.png
68 ms
TB1X8FDKpXXXXckXpXXXXXXXXXX-210-42.png
72 ms
TB1vwlIKpXXXXXZXpXXXXXXXXXX-210-42.png
66 ms
TB1iiLsKXXXXXX5XFXXXXXXXXXX-1-1.png
99 ms
processUserCookie.htm
20004 ms
recommend
1936 ms
recommend
1986 ms
index.js
65 ms
index.js
60 ms
TB1HewyLFXXXXaYXFXXXXXXXXXX-58-52.png
81 ms
dyn_combo.do
4772 ms
TB1BKURLFXXXXXnXXXXXXXXXXXX-25-25.png
60 ms
TB1fq3oLFXXXXcpXVXXXXXXXXXX-111-111.png
66 ms
TB1nYDgLVXXXXXPXVXXXXXXXXXX-112-112.png
65 ms
TB1CK3nLFXXXXXWaXXXXXXXXXXX-143-51.png
61 ms
TB1MSsFLFXXXXbTXpXXXXXXXXXX-143-51.png
61 ms
TB1rRUULFXXXXcQXVXXXXXXXXXX-648-680.png_16x16.jpg
99 ms
TB2DgFFkXXXXXXRXpXXXXXXXXXX_!!693794325.jpg_160x160.jpg
48 ms
TB223fjmXXXXXbsXpXXXXXXXXXX_!!725738041.jpg_160x160.jpg
191 ms
TB1eIiHLVXXXXXWXVXXYXGcGpXX_M2.SS2_160x160.jpg
121 ms
TB2JMUDlFXXXXX8XpXXXXXXXXXX_!!54006497.jpg_160x160.jpg
35 ms
TB1NZahHXXXXXbgXXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
77 ms
TB1ex.5LVXXXXbSXXXXYXGcGpXX_M2.SS2_160x160.jpg
76 ms
35 ms
TB1elY3KpXXXXcZXVXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
39 ms
TB13UYrKpXXXXchXXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
61 ms
TB2OrV0mXXXXXb_XpXXXXXXXXXX_!!2307.jpg_160x160.jpg
72 ms
TB1n34THXXXXXbAXpXXyTkXLpXX-500-444.png
295 ms
TB1UW5eKpXXXXbSXpXXSutbFXXX.jpg_60x60.jpg
116 ms
minilogin.10.1
7019 ms
TB11ChDMpXXXXaQXpXXXXXXXXXX-770-360.jpg
197 ms
TB1pXLmMXXXXXXxXXXXXXXXXXXX-770-360.jpg
378 ms
jieyan990.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
<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
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.
jieyan990.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
jieyan990.com SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jieyan990.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 Jieyan990.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.
jieyan990.com
Open Graph description is not detected on the main page of Jieyan 990. 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: