27.9 sec in total
2.1 sec
24.9 sec
872 ms
Welcome to ca178.blog.163.com homepage info - get ready to check Ca 178 Blog 163 best content for China right away, or after learning these important things about ca178.blog.163.com
Visit ca178.blog.163.comWe analyzed Ca178.blog.163.com page load time and found that the first response time was 2.1 sec and then it took 25.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 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ca178.blog.163.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value7.0 s
6/100
25%
Value12.2 s
3/100
10%
Value550 ms
54/100
30%
Value0.75
6/100
15%
Value5.9 s
65/100
10%
2144 ms
138 ms
80 ms
312 ms
298 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Ca178.blog.163.com, 36% (29 requests) were made to B.bst.126.net and 23% (18 requests) were made to Os.blog.163.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Lofter.com.
Page size can be reduced by 538.1 kB (59%)
906.4 kB
368.3 kB
In fact, the total size of Ca178.blog.163.com main page is 906.4 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. 45% of websites need less resources to load. Javascripts take 455.0 kB which makes up the majority of the site volume.
Potential reduce by 66.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 66.5 kB or 78% 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. Ca 178 Blog 163 images are well optimized though.
Potential reduce by 313.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 313.8 kB or 69% of the original size.
Potential reduce by 148.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. Ca178.blog.163.com needs all CSS files to be minified and compressed as it can save up to 148.6 kB or 82% of the original size.
Number of requests can be reduced by 40 (53%)
76
36
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ca 178 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 14 to 1 for JavaScripts and as a result speed up the page load time.
ca178.blog.163.com
2144 ms
c.css
138 ms
nb.css
80 ms
top_banner.jpg
312 ms
icon.png
298 ms
6630133180817252049.jpg
1033 ms
1.0.0.js
647 ms
pc.js
263 ms
ph.js
264 ms
lnkbar.png
251 ms
image.png
252 ms
arrow24.png
252 ms
newtopbaricon8.png
254 ms
bg_tab.gif
249 ms
top_on.gif
254 ms
bg_titlebar.gif
254 ms
bg_l_titlebar.gif
253 ms
bg_r_titlebar.gif
254 ms
bg_web_b.gif
254 ms
xcode.png
255 ms
crossdomain.html
1064 ms
crossdomain.html
1897 ms
crossdomain.html
853 ms
request.s
720 ms
analyse.png
19866 ms
ava.s
1512 ms
loftericon.png
1738 ms
nb.css
45 ms
ava.s
1083 ms
background.gif
19 ms
player_02.gif
17 ms
player_06.gif
17 ms
player_16.gif
17 ms
player_17.gif
16 ms
player_23.gif
16 ms
timeline_1.gif
25 ms
player_29.gif
24 ms
analyse.png
19677 ms
analytics.js
16 ms
collect
16 ms
HomeBeanNew.getFriends.dwr
712 ms
HomeBeanNew.getAccessStatistics.dwr
2202 ms
UserBeanNew.getVisitor.dwr
2148 ms
NoteBeanNew.getNotesForPrev.dwr
2326 ms
FeelingsBeanNew.getRecentFeelingCards.dwr
1432 ms
MusicBeanNew.setCopyrightMusicSessionToken.dwr
1435 ms
blogPhotoAd
20486 ms
close_01.png
12 ms
top_bg.png
19 ms
bottom_bg.png
19 ms
left_bg.png
18 ms
right_bg.png
20 ms
left_top.png
17 ms
right_top.png
37 ms
left_bottom.png
47 ms
right_bottom.png
49 ms
shadow.png
34 ms
ava.s
884 ms
UserSpaceBean.getUserSpace.dwr
931 ms
ava.s
1937 ms
ava.s
4150 ms
ava.s
790 ms
ava.s
789 ms
ava.s
2631 ms
ava.s
1078 ms
ava.s
1174 ms
ava.s
1171 ms
ava.s
1583 ms
ava.s
1555 ms
ava.s
1556 ms
ava.s
1949 ms
ava.s
3419 ms
ava.s
2130 ms
ava.s
3695 ms
BgsBean.getBgsUserByUserId.dwr
1508 ms
24189263160143.js
4199 ms
-1.gif
18 ms
29686821299019.js
2126 ms
empty.png
12 ms
111464090777903243.jpg
758 ms
ca178.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.
ca178.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
ca178.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 Ca178.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 Ca178.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.
ca178.blog.163.com
Open Graph description is not detected on the main page of Ca 178 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: