Tools & Wizards About Us
ikang.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

ikang.com

爱康国宾官网-爱康国宾健康商城-爱康国宾体检预约-爱康国宾体检报告查询

Page Load Speed

8.5 sec in total

First Response

607 ms

Resources Loaded

7.8 sec

Page Rendered

72 ms

ikang.com screenshot

About Website

Click here to check amazing Ikang content for China. Otherwise, check out these important facts you probably never knew about ikang.com

爱康国宾官网为爱康用户提供体检套餐购买、体检预约、体检报告查询、齿科、口腔等服务； 爱康集团是中国收入规模领先的中高端连锁体检与健康管理集团，通过旗下多个品牌，为团体客户和家庭、个人提供高品质的健康体检、 疾病检测、齿科服务、私人医生、职场医疗、疫苗接种、抗衰老等健康管理与医疗服务

Visit ikang.com

Key Findings

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

Performance Metrics

ikang.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value39.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value87.7 s

0/100

25%

SI (Speed Index)

Value61.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,680 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.154

74/100

15%

TTI (Time to Interactive)

Value100.0 s

0/100

10%

Network Requests Diagram

ikang.com

607 ms

mall.ikang.com

906 ms

mall.ikang.com

1138 ms

hm.js

1115 ms

hm.js

1679 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Ikang.com, 50% (12 requests) were made to Static-newmall.health.ikang.com and 17% (4 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Static-newmall.health.ikang.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.3 kB (33%)

Content Size

109.2 kB

After Optimization

73.0 kB

  • HTML
  • CSS

In fact, the total size of Ikang.com main page is 109.2 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. 20% of websites need less resources to load. CSS take 70.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 31.5 kB

  • Original 38.6 kB
  • After minification 38.6 kB
  • After compression 7.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 31.5 kB or 82% of the original size.

CSS Optimization

-7%

Potential reduce by 4.8 kB

  • Original 70.6 kB
  • After minification 70.6 kB
  • After compression 65.9 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. Ikang.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

20

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ikang.com

ikang.com

607 ms

mall.ikang.com

mall.ikang.com

906 ms

mall.ikang.com

mall.ikang.com

1138 ms

hm.js

hm.js

1115 ms

hm.js

hm.js

1679 ms

chunk-vendors.36db7d41.css

chunk-vendors.36db7d41.css

1208 ms

app.d1d02d7a.css

app.d1d02d7a.css

1412 ms

chunk-vendors.d47584da.js

chunk-vendors.d47584da.js

2001 ms

app.7d92bfe2d29609c7f5f1.js

app.7d92bfe2d29609c7f5f1.js

1539 ms

hm.gif

hm.gif

923 ms

7f63b669096b4d065c77ce419bf4906c.js

7f63b669096b4d065c77ce419bf4906c.js

1544 ms

hm.gif

hm.gif

410 ms

chunk-02db8b2a.f829e006.css

chunk-02db8b2a.f829e006.css

234 ms

chunk-03cdd56a.98812938.css

chunk-03cdd56a.98812938.css

262 ms

chunk-03f8e9bd.33f083eb.css

chunk-03f8e9bd.33f083eb.css

268 ms

chunk-067a2454.b269e538.css

chunk-067a2454.b269e538.css

229 ms

delegate.html

delegate.html

250 ms

getUnread.action

getUnread.action

503 ms

1.png

1.png

1103 ms

chunk-084b68e3.10c7f7a0.css

chunk-084b68e3.10c7f7a0.css

259 ms

remoteStorage.action

remoteStorage.action

526 ms

chunk-0b443a9c.e29d42eb.css

chunk-0b443a9c.e29d42eb.css

232 ms

chunk-0d0eaf2a.26cb93bf.css

chunk-0d0eaf2a.26cb93bf.css

229 ms

chunk-0d9cfb2b.376e55b6.css

chunk-0d9cfb2b.376e55b6.css

231 ms

Accessibility Review

ikang.com accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

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

ikang.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ikang.com SEO score

77

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

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ikang.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Ikang.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

ikang.com

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