85.4 sec in total
9.2 sec
75.8 sec
343 ms
Click here to check amazing 1626 content for China. Otherwise, check out these important facts you probably never knew about 1626.com
1626潮流精选
Visit 1626.comWe analyzed 1626.com page load time and found that the first response time was 9.2 sec and then it took 76.1 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.
1626.com performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value9.1 s
1/100
25%
Value12.8 s
2/100
10%
Value200 ms
89/100
30%
Value0.477
18/100
15%
Value20.3 s
2/100
10%
9241 ms
9410 ms
7563 ms
11016 ms
3923 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original 1626.com, 74% (74 requests) were made to Cdn1626.clouddn.com and 3% (3 requests) were made to Tjs.sjs.sinajs.cn. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Cdn1626.clouddn.com.
Page size can be reduced by 760.6 kB (31%)
2.4 MB
1.7 MB
In fact, the total size of 1626.com main page is 2.4 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. 45% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 72.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 72.5 kB or 81% of the original size.
Potential reduce by 366.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, 1626 needs image optimization as it can save up to 366.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 91.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 91.8 kB or 67% of the original size.
Potential reduce by 230.1 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. 1626.com needs all CSS files to be minified and compressed as it can save up to 230.1 kB or 85% of the original size.
Number of requests can be reduced by 33 (34%)
97
64
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1626. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
1626.com
9241 ms
www.1626.com
9410 ms
0e3ea8f2df1eaa414e9b2b1e6f0780e6.css
7563 ms
35ba02a387132394046d0e59f9335cd0.js
11016 ms
dbbd918be12556f13421182e6ffb0a52.js
3923 ms
subcode.gif
8727 ms
top_pro_ios.jpg
1750 ms
top_pro_and.jpg
3824 ms
56a18a0dd0cad.jpg
19734 ms
56d3a33e874f2.jpg
19735 ms
56cfab85e7159.jpg
19736 ms
56ce62bc786e2.jpg
19738 ms
56cd1496caa18.jpg
19739 ms
56a18a0dd0cad_990x290.jpg
12923 ms
56d3a33e874f2_990x290.jpg
19460 ms
zixun.php
1261 ms
followbutton.php
4453 ms
analytics.js
41 ms
hm.js
868 ms
mvl.js
2597 ms
atrk.js
49 ms
service.php
960 ms
collect
24 ms
atrk.gif
32 ms
test.png
313 ms
hm.gif
435 ms
1626.woff
18650 ms
mba.js
10140 ms
mv.js
6 ms
b
3134 ms
t
4352 ms
followButton.css
1992 ms
kafeise.jpg
16918 ms
sso.js
671 ms
followButton.js
676 ms
suda.js
684 ms
bg_flbtn.png
3 ms
b.gif
3210 ms
ckmap.htm
12965 ms
kaqise.jpg
20008 ms
t
10355 ms
yingguangse.jpg
8115 ms
m
2355 ms
yuanmuse.jpg
3328 ms
dianduse.jpg
1004 ms
yinhua.jpg
1669 ms
suihua.jpg
1675 ms
touming.jpg
1738 ms
tiaowen.jpg
4926 ms
bodian.jpg
2346 ms
gezi.jpg
3466 ms
micai.jpg
3015 ms
shewen.jpg
8917 ms
baowen.jpg
3686 ms
banmawen.jpg
19986 ms
32206577188a87fa59a31e7a0aac7224KaQKSr_310x310.jpg
4848 ms
35_1447967337_middle.jpg
4025 ms
40d7e33c50efec358f8194a98bc091a3t96tq2_310x310.jpg
5303 ms
68_1402702625_middle.jpg
7186 ms
06c33291b3791643b1da302ca8f3734aTLUlKE_310x310.jpg
6571 ms
82_1451959703_middle.jpg
5639 ms
a6419e587bd9ade4e7fc6f52fd703e4aCB9AOo_310x310.jpg
8362 ms
22_1404632821_middle.jpg
6908 ms
6c22058585ea84a1a3e79d27cd5ea238FZzU70_310x310.jpg
7575 ms
noavatar_middle.jpg
7624 ms
c93a36321b3e12386f01c15b7301b80edVuQ33_310x310.jpg
8247 ms
11f1ab2c6e7657729ad0e0920ff68971EicwOO_310x310.jpg
12397 ms
40_1433229487_middle.jpg
9461 ms
2ddc03ffe45401e9789830ef49144e2530PXj8_310x310.jpg
10251 ms
90_1398644613_middle.jpg
9351 ms
bb965d6a61ec50975b3cdd1da12cafccpX6mF7_310x310.jpg
11212 ms
65_1448233800_middle.jpg
10381 ms
79d48a755f08230216e8a55acda515d106nCNz_310x310.jpg
12325 ms
23_1449529858_middle.jpg
11474 ms
26f1545ed63312e6db0a351fa3bf16a6xNHMCq_310x310.jpg
10817 ms
6b7dced6abdcf8df5d0050188fa932110S9pDQ_310x310.jpg
10607 ms
30ea77663c15451c4a23e90d29328987Hj37M3_310x310.jpg
12414 ms
c1dc738406d4d43d9b3d4d514471cde2iQ7lFq_310x310.jpg
11135 ms
4ddd5a89983ef77e7707ea8d6a1304d0kJqFw9_310x310.jpg
13289 ms
10_1415145260_middle.jpg
10907 ms
67942c09639fcdae54a23afcf1c61dd62pp27z_310x310.jpg
12885 ms
751e72992703d3e645a00ec78ff53685343z43_310x310.jpg
13601 ms
bc5af470948090508543ee01c3c3711aOI63OF_310x310.jpg
11478 ms
div_close.jpg
13236 ms
zx_botfx_01.jpg
11216 ms
zx_botfx_02.jpg
11664 ms
mk_let_icon01.jpg
11539 ms
mk_let_icon02.jpg
16249 ms
hi_icon.png
20135 ms
hi_icon.png
20068 ms
indtop-search.gif
11999 ms
top_pro_img.png
20341 ms
hi_modle_bg02.gif
11170 ms
float_mfs.png
14304 ms
back-topind.jpg
13427 ms
go-flashimg_05.jpg
16408 ms
hi_icon.png
20355 ms
moneyicon-s.png
14128 ms
pagina-ban01.png
16163 ms
pagination.gif
15417 ms
1626.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
1626.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
1626.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
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1626.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 1626.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.
1626.com
Open Graph description is not detected on the main page of 1626. 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: