Tools & Wizards About Us
g4a.health screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

g4a.health

Healthcare innovation funding for e-health startups | Bayer G4A

Page Load Speed

3.5 sec in total

First Response

190 ms

Resources Loaded

2.4 sec

Page Rendered

888 ms

g4a.health screenshot

About Website

Click here to check amazing G4A content for Turkey. Otherwise, check out these important facts you probably never knew about g4a.health

Bayer Healthcare innovation funding - G4A drives innovative digital health solutions. Profit of Bayer funding & support: Consulting ✓ Expertness ✓ Events ✓

Visit g4a.health

Key Findings

We analyzed G4a.health page load time and found that the first response time was 190 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

g4a.health performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

g4a.health

190 ms

www.g4a.health

105 ms

otSDKStub.js

84 ms

OtAutoBlock.js

106 ms

style.css

68 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 89% of them (32 requests) were addressed to the original G4a.health, 8% (3 requests) were made to Cdn.cookielaw.org and 3% (1 request) were made to Assets.baywsf.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain G4a.health.

Page Optimization Overview & Recommendations

Page size can be reduced by 602.0 kB (11%)

Content Size

5.4 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of G4a.health main page is 5.4 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. 40% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 468.0 kB

  • Original 521.1 kB
  • After minification 514.2 kB
  • After compression 53.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 468.0 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 4.1 kB

  • Original 4.6 MB
  • After minification 4.6 MB

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. G4A images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 129.8 kB

  • Original 300.8 kB
  • After minification 300.6 kB
  • After compression 171.0 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 129.8 kB or 43% of the original size.

CSS Optimization

-11%

Potential reduce by 126 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 1.0 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. G4a.health needs all CSS files to be minified and compressed as it can save up to 126 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (68%)

Requests Now

31

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

g4a.health

g4a.health

190 ms

www.g4a.health

www.g4a.health

105 ms

otSDKStub.js

otSDKStub.js

84 ms

OtAutoBlock.js

OtAutoBlock.js

106 ms

style.css

style.css

68 ms

js_MktJVJf3wRnutcAEOcmMdcjGg-CNjzaL5CMCD4roEow.js

js_MktJVJf3wRnutcAEOcmMdcjGg-CNjzaL5CMCD4roEow.js

316 ms

js_HmM3asRMbcLiHiEu5Jzly7U1zJgS4JaYda2kK-gFcBQ.js

js_HmM3asRMbcLiHiEu5Jzly7U1zJgS4JaYda2kK-gFcBQ.js

178 ms

js_jBwu0aXeG9w6HYfRtLYIWsVJECRsdZn5k9UIPNDfIxY.js

js_jBwu0aXeG9w6HYfRtLYIWsVJECRsdZn5k9UIPNDfIxY.js

241 ms

js_a04qd3krYVMHElgc4MpXhN31z9eggvKY61C1U8wCLsQ.js

js_a04qd3krYVMHElgc4MpXhN31z9eggvKY61C1U8wCLsQ.js

240 ms

js_wBw40AKOMfOKWM6LIRevcbnyazKtuu5yAX0D4qzqIvE.js

js_wBw40AKOMfOKWM6LIRevcbnyazKtuu5yAX0D4qzqIvE.js

242 ms

js_RfEC_GanCWWmmPX3iatTmny0Y6uODz2qQae_s5QC7NA.js

js_RfEC_GanCWWmmPX3iatTmny0Y6uODz2qQae_s5QC7NA.js

613 ms

js_BhW6T69wudqVKXKgpxXjVTMyYXRP2378zBvspbh86L8.js

js_BhW6T69wudqVKXKgpxXjVTMyYXRP2378zBvspbh86L8.js

413 ms

gtm.min.js

gtm.min.js

414 ms

gtag.min.js

gtag.min.js

422 ms

js_i0N5FoN4683r7v7PF8uBzaKxBTvl1EqXMUtGba6IrFw.js

js_i0N5FoN4683r7v7PF8uBzaKxBTvl1EqXMUtGba6IrFw.js

545 ms

js_hkKN6NtYsp3hACflZKtCnrTtchO2zWE4nlM6qXr6GIY.js

js_hkKN6NtYsp3hACflZKtCnrTtchO2zWE4nlM6qXr6GIY.js

576 ms

js_pKULGrxIs_MvH_YrGiROlrHCQXTjB-zNaSL3xmaLfSo.js

js_pKULGrxIs_MvH_YrGiROlrHCQXTjB-zNaSL3xmaLfSo.js

500 ms

js_xGejbjA-iF9kMQ7358qHImTfmVzII49jBSfsO4yXH3E.js

js_xGejbjA-iF9kMQ7358qHImTfmVzII49jBSfsO4yXH3E.js

781 ms

brand-colorlogo-b4a-.png

brand-colorlogo-b4a-.png

586 ms

menu-arr-red.png

menu-arr-red.png

716 ms

apply-red.png

apply-red.png

1033 ms

homepage_banner_ani.png

homepage_banner_ani.png

744 ms

hm-bg-lg-no-cle.png

hm-bg-lg-no-cle.png

1471 ms

cle-right-pt.png

cle-right-pt.png

834 ms

white_patch.png

white_patch.png

895 ms

arr-48.png

arr-48.png

1281 ms

Latest_Expert_opinions_bg-N.png

Latest_Expert_opinions_bg-N.png

1232 ms

TURBINE.png

TURBINE.png

1218 ms

Rachel_Trobman_Upside_Health_V2.png

Rachel_Trobman_Upside_Health_V2.png

1077 ms

SKY%20LABS.png

SKY%20LABS.png

1282 ms

Arfa%20Headshot.png

Arfa%20Headshot.png

1387 ms

Turbine%20CEO%20png.png

Turbine%20CEO%20png.png

1498 ms

GothicA1-Regular.ttf

GothicA1-Regular.ttf

1422 ms

46478528-74d5-4d34-9648-7d2484b7f782.json

46478528-74d5-4d34-9648-7d2484b7f782.json

27 ms

GothicA1-Bold.ttf

GothicA1-Bold.ttf

1167 ms

icomoon_0.woff

icomoon_0.woff

1853 ms

Accessibility Review

g4a.health accessibility score

82

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.

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

g4a.health 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

g4a.health SEO score

84

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

g4a.health

Open Graph data is detected on the main page of G4A. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: