Tools & Wizards About Us
s.weibo.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 0

    Best Practices

  • 83

    SEO

    Google-friendlier than
    46% of websites

s.weibo.com

Sina Visitor System

Page Load Speed

29.9 sec in total

First Response

13.8 sec

Resources Loaded

15.9 sec

Page Rendered

140 ms

s.weibo.com screenshot

About Website

Click here to check amazing S Weibo content for China. Otherwise, check out these important facts you probably never knew about s.weibo.com

Visit s.weibo.com

Key Findings

We analyzed S.weibo.com page load time and found that the first response time was 13.8 sec and then it took 16.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

s.weibo.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

s.weibo.com

13806 ms

common.css

22 ms

index4.css

12 ms

search_directarea.css

13 ms

general.css

9 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original S.weibo.com, 59% (24 requests) were made to Img.t.sinajs.cn and 24% (10 requests) were made to Js.t.sinajs.cn. The less responsive or slowest element that took the longest time to load (13.8 sec) belongs to the original domain S.weibo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (69%)

Content Size

2.7 MB

After Optimization

827.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of S.weibo.com main page is 2.7 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. 70% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 12.6 kB

  • Original 16.4 kB
  • After minification 13.7 kB
  • After compression 3.8 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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 12.6 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 5.9 kB

  • Original 221.4 kB
  • After minification 215.5 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. S Weibo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 1.0 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 457.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 1.0 MB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 810.4 kB

  • Original 960.8 kB
  • After minification 902.5 kB
  • After compression 150.4 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. S.weibo.com needs all CSS files to be minified and compressed as it can save up to 810.4 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

s.weibo.com

s.weibo.com

13806 ms

common.css

common.css

22 ms

index4.css

index4.css

12 ms

search_directarea.css

search_directarea.css

13 ms

general.css

general.css

9 ms

hot_ranktit.css

hot_ranktit.css

15 ms

usually.css

usually.css

13 ms

feed.css

feed.css

14 ms

rela_person.css

rela_person.css

13 ms

direct_weiguantuan.css

direct_weiguantuan.css

15 ms

bootstrap.js

bootstrap.js

38 ms

musicplayer_stk_v6.0.14.js

musicplayer_stk_v6.0.14.js

39 ms

player.js

player.js

596 ms

body_repeat_v6.png

body_repeat_v6.png

18 ms

body_bg_v6.jpg

body_bg_v6.jpg

19 ms

getmd5url.html

getmd5url.html

318 ms

PCD_mplayer.css

PCD_mplayer.css

5 ms

player_bg.png

player_bg.png

4 ms

ico_btn_player.png

ico_btn_player.png

4 ms

md5_mapping_file.json

md5_mapping_file.json

3 ms

module_0141cf458b3d9cpb.js

module_0141cf458b3d9cpb.js

7 ms

topnavthird

topnavthird

3088 ms

index_logo.png

index_logo.png

14 ms

ico_expand.png

ico_expand.png

13 ms

W_outFrame.css

W_outFrame.css

13 ms

feedSDK.css

feedSDK.css

22 ms

connect_layer.css

connect_layer.css

4 ms

topInit.js

topInit.js

6 ms

searchIndex.js

searchIndex.js

21 ms

topnavthird

topnavthird

664 ms

suda.js

suda.js

4 ms

a.gif

a.gif

2023 ms

WB_outframe.css

WB_outframe.css

5 ms

top.js

top.js

7 ms

logo_us.png

logo_us.png

6 ms

WB_logo.png

WB_logo.png

9 ms

icon_out.png

icon_out.png

10 ms

wbficon.svg

wbficon.svg

5 ms

userCard.js

userCard.js

5 ms

smartSortCard.js

smartSortCard.js

16 ms

followingListCard.js

followingListCard.js

16 ms

Accessibility Review

s.weibo.com accessibility score

51

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

Form elements do not have associated labels

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.

SEO Factors

s.weibo.com SEO score

83

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise S.weibo.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that S.weibo.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

s.weibo.com

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