10.8 sec in total
2 sec
8.7 sec
154 ms
Visit 521.im now to see the best up-to-date 521 content and also check out these interesting facts you probably never knew about 521.im
Visit 521.imWe analyzed 521.im page load time and found that the first response time was 2 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
521.im performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value9.4 s
0/100
25%
Value8.6 s
17/100
10%
Value390 ms
69/100
30%
Value0.153
75/100
15%
Value11.6 s
18/100
10%
1967 ms
245 ms
2056 ms
310 ms
253 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 92% of them (49 requests) were addressed to the original 521.im, 4% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.useso.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Clicki.cn.
Page size can be reduced by 233.8 kB (38%)
614.3 kB
380.6 kB
In fact, the total size of 521.im main page is 614.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 342.9 kB which makes up the majority of the site volume.
Potential reduce by 23.2 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 4.3 kB, which is 14% 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 23.2 kB or 76% of the original size.
Potential reduce by 46.0 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, 521 needs image optimization as it can save up to 46.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 139.2 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 139.2 kB or 67% of the original size.
Potential reduce by 25.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. 521.im needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 80% of the original size.
Number of requests can be reduced by 17 (34%)
50
33
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 521. 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.
521.im
1967 ms
style.css
245 ms
css
2056 ms
jquery.js
310 ms
jquery.nivo.slider.pack.js
253 ms
all.js
249 ms
fancybox.css
252 ms
jquery.js
314 ms
jquery.fancybox.js
312 ms
header_bg.jpg
90 ms
logo.png
161 ms
facepic_border.png
104 ms
fb2d11d5d9149c4255a337ad7cd332b0-120.jpg
99 ms
leftarrow.png
102 ms
rightarrow.png
100 ms
line.png
159 ms
thumb-overlay.png
160 ms
moren7.jpg
215 ms
author.png
161 ms
cate.png
161 ms
time.png
170 ms
comment.png
206 ms
view.png
216 ms
timthumb.php
398 ms
timthumb.php
402 ms
timthumb.php
455 ms
timthumb.php
559 ms
click.png
396 ms
timthumb.php
607 ms
timthumb.php
529 ms
timthumb.php
1039 ms
timthumb.php
1034 ms
timthumb.php
1045 ms
0184c6c74790bbcaa039d43320728d18-120.jpg
597 ms
9a63d5ba1d2b6829c735533294da7919-40.jpg
666 ms
73924b151d3cf8d9a0feb08f6ed9419a-40.jpg
671 ms
50de9e6a6a10a38217b32980c5e572cb-40.jpg
675 ms
fb2d11d5d9149c4255a337ad7cd332b0-40.jpg
735 ms
slide1.jpg
806 ms
slide2.jpg
879 ms
slide3.jpg
869 ms
slide4.jpg
950 ms
search_btn.png
935 ms
footer-bg.png
909 ms
down-arrow.png
953 ms
EFpQQyG9GqCrobXxL-KRMXbFhgvWbfSbdVg11QabG8w.woff
40 ms
s-BiyweUPV0v-yRb-cjciL3hpw3pgy2gAi-Ip7WPMi0.woff
41 ms
right-shadow.png
967 ms
50016
4542 ms
left-shadow.png
932 ms
footer-top-bg.png
989 ms
footer-widgets-bg.png
996 ms
slider.png
998 ms
521.im 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.
521.im best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
521.im SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 521.im 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), while the claimed language is Chinese. Our system also found out that 521.im 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.
521.im
Open Graph description is not detected on the main page of 521. 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: