31.3 sec in total
2.5 sec
27.1 sec
1.6 sec
Visit a1pass.blog.163.com now to see the best up-to-date A1Pass Blog 163 content for China and also check out these interesting facts you probably never knew about a1pass.blog.163.com
Visit a1pass.blog.163.comWe analyzed A1pass.blog.163.com page load time and found that the first response time was 2.5 sec and then it took 28.8 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 were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
a1pass.blog.163.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value6.5 s
9/100
25%
Value11.2 s
5/100
10%
Value620 ms
48/100
30%
Value0.701
7/100
15%
Value6.3 s
61/100
10%
2466 ms
54 ms
972 ms
1182 ms
115 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original A1pass.blog.163.com, 20% (11 requests) were made to B.bst.126.net and 18% (10 requests) were made to Api.blog.163.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source D.hackav.com.
Page size can be reduced by 581.1 kB (45%)
1.3 MB
718.4 kB
In fact, the total size of A1pass.blog.163.com 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. 20% of websites need less resources to load. Images take 530.6 kB which makes up the majority of the site volume.
Potential reduce by 112.1 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 112.1 kB or 81% of the original size.
Potential reduce by 9.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. A1Pass Blog 163 images are well optimized though.
Potential reduce by 310.5 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 310.5 kB or 69% of the original size.
Potential reduce by 149.3 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. A1pass.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.3 kB or 82% of the original size.
Number of requests can be reduced by 29 (60%)
48
19
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A1Pass Blog 163. 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.
a1pass.blog.163.com
2466 ms
c.css
54 ms
b.css
972 ms
6630133180817252049.jpg
1182 ms
xcode.png
115 ms
1.0.0.js
179 ms
pc.js
241 ms
ph.js
227 ms
5727734301085237150.jpg
20153 ms
icon.png
583 ms
5735052650479714472.jpg
858 ms
5735052650479714337.jpg
867 ms
5727734301085237158.jpg
1257 ms
5735052650479714336.jpg
1265 ms
lnkbar.png
526 ms
image.png
530 ms
arrow24.png
531 ms
newtopbaricon8.png
530 ms
crossdomain.html
1049 ms
crossdomain.html
1818 ms
request.s
1691 ms
analyse.png
20417 ms
ava.s
4354 ms
crossdomain.html
853 ms
analyse.png
20192 ms
analytics.js
133 ms
collect
50 ms
BlogBeanNew.getHostHotBlogs.dwr
1029 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
2209 ms
blogPhotoAd
19998 ms
close_01.png
14 ms
top_bg.png
26 ms
bottom_bg.png
25 ms
left_bg.png
28 ms
right_bg.png
28 ms
left_top.png
28 ms
right_top.png
27 ms
left_bottom.png
41 ms
right_bottom.png
40 ms
shadow.png
12 ms
SetupBeanNew.getCustomModulesData.dwr
1115 ms
SetupBeanNew.getResourceModulesData.dwr
1137 ms
HomeBeanNew.getAccessStatistics.dwr
5813 ms
NoteBeanNew.getNotesForPrev.dwr
1092 ms
BlogBeanNew.getBlogClasses.dwr
1880 ms
VoteBean.getVotesByUserId.dwr
19760 ms
PhotoBlogBean.getHeadPic.dwr
3258 ms
face0.gif
73 ms
mailme_5.png
2129 ms
88x31.png
317 ms
aonepass.jpg
20499 ms
3205437034781687037.jpg
1737 ms
BgsBean.getBgsUserByUserId.dwr
983 ms
3339700598673024954.jpg
3101 ms
6598072521262116486.jpg
1607 ms
a1pass.blog.163.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
Form elements do not have associated labels
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.
a1pass.blog.163.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
a1pass.blog.163.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
ZH
ZH
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A1pass.blog.163.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that A1pass.blog.163.com main page’s claimed encoding is gbk. 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.
a1pass.blog.163.com
Open Graph description is not detected on the main page of A1Pass Blog 163. 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: