14.9 sec in total
1.4 sec
12.6 sec
916 ms
Click here to check amazing Cwrblog content. Otherwise, check out these important facts you probably never knew about cwrblog.net
致力于能源电力、铁路建设、建筑施工等领域的信息化技术研究与创新应用
Visit cwrblog.netWe analyzed Cwrblog.net page load time and found that the first response time was 1.4 sec and then it took 13.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cwrblog.net performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.014
100/100
15%
Value0
0/100
10%
1372 ms
1398 ms
1447 ms
1388 ms
1386 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 90% of them (35 requests) were addressed to the original Cwrblog.net, 3% (1 request) were made to Emlog.com and 3% (1 request) were made to Img.baidu.com. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Js.users.51.la.
Page size can be reduced by 591.3 kB (21%)
2.9 MB
2.3 MB
In fact, the total size of Cwrblog.net main page is 2.9 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. 30% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 23.7 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 23.7 kB or 71% of the original size.
Potential reduce by 476.6 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, Cwrblog needs image optimization as it can save up to 476.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 77.3 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 77.3 kB or 72% of the original size.
Potential reduce by 13.7 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. Cwrblog.net needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 78% of the original size.
Number of requests can be reduced by 3 (8%)
37
34
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cwrblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
cwrblog.net
1372 ms
style.css
1398 ms
Sean_flash.js
1447 ms
Sean_script.js
1388 ms
tj.js
1386 ms
yd.gif
518 ms
jyb_logo.png
235 ms
logo-80px.gif
985 ms
search.png
150 ms
tyc.gif
506 ms
dyyl.jpg
324 ms
topjyb.gif
346 ms
mid1jyb.jpg
271 ms
mid2jyb.gif
544 ms
mid3.jpg
401 ms
bottomjyb.gif
522 ms
bg_gnbtop.gif
150 ms
btn_srch.gif
151 ms
icon_02.png
148 ms
loading.gif
152 ms
1.jpg
199 ms
2.jpg
252 ms
3.jpg
213 ms
4.jpg
285 ms
news_nbg1.gif
216 ms
icon_3.png
159 ms
5.jpg
223 ms
6.jpg
264 ms
7.jpg
272 ms
8.jpg
290 ms
9.jpg
351 ms
10.jpg
319 ms
icon_01.gif
328 ms
34.png
399 ms
33.png
995 ms
32.png
998 ms
72.png
791 ms
71.png
801 ms
17709036.js
9536 ms
cwrblog.net accessibility score
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
<frame> or <iframe> elements do not have a title
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
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.
cwrblog.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
cwrblog.net SEO score
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 Cwrblog.net 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 Cwrblog.net 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.
cwrblog.net
Open Graph description is not detected on the main page of Cwrblog. 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: