6.1 sec in total
217 ms
2 sec
3.9 sec
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.healthWe analyzed G4a.health page load time and found that the first response time was 217 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
g4a.health performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value6.4 s
9/100
25%
Value27.6 s
0/100
10%
Value14,010 ms
0/100
30%
Value0.037
100/100
15%
Value43.6 s
0/100
10%
217 ms
430 ms
381 ms
486 ms
351 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 83% of them (24 requests) were addressed to the original G4a.health, 10% (3 requests) were made to Cdn.cookielaw.org and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain G4a.health.
Page size can be reduced by 672.9 kB (13%)
5.2 MB
4.5 MB
In fact, the total size of G4a.health main page is 5.2 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. 55% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 553.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 553.2 kB or 91% of the original size.
Potential reduce by 6.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. G4A images are well optimized though.
Potential reduce by 113.8 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 113.8 kB or 60% of the original size.
Number of requests can be reduced by 13 (54%)
24
11
The browser has sent 24 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 14 to 1 for JavaScripts and as a result speed up the page load time.
g4a.health
217 ms
www.g4a.health
430 ms
otSDKStub.js
381 ms
OtAutoBlock.js
486 ms
google_tag.script.js
351 ms
css
382 ms
js_vKRPm-wY3td5EeY6Sz57g8BJDdbNG7-XS_cy-HTh2pY.js
242 ms
js_P062V422WZtekyhLcGqB5Y5jqYeI5QHQrm-o7OR50I4.js
200 ms
js_WJh1kBsw4V4YGous9m5w2OmLc2ARMW3jVrq9NFhKJPo.js
198 ms
js_GFYdhVaoGShM9Xu40GubwLsJq_P8i13TyTAOLryJOx0.js
197 ms
js_s-wKgOMyub_6sHEl2p9PaLyClljag9T5qB0faY1jiXU.js
195 ms
js_euOzOxjhc0MozlsWtNE9KTX_iPoYi6HZBLSlzcVEEuI.js
198 ms
js__6X-3EqlyRVCXG31RTMzHBEIuV04_56SLu0DT0kaJh0.js
201 ms
js_VCIdOFSPCMtHOxbhDlc3sbck0iDBGTIo2uTeWmeyMdE.js
231 ms
js_z4y9BhcuklgVtspX8OUgC1VIIPuYsrDoUC3W8J9ut_k.js
260 ms
js_W27OHth3HdpRYsc8-Asjbo1xTRn6o51fK7HbmCFV5xA.js
260 ms
brand-colorlogo-b4a-.png
200 ms
menu-arr-red.png
579 ms
apply-red.png
377 ms
homepage_banner_ani.png
308 ms
cle-right-pt.png
516 ms
white_patch.png
749 ms
arr-48.png
495 ms
portfolio-view-bg.png
415 ms
GothicA1-Regular.ttf
1271 ms
GothicA1-Bold.ttf
1274 ms
icomoon_0.woff
1075 ms
46478528-74d5-4d34-9648-7d2484b7f782.json
156 ms
location
107 ms
g4a.health accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
g4a.health best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
g4a.health SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: