Tools & Wizards About Us
blog.m148.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.m148.com

www.m148.com-官网首页

Page Load Speed

31.4 sec in total

First Response

787 ms

Resources Loaded

30.3 sec

Page Rendered

267 ms

blog.m148.com screenshot

About Website

Click here to check amazing Blog M 148 content for China. Otherwise, check out these important facts you probably never knew about blog.m148.com

百度熊掌收录-纵横法律网-10-19年记录-历史百度权重3-桔子高评分-外链超多

Visit blog.m148.com

Key Findings

We analyzed Blog.m148.com page load time and found that the first response time was 787 ms and then it took 30.6 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.

Performance Metrics

blog.m148.com performance score

0

Network Requests Diagram

blog.m148.com

787 ms

blog.m1488.com

2744 ms

base.css

5160 ms

blog_m.css

2930 ms

JavaScript.js

19942 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Blog.m148.com, 65% (24 requests) were made to Img.m1488.com and 14% (5 requests) were made to Avatar.m1488.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Js.m1488.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.7 kB (28%)

Content Size

192.4 kB

After Optimization

137.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.m148.com main page is 192.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. 20% of websites need less resources to load. Images take 125.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.1 kB

  • Original 30.1 kB
  • After minification 29.7 kB
  • After compression 7.0 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.1 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 5.5 kB

  • Original 125.5 kB
  • After minification 120.0 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. Blog M 148 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 11.3 kB

  • Original 17.7 kB
  • After minification 16.4 kB
  • After compression 6.4 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 11.3 kB or 64% of the original size.

CSS Optimization

-78%

Potential reduce by 14.9 kB

  • Original 19.2 kB
  • After minification 18.2 kB
  • After compression 4.2 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.m148.com needs all CSS files to be minified and compressed as it can save up to 14.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (34%)

Requests Now

35

After Optimization

23

  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog M 148. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

blog.m148.com

blog.m148.com

787 ms

blog.m1488.com

blog.m1488.com

2744 ms

base.css

base.css

5160 ms

blog_m.css

blog_m.css

2930 ms

JavaScript.js

JavaScript.js

19942 ms

focus.js

focus.js

2975 ms

footer_o.js

footer_o.js

3571 ms

bg_m148.gif

bg_m148.gif

665 ms

avatar-s.jpg

avatar-s.jpg

2917 ms

m148logo.png

m148logo.png

1955 ms

blog_logo.gif

blog_logo.gif

1850 ms

112311-5461.jpg

112311-5461.jpg

1892 ms

113206-3710.jpg

113206-3710.jpg

2558 ms

113926-7956.jpg

113926-7956.jpg

1975 ms

111430-6980.jpg

111430-6980.jpg

2461 ms

110755-2017.jpg

110755-2017.jpg

3130 ms

13.gif

13.gif

2596 ms

vip0.gif

vip0.gif

2624 ms

0.gif

0.gif

3085 ms

6.gif

6.gif

3225 ms

5.gif

5.gif

3252 ms

24.gif

24.gif

3301 ms

vip1.gif

vip1.gif

3775 ms

avatar-s.jpg

avatar-s.jpg

2893 ms

avatar-s.jpg

avatar-s.jpg

2932 ms

avatar-s.jpg

avatar-s.jpg

3279 ms

avatar-s.jpg

avatar-s.jpg

3612 ms

m148_navbg.png

m148_navbg.png

6514 ms

main_navbg.png

main_navbg.png

3854 ms

nav_icon.png

nav_icon.png

4712 ms

blog_bg.png

blog_bg.png

4712 ms

button_11.gif

button_11.gif

906 ms

stat.php

stat.php

2146 ms

bar_bg.gif

bar_bg.gif

6023 ms

stat.htm

stat.htm

416 ms

core.php

core.php

1328 ms

9.gif

9.gif

3283 ms

SEO Factors

blog.m148.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.m148.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Blog.m148.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.

Social Sharing Optimization

blog.m148.com

Open Graph description is not detected on the main page of Blog M 148. 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: