Tools & Wizards About Us
gaoboy.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

gaoboy.com

猿资猿味 - 高波的博客

Page Load Speed

39.5 sec in total

First Response

2 sec

Resources Loaded

37.1 sec

Page Rendered

428 ms

gaoboy.com screenshot

About Website

Visit gaoboy.com now to see the best up-to-date Gaoboy content for China and also check out these interesting facts you probably never knew about gaoboy.com

高波的博客猿资猿味

Visit gaoboy.com

Key Findings

We analyzed Gaoboy.com page load time and found that the first response time was 2 sec and then it took 37.5 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

gaoboy.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

gaoboy.com

1958 ms

theme.min.css

37 ms

bootstrap-responsive.min.css

31 ms

font-awesome.min.css

56 ms

shCore.css

23 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 17% of them (18 requests) were addressed to the original Gaoboy.com, 15% (16 requests) were made to Source.gaoboy.com and 12% (13 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source T11.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 663.7 kB (45%)

Content Size

1.5 MB

After Optimization

802.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 32.6 kB

  • Original 44.8 kB
  • After minification 44.7 kB
  • After compression 12.2 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 32.6 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 3.4 kB

  • Original 443.7 kB
  • After minification 440.3 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. Gaoboy images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 450.7 kB

  • Original 761.6 kB
  • After minification 761.5 kB
  • After compression 310.9 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 450.7 kB or 59% of the original size.

CSS Optimization

-82%

Potential reduce by 176.9 kB

  • Original 216.3 kB
  • After minification 215.9 kB
  • After compression 39.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. Gaoboy.com needs all CSS files to be minified and compressed as it can save up to 176.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (54%)

Requests Now

101

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gaoboy.com

gaoboy.com

1958 ms

theme.min.css

theme.min.css

37 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

31 ms

font-awesome.min.css

font-awesome.min.css

56 ms

shCore.css

shCore.css

23 ms

shThemeFadeToGrey.css

shThemeFadeToGrey.css

27 ms

style.css

style.css

31 ms

one_5707b99df2594.jpg

one_5707b99df2594.jpg

2843 ms

logo.png

logo.png

48 ms

headicon.png

headicon.png

49 ms

ng_570684b80e58b.jpg

ng_570684b80e58b.jpg

1587 ms

one_5706682ecd265.jpg

one_5706682ecd265.jpg

2345 ms

index.php

index.php

913 ms

c.js

c.js

1075 ms

i.js

i.js

741 ms

f.js

f.js

1113 ms

jquery.js

jquery.js

82 ms

wind.js

wind.js

78 ms

bootstrap.min.js

bootstrap.min.js

79 ms

frontend.js

frontend.js

78 ms

shCore.js

shCore.js

78 ms

shAutoloader.js

shAutoloader.js

79 ms

my_wechat_qrcode.jpg

my_wechat_qrcode.jpg

80 ms

ng_57053338ddee0.jpg

ng_57053338ddee0.jpg

2948 ms

one_570516a66d07a.jpg

one_570516a66d07a.jpg

2283 ms

ng_5703e1b861211.jpg

ng_5703e1b861211.jpg

3453 ms

one_5703c51e07003.jpg

one_5703c51e07003.jpg

2036 ms

ng_57029036663c2.jpg

ng_57029036663c2.jpg

2308 ms

one_5702739eee940.jpg

one_5702739eee940.jpg

2507 ms

ng_57013eba4bdf6.jpg

ng_57013eba4bdf6.jpg

3398 ms

one_570122277f4a7.jpg

one_570122277f4a7.jpg

2777 ms

ng_56ffed36de90a.jpg

ng_56ffed36de90a.jpg

2879 ms

one_56ffd0a4551b6.jpg

one_56ffd0a4551b6.jpg

2976 ms

one_56fe7f1e73221.jpg

one_56fe7f1e73221.jpg

3697 ms

ng_56fd4a3ad9e51.jpg

ng_56fd4a3ad9e51.jpg

3438 ms

one_56fd2d9e4f3c5.jpg

one_56fd2d9e4f3c5.jpg

4063 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

932 ms

weiboShow.css

weiboShow.css

28 ms

skin_default.css

skin_default.css

32 ms

gaea_1_19.js

gaea_1_19.js

40 ms

show.js

show.js

19 ms

suda.js

suda.js

16 ms

1

1

741 ms

icon_user.png

icon_user.png

148 ms

btns_bg.png

btns_bg.png

63 ms

icon_follow.png

icon_follow.png

62 ms

icon_tips.png

icon_tips.png

64 ms

bg_trans.png

bg_trans.png

63 ms

a.gif

a.gif

1092 ms

icem

icem

737 ms

share.js

share.js

1115 ms

icem

icem

759 ms

ui

ui

964 ms

icem

icem

1015 ms

tmp.gif

tmp.gif

3893 ms

z_stat.php

z_stat.php

1058 ms

icem

icem

1445 ms

dynamicFloat.js

dynamicFloat.js

503 ms

ui

ui

417 ms

stat.htm

stat.htm

187 ms

core.php

core.php

950 ms

icem

icem

11297 ms

eye.php

eye.php

578 ms

adx.php

adx.php

652 ms

9.gif

9.gif

976 ms

pic.gif

pic.gif

786 ms

analytics.js

analytics.js

17 ms

collect

collect

14 ms

u=1065341403,1694113630&fm=76

u=1065341403,1694113630&fm=76

1334 ms

u=2033516230,2926699423&fm=76

u=2033516230,2926699423&fm=76

1817 ms

bg.png

bg.png

480 ms

reduce_bd-logo1_oper.png

reduce_bd-logo1_oper.png

487 ms

u=1724764875,2457438641&fm=76

u=1724764875,2457438641&fm=76

4624 ms

u=1950084546,3010546825&fm=76

u=1950084546,3010546825&fm=76

3077 ms

app.gif

app.gif

772 ms

noty.js

noty.js

2805 ms

slide_api.js

slide_api.js

374 ms

slide_view.js

slide_view.js

685 ms

select_api.js

select_api.js

824 ms

select_view.js

select_view.js

768 ms

image_api.js

image_api.js

733 ms

image_view.js

image_view.js

735 ms

tangram.js

tangram.js

2448 ms

api_base.js

api_base.js

656 ms

view_base.js

view_base.js

415 ms

slide_share.css

slide_share.css

360 ms

logger.js

logger.js

422 ms

closefeedback.min.js

closefeedback.min.js

510 ms

animate.js

animate.js

1157 ms

reduce_promotion_oper.png

reduce_promotion_oper.png

523 ms

bd_logo.png

bd_logo.png

523 ms

bg_rb.png

bg_rb.png

528 ms

nopic.jpg

nopic.jpg

608 ms

adx.php

adx.php

651 ms

u=3334814142,2362060578&fm=76

u=3334814142,2362060578&fm=76

1484 ms

u=1668904682,2491063491&fm=76

u=1668904682,2491063491&fm=76

4824 ms

u=1195059970,1971390691&fm=76

u=1195059970,1971390691&fm=76

3183 ms

native_ad.png

native_ad.png

483 ms

u=1716177312,2500053663&fm=76

u=1716177312,2500053663&fm=76

3101 ms

u=295542087,2304134935&fm=76

u=295542087,2304134935&fm=76

2807 ms

u=742424360,1072301844&fm=76

u=742424360,1072301844&fm=76

2371 ms

u=923453326,2270382662&fm=76

u=923453326,2270382662&fm=76

19762 ms

o.htm

o.htm

940 ms

wh.js

wh.js

776 ms

ac.js

ac.js

547 ms

Accessibility Review

gaoboy.com accessibility score

68

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.

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

gaoboy.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gaoboy.com SEO score

96

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gaoboy.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gaoboy.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

gaoboy.com

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