33.1 sec in total
2.3 sec
30.3 sec
528 ms
Visit 520101.com now to see the best up-to-date 520101 content for China and also check out these interesting facts you probably never knew about 520101.com
家电维修资料网是一个集合家电维修经验交流与技术分享的综合网站,提供丰富的维修资料和图纸与刷机数据固件。
Visit 520101.comWe analyzed 520101.com page load time and found that the first response time was 2.3 sec and then it took 30.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.
520101.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value6.8 s
8/100
25%
Value11.4 s
5/100
10%
Value3,010 ms
3/100
30%
Value0.395
26/100
15%
Value16.5 s
6/100
10%
2323 ms
1142 ms
758 ms
766 ms
840 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 39% of them (32 requests) were addressed to the original 520101.com, 9% (7 requests) were made to Pos.baidu.com and 7% (6 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source T12.baidu.com.
Page size can be reduced by 567.5 kB (52%)
1.1 MB
517.5 kB
In fact, the total size of 520101.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. 40% of websites need less resources to load. Javascripts take 698.2 kB which makes up the majority of the site volume.
Potential reduce by 90.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 90.4 kB or 83% of the original size.
Potential reduce by 16.5 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. 520101 images are well optimized though.
Potential reduce by 440.7 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 440.7 kB or 63% of the original size.
Potential reduce by 19.9 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. 520101.com needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 83% of the original size.
Number of requests can be reduced by 38 (49%)
77
39
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 520101. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
520101.com
2323 ms
cssmain.css
1142 ms
other.css
758 ms
mian.js
766 ms
focus.js
840 ms
banner.js
853 ms
banner3.js
1142 ms
show_ads.js
8 ms
c.js
987 ms
stat.php
1504 ms
cssindex.css
383 ms
2013063000244818217.jpg
3078 ms
ehaier.jpg
4230 ms
logo.gif
6028 ms
logo.gif
4534 ms
logo.png
1944 ms
2013062923454496964.jpg
2370 ms
20155261253813967.jpg
3246 ms
201541711354194338.jpg
3268 ms
2015060811200032049.jpg
2981 ms
2015070511293233282.jpg
4663 ms
2015070510360449035.jpg
7992 ms
2013092620534595763.jpg
5009 ms
2013100723453428551.jpg
5461 ms
bg.gif
379 ms
bg_top.gif
379 ms
logo.gif
417 ms
class_ar.gif
379 ms
fmdiylogo.gif
1633 ms
kcnm
980 ms
kcnm
1117 ms
nav_001.gif
382 ms
nav_002.gif
381 ms
nav_003.gif
461 ms
nav_000.gif
381 ms
ca-pub-8423476013912015.js
98 ms
zrt_lookup.html
140 ms
show_ads_impl.js
93 ms
search.gif
437 ms
dot.gif
735 ms
focusb.gif
733 ms
focusa.gif
7646 ms
fb.jpg
4912 ms
title1_r2.gif
807 ms
kcnm
1380 ms
ads
242 ms
osd.js
6 ms
ads
228 ms
m_js_controller.js
18 ms
abg.js
35 ms
favicon
54 ms
favicon
49 ms
googlelogo_color_112x36dp.png
63 ms
mobile_unified_button_icon_white.png
40 ms
s
30 ms
x_button_blue2.png
7 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
6 ms
stat.htm
553 ms
core.php
745 ms
kcnm
743 ms
kcnm
1650 ms
9.gif
2115 ms
kcnm
2935 ms
activeview
13 ms
adx.php
719 ms
reduce_bd-logo1_oper.png
500 ms
app.gif
1011 ms
u=795594825,4085260015&fm=76
2573 ms
u=1397038772,2124887696&fm=76
3324 ms
u=355982539,248578341&fm=76
6424 ms
u=1436033464,1876602957&fm=76
6668 ms
u=966502125,1160878830&fm=76
5076 ms
u=1926100116,2773192077&fm=76
3576 ms
u=1391018993,690726417&fm=76
20497 ms
closefeedback.min.js
529 ms
o.htm
1241 ms
ui
51 ms
reduce_promotion_oper.png
506 ms
bd_logo.png
502 ms
bg_rb.png
509 ms
ac.js
485 ms
wh.js
758 ms
520101.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
520101.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
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
520101.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 520101.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 520101.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
520101.com
Open Graph description is not detected on the main page of 520101. 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: