18.5 sec in total
1.8 sec
16.6 sec
126 ms
Visit blog.cofface.com now to see the best up-to-date Blog Cofface content for China and also check out these interesting facts you probably never knew about blog.cofface.com
Cofface Blog-国内Android(安卓)第三方Rom/Recovery/Root开发
Visit blog.cofface.comWe analyzed Blog.cofface.com page load time and found that the first response time was 1.8 sec and then it took 16.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
blog.cofface.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.5 s
65/100
25%
Value4.5 s
73/100
10%
Value0 ms
100/100
30%
Value0.149
76/100
15%
Value3.2 s
94/100
10%
1782 ms
242 ms
467 ms
700 ms
468 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 25% of them (17 requests) were addressed to the original Blog.cofface.com, 12% (8 requests) were made to Img.t.sinajs.cn and 9% (6 requests) were made to Tp3.sinaimg.cn. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Widget.weibo.com.
Page size can be reduced by 467.2 kB (67%)
701.2 kB
234.0 kB
In fact, the total size of Blog.cofface.com main page is 701.2 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. 40% of websites need less resources to load. Javascripts take 368.8 kB which makes up the majority of the site volume.
Potential reduce by 16.6 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 16.6 kB or 75% of the original size.
Potential reduce by 8.9 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, Blog Cofface needs image optimization as it can save up to 8.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 252.1 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 252.1 kB or 68% of the original size.
Potential reduce by 189.5 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. Blog.cofface.com needs all CSS files to be minified and compressed as it can save up to 189.5 kB or 83% of the original size.
Number of requests can be reduced by 26 (40%)
65
39
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Cofface. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
blog.cofface.com
1782 ms
wp-emoji-release.min.js
242 ms
jquery.fancybox-1.3.4.css
467 ms
bootstrap.min.css
700 ms
font-awesome.min.css
468 ms
main.css
474 ms
jquery.min.js
718 ms
jquery.fancybox-1.3.4.js
482 ms
front.js
697 ms
bootstrap.min.js
709 ms
loader.js
710 ms
wp-embed.min.js
713 ms
index.php
7151 ms
logo5.png
240 ms
stat.php
1788 ms
fontawesome-webfont.woff
929 ms
stat.htm
247 ms
core.php
1255 ms
9.gif
1277 ms
online_v3.php
1745 ms
main.js
469 ms
ias.min.js
237 ms
signpop.js
469 ms
app.gif
4889 ms
weiboShow.css
1620 ms
skin_default.css
1622 ms
gaea_1_19.js
1479 ms
show.js
1071 ms
suda.js
1071 ms
1
3599 ms
a13fe932gw1f1gk8zhy2tj20k00zk10e.jpg
86 ms
70d923a0gw1f1evf0lpvuj20c815p0ti.jpg
368 ms
a13fe932gw1f1d0y0am5dj20k00zk0zc.jpg
1617 ms
a13fe932gw1f1bravfuthj20k00zkmzh.jpg
1461 ms
1
580 ms
1
4321 ms
1
70 ms
1
4499 ms
1
4312 ms
1
4616 ms
1
4319 ms
1
336 ms
1
328 ms
1
517 ms
c087c063gw1f0n6bveqixj20yg5g27nr.jpg
70 ms
a13fe932gw1f152aolbaoj20ku112gnp.jpg
356 ms
a13fe932gw1f14t6wh3ldj20a601374b.jpg
348 ms
61e89b74jw1f107eyzacqj20hs0vkq5s.jpg
351 ms
1
192 ms
1
68 ms
1
65 ms
0
65 ms
1
63 ms
1
3563 ms
0
3751 ms
1
3570 ms
1
3568 ms
0
3548 ms
wb_logo16_a.png
56 ms
icon_user.png
58 ms
btns_bg.png
57 ms
icon_follow.png
58 ms
a13fe932gw1f13ni3foq8j20it0ca76x.jpg
1591 ms
61e61e8cjw1f0kzifoxtej208b04o748.jpg
1598 ms
bg_trans.png
14 ms
icon_tips.png
15 ms
a.gif
5185 ms
tmp.gif
1427 ms
blog.cofface.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
blog.cofface.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
blog.cofface.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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.cofface.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 Blog.cofface.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.
blog.cofface.com
Open Graph description is not detected on the main page of Blog Cofface. 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: