Tools & Wizards About Us
yhasdfgh2348.blog.163.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 38

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

Page Load Speed

16.8 sec in total

First Response

1.6 sec

Resources Loaded

14.7 sec

Page Rendered

450 ms

yhasdfgh2348.blog.163.com screenshot

About Website

Welcome to yhasdfgh2348.blog.163.com homepage info - get ready to check Yhasdfgh 2348 Blog 163 best content for China right away, or after learning these important things about yhasdfgh2348.blog.163.com

Visit yhasdfgh2348.blog.163.com

Key Findings

We analyzed Yhasdfgh2348.blog.163.com page load time and found that the first response time was 1.6 sec and then it took 15.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

yhasdfgh2348.blog.163.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.749

6/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

yhasdfgh2348.blog.163.com

1592 ms

c.css

9 ms

b.css

726 ms

6630914933582973314.jpg

1702 ms

2139491298077965264.jpg

1135 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Yhasdfgh2348.blog.163.com, 23% (11 requests) were made to B.bst.126.net and 17% (8 requests) were made to B2.bst.126.net. The less responsive or slowest element that took the longest time to load (7.3 sec) relates to the external source Lofter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 595.1 kB (48%)

Content Size

1.2 MB

After Optimization

636.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yhasdfgh2348.blog.163.com main page is 1.2 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. Javascripts take 521.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 77.4 kB

  • Original 97.6 kB
  • After minification 97.5 kB
  • After compression 20.1 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 77.4 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 10.1 kB

  • Original 430.7 kB
  • After minification 420.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. Yhasdfgh 2348 Blog 163 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 358.6 kB

  • Original 521.7 kB
  • After minification 521.7 kB
  • After compression 163.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 358.6 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 149.0 kB

  • Original 181.7 kB
  • After minification 177.8 kB
  • After compression 32.8 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. Yhasdfgh2348.blog.163.com needs all CSS files to be minified and compressed as it can save up to 149.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (56%)

Requests Now

45

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yhasdfgh 2348 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 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

yhasdfgh2348.blog.163.com

yhasdfgh2348.blog.163.com

1592 ms

c.css

c.css

9 ms

b.css

b.css

726 ms

6630914933582973314.jpg

6630914933582973314.jpg

1702 ms

2139491298077965264.jpg

2139491298077965264.jpg

1135 ms

6630133180817252049.jpg

6630133180817252049.jpg

1211 ms

xcode.png

xcode.png

7 ms

1.0.0.js

1.0.0.js

75 ms

pc.js

pc.js

9 ms

ph.js

ph.js

9 ms

3944308848663575603.jpg

3944308848663575603.jpg

4509 ms

icon.png

icon.png

62 ms

lnkbar.png

lnkbar.png

62 ms

image.png

image.png

61 ms

arrow24.png

arrow24.png

61 ms

newtopbaricon8.png

newtopbaricon8.png

62 ms

crossdomain.html

crossdomain.html

860 ms

crossdomain.html

crossdomain.html

1128 ms

request.s

request.s

650 ms

analyse.png

analyse.png

3329 ms

empty.png

empty.png

22 ms

ava.s

ava.s

2474 ms

crossdomain.html

crossdomain.html

2119 ms

analyse.png

analyse.png

7270 ms

analytics.js

analytics.js

4 ms

collect

collect

11 ms

SetupBeanNew.getCustomModulesData.dwr

SetupBeanNew.getCustomModulesData.dwr

920 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

1386 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

1296 ms

blogPhotoAd

blogPhotoAd

1314 ms

close_01.png

close_01.png

6 ms

top_bg.png

top_bg.png

10 ms

bottom_bg.png

bottom_bg.png

11 ms

left_bg.png

left_bg.png

12 ms

right_bg.png

right_bg.png

10 ms

left_top.png

left_top.png

12 ms

right_top.png

right_top.png

13 ms

left_bottom.png

left_bottom.png

13 ms

right_bottom.png

right_bottom.png

14 ms

shadow.png

shadow.png

12 ms

3237806657203268723.jpg

3237806657203268723.jpg

2945 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

916 ms

r

r

1251 ms

close2.png

close2.png

4 ms

ad

ad

1190 ms

jquery-1.4.2.js

jquery-1.4.2.js

428 ms

0316ykt-300-250.jpg

0316ykt-300-250.jpg

7046 ms

Accessibility Review

yhasdfgh2348.blog.163.com accessibility score

38

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

yhasdfgh2348.blog.163.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

yhasdfgh2348.blog.163.com SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yhasdfgh2348.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 Yhasdfgh2348.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.

Social Sharing Optimization

yhasdfgh2348.blog.163.com

Open Graph description is not detected on the main page of Yhasdfgh 2348 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: