Tools & Wizards About Us
city.ibeike.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

city.ibeike.com

温馨提示

Page Load Speed

5.3 sec in total

First Response

602 ms

Resources Loaded

4.4 sec

Page Rendered

264 ms

city.ibeike.com screenshot

About Website

Click here to check amazing City Ibeike content for China. Otherwise, check out these important facts you probably never knew about city.ibeike.com

腾讯云域名注册, 腾讯云旗下品牌。腾讯云域名注册是中国领先的域名注册服务提供商, 并提供云主机、网站建设等网络服务。

Visit city.ibeike.com

Key Findings

We analyzed City.ibeike.com page load time and found that the first response time was 602 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

city.ibeike.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

forum.php

602 ms

style_2_common.css

852 ms

style_2_forum_index.css

555 ms

common.js

825 ms

forum.js

543 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 88% of them (66 requests) were addressed to the original City.ibeike.com, 5% (4 requests) were made to Uc.ibeike.com and 3% (2 requests) were made to Ibeike.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Uc.ibeike.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 236.4 kB (49%)

Content Size

479.5 kB

After Optimization

243.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of City.ibeike.com main page is 479.5 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. 35% of websites need less resources to load. Images take 228.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 53.6 kB

  • Original 68.1 kB
  • After minification 68.1 kB
  • After compression 14.5 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 53.6 kB or 79% of the original size.

Image Optimization

-23%

Potential reduce by 52.2 kB

  • Original 228.2 kB
  • After minification 176.0 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. Obviously, City Ibeike needs image optimization as it can save up to 52.2 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 68.1 kB

  • Original 102.8 kB
  • After minification 101.8 kB
  • After compression 34.7 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 68.1 kB or 66% of the original size.

CSS Optimization

-78%

Potential reduce by 62.6 kB

  • Original 80.4 kB
  • After minification 78.7 kB
  • After compression 17.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. City.ibeike.com needs all CSS files to be minified and compressed as it can save up to 62.6 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (18%)

Requests Now

74

After Optimization

61

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forum.php

forum.php

602 ms

style_2_common.css

style_2_common.css

852 ms

style_2_forum_index.css

style_2_forum_index.css

555 ms

common.js

common.js

825 ms

forum.js

forum.js

543 ms

topnav.js

topnav.js

765 ms

logging.js

logging.js

554 ms

md5.js

md5.js

541 ms

title.js

title.js

1077 ms

ping.js

ping.js

140 ms

discuz_tips.js

discuz_tips.js

140 ms

wechat_ibeike.jpg

wechat_ibeike.jpg

748 ms

noavatar_small.gif

noavatar_small.gif

908 ms

body_bg.png

body_bg.png

15 ms

logo.png

logo.png

12 ms

wechat_login.png

wechat_login.png

15 ms

list.gif

list.gif

11 ms

collapsed_no.gif

collapsed_no.gif

15 ms

common_272_icon.png

common_272_icon.png

27 ms

common_273_icon.png

common_273_icon.png

28 ms

common_293_icon.png

common_293_icon.png

25 ms

common_244_icon.png

common_244_icon.png

28 ms

common_76_icon.png

common_76_icon.png

30 ms

common_266_icon.png

common_266_icon.png

30 ms

common_274_icon.png

common_274_icon.png

32 ms

common_270_icon.png

common_270_icon.png

31 ms

common_271_icon.png

common_271_icon.png

32 ms

common_267_icon.png

common_267_icon.png

45 ms

common_358_icon.png

common_358_icon.png

33 ms

common_32_icon.png

common_32_icon.png

45 ms

common_209_icon.png

common_209_icon.png

31 ms

common_198_icon.png

common_198_icon.png

45 ms

common_286_icon.png

common_286_icon.png

47 ms

common_158_icon.png

common_158_icon.png

47 ms

common_180_icon.png

common_180_icon.png

48 ms

common_288_icon.png

common_288_icon.png

47 ms

common_290_icon.png

common_290_icon.png

52 ms

common_285_icon.png

common_285_icon.png

48 ms

common_55_icon.png

common_55_icon.png

49 ms

common_257_icon.png

common_257_icon.png

50 ms

common_256_icon.png

common_256_icon.png

50 ms

common_282_icon.png

common_282_icon.png

51 ms

common_281_icon.png

common_281_icon.png

52 ms

common_258_icon.png

common_258_icon.png

66 ms

common_312_icon.png

common_312_icon.png

67 ms

common_298_icon.png

common_298_icon.png

52 ms

09_avatar_small.jpg

09_avatar_small.jpg

1429 ms

51_avatar_small.jpg

51_avatar_small.jpg

1428 ms

03_avatar_small.jpg

03_avatar_small.jpg

1426 ms

common_297_icon.png

common_297_icon.png

61 ms

common_296_icon.png

common_296_icon.png

58 ms

common_300_icon.png

common_300_icon.png

59 ms

common_295_icon.png

common_295_icon.png

60 ms

common_299_icon.png

common_299_icon.png

62 ms

forum.gif

forum.gif

52 ms

security.png

security.png

49 ms

header_top_bg.png

header_top_bg.png

49 ms

header_bg.png

header_bg.png

48 ms

top_corn.png

top_corn.png

51 ms

px.png

px.png

47 ms

pn.png

pn.png

49 ms

nav_bg.png

nav_bg.png

35 ms

qmenu.png

qmenu.png

36 ms

menu_btb.png

menu_btb.png

41 ms

menu_btbr.png

menu_btbr.png

41 ms

menu_bt.png

menu_bt.png

43 ms

menu_btr.png

menu_btr.png

39 ms

search.png

search.png

39 ms

main_bg.png

main_bg.png

22 ms

pt_item.png

pt_item.png

21 ms

listbg.gif

listbg.gif

28 ms

h3_bg.png

h3_bg.png

550 ms

Mjc4NjYzOTE=.js

Mjc4NjYzOTE=.js

355 ms

scrolltop.png

scrolltop.png

9 ms

switch_width.png

switch_width.png

29 ms

Accessibility Review

city.ibeike.com accessibility score

76

Accessibility Issues

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

Document doesn't have a <title> element

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

Best Practices

city.ibeike.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

city.ibeike.com SEO score

50

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 City.ibeike.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 City.ibeike.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

city.ibeike.com

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