10.8 sec in total
924 ms
6 sec
3.9 sec
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 924 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
1626.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.4 s
40/100
25%
Value32.4 s
0/100
10%
Value590 ms
50/100
30%
Value0.786
5/100
15%
Value60.1 s
0/100
10%
924 ms
972 ms
944 ms
1785 ms
269 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original 1626.com, 96% (54 requests) were made to Nwzimg.wezhan.cn. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Nwzimg.wezhan.cn.
Page size can be reduced by 352.9 kB (9%)
4.0 MB
3.6 MB
In fact, the total size of 1626.com main page is 4.0 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. 40% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 92.7 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 13.0 kB, which is 12% 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 92.7 kB or 86% of the original size.
Potential reduce by 211.3 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. 1626 images are well optimized though.
Potential reduce by 40.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 40.3 kB or 20% of the original size.
Potential reduce by 8.6 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 8.6 kB or 34% of the original size.
Number of requests can be reduced by 31 (58%)
53
22
The browser has sent 53 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 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
1626.com
924 ms
1626.com
972 ms
30536_zh-cn.html.Head.js
944 ms
30536_zh-cn.html.Body.js
1785 ms
pcstyle.css
269 ms
reset.css
271 ms
iconfont.css
272 ms
iconfont.css
269 ms
iconfont.css
273 ms
pager.css
489 ms
hover-effects.css
493 ms
antChain.css
492 ms
30536_Pc_zh-CN.css
1112 ms
jquery-3.6.3.min.js
524 ms
jquery.lazyload.min.js
712 ms
smart.animation.min.js
728 ms
kino.razor.min.js
714 ms
common.min.js
754 ms
admin.validator.min.js
935 ms
jquery.cookie.js
937 ms
jssor.slider-22.2.16-all.min.js
970 ms
jquery.jqueryzoom.js
976 ms
slideshow.js
1053 ms
jqPaginator.min.js
1158 ms
31557325.png
222 ms
polyfill.min.js
232 ms
slicknav.css
226 ms
jquery.slicknav.min.js
234 ms
modernizr.min.js
229 ms
ResponsiveJsLoader.js
224 ms
31558062.png
413 ms
31557584.png
447 ms
31558146.png
446 ms
31542880.jpg
450 ms
31572427.png
452 ms
49663757.jpg
594 ms
49663760.jpg
839 ms
49663762.jpg
965 ms
49663764.jpg
867 ms
49663766.jpg
1101 ms
49968879.jpg
872 ms
49966973.jpg
822 ms
49967630.jpg
1056 ms
49967390.jpg
1071 ms
49951345.jpeg
1265 ms
49855525.jpg
1289 ms
49831336.jpg
1345 ms
49827208.jpg
1334 ms
49824245.jpg
1394 ms
49824431.png
1554 ms
49763378.jpg
1744 ms
49712585.jpg
1725 ms
31543339.png
1556 ms
ga_icon.png
1566 ms
iconfont.woff
1565 ms
Core-Babeled.js
614 ms
1626.com 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.
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
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
Links do not have a discernible name
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
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
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: