Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

grandstar.blog.com

(GrandStar)玄辰 | 【御剑乘风来,除魔天地间,有酒乐逍遥,无酒我亦癫,一饮尽江河,再饮吞日月,千杯醉不倒,惟我酒剑仙】

Page Load Speed

8.5 sec in total

First Response

468 ms

Resources Loaded

6 sec

Page Rendered

2.1 sec

grandstar.blog.com screenshot

About Website

Welcome to grandstar.blog.com homepage info - get ready to check Grand Star Blog best content for China right away, or after learning these important things about grandstar.blog.com

【御剑乘风来,除魔天地间,有酒乐逍遥,无酒我亦癫,一饮尽江河,再饮吞日月,千杯醉不倒,惟我酒剑仙】

Visit grandstar.blog.com

Key Findings

We analyzed Grandstar.blog.com page load time and found that the first response time was 468 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

grandstar.blog.com performance score

0

Network Requests Diagram

grandstar.blog.com

468 ms

style.css

217 ms

admin-bar.css

215 ms

blogcom-admin-bar.css

218 ms

nggallery.css

224 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Grandstar.blog.com, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Yui.yahooapis.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Grandstar.blog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 773.5 kB (10%)

Content Size

7.6 MB

After Optimization

6.8 MB

In fact, the total size of Grandstar.blog.com main page is 7.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 36.2 kB

  • Original 49.2 kB
  • After minification 47.2 kB
  • After compression 13.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 36.2 kB or 74% of the original size.

Image Optimization

-8%

Potential reduce by 610.5 kB

  • Original 7.3 MB
  • After minification 6.7 MB

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. Grand Star Blog images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 104.0 kB

  • Original 190.1 kB
  • After minification 183.9 kB
  • After compression 86.0 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 104.0 kB or 55% of the original size.

CSS Optimization

-78%

Potential reduce by 22.8 kB

  • Original 29.1 kB
  • After minification 22.1 kB
  • After compression 6.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. Grandstar.blog.com needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (41%)

Requests Now

63

After Optimization

37

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

SEO Factors

grandstar.blog.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Open Graph data is detected on the main page of Grand Star Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: