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

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 35

    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

l37104105.blog.163.com

分享淘宝推广方案 淘宝商城运营天猫策划 - 谢明柴 - 网易博客

Page Load Speed

27.4 sec in total

First Response

1.9 sec

Resources Loaded

24.5 sec

Page Rendered

930 ms

l37104105.blog.163.com screenshot

About Website

Visit l37104105.blog.163.com now to see the best up-to-date L 37104105 Blog 163 content for China and also check out these interesting facts you probably never knew about l37104105.blog.163.com

我 ，是一切的根源,写给做电商的,世上已无企业家,电商2.0：一场追求速度和匹配的电商淘汰赛,电子商务是一种全新的零售变革，是未来的大趋势,传统电商，向2.0进军！,多品牌：硬信息里的宽门，找不到天堂的路,优化直通车关键词三大策略,一位淘宝运营成长记，是干货，是水货由你来鉴定！,网店客户群研究分析,谢明柴的网易博客,专注于淘宝商城运营策划、淘宝直通车优化、淘宝运营策划、影响力最广的电子商务博客,谢...

Visit l37104105.blog.163.com

Key Findings

We analyzed L37104105.blog.163.com page load time and found that the first response time was 1.9 sec and then it took 25.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

l37104105.blog.163.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.749

6/100

15%

TTI (Time to Interactive)

Value8.8 s

36/100

10%

Network Requests Diagram

l37104105.blog.163.com

1943 ms

c.css

37 ms

b.css

1355 ms

6630133180817252049.jpg

937 ms

xcode.png

50 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 548.9 kB (58%)

Content Size

939.6 kB

After Optimization

390.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of L37104105.blog.163.com main page is 939.6 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. 30% of websites need less resources to load. Javascripts take 417.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 106.0 kB

  • Original 135.1 kB
  • After minification 135.0 kB
  • After compression 29.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 106.0 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 13.2 kB

  • Original 203.0 kB
  • After minification 189.8 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. L 37104105 Blog 163 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 278.6 kB

  • Original 417.1 kB
  • After minification 417.1 kB
  • After compression 138.6 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 278.6 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 151.2 kB

  • Original 184.5 kB
  • After minification 180.4 kB
  • After compression 33.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. L37104105.blog.163.com needs all CSS files to be minified and compressed as it can save up to 151.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (52%)

Requests Now

44

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L 37104105 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

l37104105.blog.163.com

l37104105.blog.163.com

1943 ms

c.css

c.css

37 ms

b.css

b.css

1355 ms

6630133180817252049.jpg

6630133180817252049.jpg

937 ms

xcode.png

xcode.png

50 ms

1.0.0.js

1.0.0.js

103 ms

pc.js

pc.js

85 ms

ph.js

ph.js

75 ms

5770518497545593941.jpg

5770518497545593941.jpg

774 ms

rssi.png

rssi.png

230 ms

5780933071683898331.jpg

5780933071683898331.jpg

19589 ms

5780933071683898330.jpg

5780933071683898330.jpg

19588 ms

5780933071683898375.jpg

5780933071683898375.jpg

2980 ms

5780933071683898329.jpg

5780933071683898329.jpg

3810 ms

5770518497545593887.jpg

5770518497545593887.jpg

2289 ms

5788532896055036664.jpg

5788532896055036664.jpg

2634 ms

5780933071683898345.jpg

5780933071683898345.jpg

3615 ms

icon.png

icon.png

226 ms

lnkbar.png

lnkbar.png

221 ms

image.png

image.png

220 ms

arrow24.png

arrow24.png

222 ms

newtopbaricon8.png

newtopbaricon8.png

222 ms

crossdomain.html

crossdomain.html

927 ms

crossdomain.html

crossdomain.html

2062 ms

request.s

request.s

950 ms

analyse.png

analyse.png

20288 ms

empty.png

empty.png

45 ms

ava.s

ava.s

5604 ms

crossdomain.html

crossdomain.html

4383 ms

ava.s

ava.s

883 ms

analyse.png

analyse.png

20012 ms

analytics.js

analytics.js

121 ms

collect

collect

42 ms

HomeBeanNew.getAccessStatistics.dwr

HomeBeanNew.getAccessStatistics.dwr

2576 ms

UserBeanNew.getVisitor.dwr

UserBeanNew.getVisitor.dwr

20339 ms

FeelingsBeanNew.getRecentFeelingCards.dwr

FeelingsBeanNew.getRecentFeelingCards.dwr

20343 ms

BlogBeanNew.getBlogClasses.dwr

BlogBeanNew.getBlogClasses.dwr

1531 ms

TagBeanNew.getHostHotTags.dwr

TagBeanNew.getHostHotTags.dwr

5623 ms

MusicBeanNew.setCopyrightMusicSessionToken.dwr

MusicBeanNew.setCopyrightMusicSessionToken.dwr

2005 ms

blogPhotoAd

blogPhotoAd

19807 ms

close_01.png

close_01.png

119 ms

top_bg.png

top_bg.png

405 ms

bottom_bg.png

bottom_bg.png

437 ms

left_bg.png

left_bg.png

475 ms

right_bg.png

right_bg.png

594 ms

left_top.png

left_top.png

594 ms

right_top.png

right_top.png

516 ms

left_bottom.png

left_bottom.png

517 ms

right_bottom.png

right_bottom.png

509 ms

shadow.png

shadow.png

377 ms

SetupBeanNew.getCustomModulesData.dwr

SetupBeanNew.getCustomModulesData.dwr

1782 ms

BgsBean.getBgsUserByUserId.dwr

BgsBean.getBgsUserByUserId.dwr

916 ms

Accessibility Review

l37104105.blog.163.com accessibility score

35

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

l37104105.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

l37104105.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 L37104105.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 L37104105.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

l37104105.blog.163.com

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