37.1 sec in total
1.9 sec
34 sec
1.2 sec
Welcome to 365srzt.cn homepage info - get ready to check 365 Srzt best content right away, or after learning these important things about 365srzt.cn
365srzt.cn
Visit 365srzt.cnWe analyzed 365srzt.cn page load time and found that the first response time was 1.9 sec and then it took 35.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.
365srzt.cn performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value3.1 s
75/100
25%
Value5.1 s
62/100
10%
Value20 ms
100/100
30%
Value0.441
21/100
15%
Value2.9 s
96/100
10%
1853 ms
110 ms
213 ms
217 ms
117 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 49% of them (50 requests) were addressed to the original 365srzt.cn, 8% (8 requests) were made to Img01.taobaocdn.com and 6% (6 requests) were made to Img05.taobaocdn.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Web.51.la.
Page size can be reduced by 146.3 kB (12%)
1.3 MB
1.1 MB
In fact, the total size of 365srzt.cn main page is 1.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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 42.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 42.4 kB or 82% of the original size.
Potential reduce by 28.6 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. 365 Srzt images are well optimized though.
Potential reduce by 31.3 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 31.3 kB or 51% of the original size.
Potential reduce by 44.0 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. 365srzt.cn needs all CSS files to be minified and compressed as it can save up to 44.0 kB or 87% of the original size.
Number of requests can be reduced by 11 (18%)
61
50
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 365 Srzt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.365srzt.cn
1853 ms
t2_li.js
110 ms
style.css
213 ms
shop.css
217 ms
T1peB2Fv4aXXXXXXXX_!!0-item_pic.jpg
117 ms
TB1MF4aHVXXXXacXXXXXXXXXXXX_!!0-item_pic.jpg
543 ms
TB1v6cyGVXXXXcIXVXXXXXXXXXX_!!0-item_pic.jpg
466 ms
T17MKOXrpeXXXXXXXX_!!0-item_pic.jpg
308 ms
T14lAOFkdhXXXXXXXX_!!1-item_pic.gif
308 ms
T1H2F7FqFiXXXXXXXX_!!0-item_pic.jpg
307 ms
T18QevFd4dXXXXXXXX_!!0-item_pic.jpg
308 ms
TB18GXfHFXXXXbUXFXXXXXXXXXX_!!0-item_pic.jpg
322 ms
TB1SQy9HFXXXXaxXpXXXXXXXXXX_!!0-item_pic.jpg
320 ms
T2GjZCXjVXXXXXXXXX_!!279490231.jpg
339 ms
TB2CeOnXVXXXXX6XXXXXXXXXXXX_!!1976447417.jpg
341 ms
TB1V2UHGVXXXXauXpXXXXXXXXXX_!!0-item_pic.jpg
379 ms
TB1_TAtHpXXXXc6XXXXXXXXXXXX_!!0-item_pic.jpg
379 ms
TB1rme5FVXXXXaaXFXXXXXXXXXX_!!0-item_pic.jpg
390 ms
TB1u8zvFVXXXXcXXpXXXXXXXXXX_!!2-item_pic.png
397 ms
T1XJmGXyBbXXXXXXXX_!!0-item_pic.jpg
425 ms
TB1MGZ2HpXXXXaFXXXXXXXXXXXX_!!0-item_pic.jpg
429 ms
TB1dq7ZHpXXXXbxXXXXXXXXXXXX_!!0-item_pic.jpg
444 ms
TB1hpFNFVXXXXapaXXXXXXXXXXX_!!0-item_pic.jpg
450 ms
TB12VtiHVXXXXbeXVXXXXXXXXXX_!!0-item_pic.jpg
501 ms
T1Wx8dXk3GxdKWt5AT_011951.jpg
502 ms
T17UukXmhjXXXBJN3Z_032559.jpg
528 ms
TB1.vwLGXXXXXcOXXXXXXXXXXXX_!!1-item_pic.gif
534 ms
T12ctKXsxfXXXXXXXX_!!0-item_pic.jpg
546 ms
TB1nDWxGXXXXXbgXpXXXXXXXXXX_!!0-item_pic.jpg
572 ms
T1DzCRFbleXXXXXXXX_!!0-item_pic.jpg
571 ms
TB1DNl2GXXXXXXUXpXXXXXXXXXX_!!0-item_pic.jpg
577 ms
T1w45HFktaXXXXXXXX_!!0-item_pic.jpg
580 ms
T14ITDXitXXXXf.zLa_121624.jpg
592 ms
TB1ER7QHpXXXXXMXFXXXXXXXXXX_!!0-item_pic.jpg
598 ms
T1kWlHFs0CXXXXXXXX_!!0-item_pic.jpg
638 ms
TB12BlSGpXXXXcBXpXXXXXXXXXX_!!1-item_pic.gif
639 ms
TB1vqiKGXXXXXX9XpXXXXXXXXXX_!!0-item_pic.jpg
679 ms
TB12YS_FVXXXXc8XXXXXXXXXXXX_!!0-item_pic.jpg
686 ms
group.png
247 ms
wz_tooltip-min.js
609 ms
jia.js
823 ms
17072459.js
983 ms
stat.php
3441 ms
TB14PLmHpXXXXacXXXXXXXXXXXX_!!0-item_pic.jpg
621 ms
T1peB2Fv4aXXXXXXXX_!!0-item_pic.jpg_310x310.jpg
1139 ms
T14lAOFkdhXXXXXXXX_!!1-item_pic.gif_160x160.jpg
121 ms
T17MKOXrpeXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
350 ms
T1H2F7FqFiXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
991 ms
T18QevFd4dXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
322 ms
TB1SQy9HFXXXXaxXpXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
311 ms
TB18GXfHFXXXXbUXFXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
380 ms
T2GjZCXjVXXXXXXXXX_!!279490231.jpg_160x160.jpg
881 ms
TB2CeOnXVXXXXX6XXXXXXXXXXXX_!!1976447417.jpg_160x160.jpg
41 ms
TB1DBQUHpXXXXXgXFXXXXXXXXXX_!!0-item_pic.jpg
463 ms
T10SiFXu8eXXXXXXXX_!!0-item_pic.jpg
464 ms
TB1a1bPHpXXXXahaXXXXXXXXXXX_!!0-item_pic.jpg
510 ms
001.jpg
1133 ms
light.png
2086 ms
boxed-container-shadow.png
946 ms
002.jpg
766 ms
shadow-product.png
564 ms
TB1V2UHGVXXXXauXpXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
349 ms
TB1_TAtHpXXXXc6XXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
19 ms
TB1rme5FVXXXXaaXFXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
1126 ms
TB1u8zvFVXXXXcXXpXXXXXXXXXX_!!2-item_pic.png_160x160.jpg
744 ms
T1XJmGXyBbXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
798 ms
TB1MGZ2HpXXXXaFXXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
981 ms
TB1dq7ZHpXXXXbxXXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
629 ms
TB1hpFNFVXXXXapaXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
1107 ms
TB1v6cyGVXXXXcIXVXXXXXXXXXX_!!0-item_pic.jpg_310x310.jpg
678 ms
TB12VtiHVXXXXbeXVXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
2420 ms
T1Wx8dXk3GxdKWt5AT_011951.jpg_160x160.jpg
485 ms
T17UukXmhjXXXBJN3Z_032559.jpg_160x160.jpg
40 ms
TB1MF4aHVXXXXacXXXXXXXXXXXX_!!0-item_pic.jpg_310x310.jpg
800 ms
TB1.vwLGXXXXXcOXXXXXXXXXXXX_!!1-item_pic.gif_160x160.jpg
641 ms
T12ctKXsxfXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
86 ms
TB1nDWxGXXXXXbgXpXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
458 ms
T1DzCRFbleXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
601 ms
TB1DNl2GXXXXXXUXpXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
13 ms
T1w45HFktaXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
364 ms
T14ITDXitXXXXf.zLa_121624.jpg_160x160.jpg
451 ms
TB1ER7QHpXXXXXMXFXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
513 ms
T1kWlHFs0CXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
455 ms
TB12BlSGpXXXXcBXpXXXXXXXXXX_!!1-item_pic.gif_160x160.jpg
204 ms
TB1vqiKGXXXXXX9XpXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
210 ms
TB12YS_FVXXXXc8XXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
483 ms
function.js
8970 ms
TB14PLmHpXXXXacXXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
3803 ms
TB1DBQUHpXXXXXgXFXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
329 ms
T10SiFXu8eXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
61 ms
TB1a1bPHpXXXXahaXXXXXXXXXXX_!!0-item_pic.jpg_160x160.jpg
118 ms
lessthen980.css
151 ms
lessthen600.css
118 ms
jiathis_utility.html
54 ms
jiathis_share.css
102 ms
plugin.client.js
97 ms
jiathis_ico.png
564 ms
stat.htm
349 ms
core.php
1097 ms
go.asp
20280 ms
9.gif
1039 ms
app.gif
1174 ms
365srzt.cn 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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.
365srzt.cn 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
365srzt.cn 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
![]()
EN
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 365srzt.cn can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that 365srzt.cn 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.
365srzt.cn
Open Graph description is not detected on the main page of 365 Srzt. 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: