Tools & Wizards About Us
gehealthcare.co.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

gehealthcare.co.jp

GE Healthcare Japan - 公式サイト | GE HealthCare (Japan)

Page Load Speed

2.1 sec in total

First Response

194 ms

Resources Loaded

1.6 sec

Page Rendered

322 ms

gehealthcare.co.jp screenshot

About Website

Welcome to gehealthcare.co.jp homepage info - get ready to check GE Healthcare best content for Japan right away, or after learning these important things about gehealthcare.co.jp

GE Healthcare Japan - 公式サイト

Visit gehealthcare.co.jp

Key Findings

We analyzed Gehealthcare.co.jp page load time and found that the first response time was 194 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

gehealthcare.co.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value23.4 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value8,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value33.9 s

0/100

10%

Network Requests Diagram

www.gehealthcare.co.jp

194 ms

ja-JP.css

242 ms

satelliteLib-3667d5ef0856da7c2ed922d9652da5d847ba357b.js

27 ms

3AE529289F87456A844E4566674C5D77

21 ms

vendors~main.d09096eb.chunk.css

35 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 69% of them (52 requests) were addressed to the original Gehealthcare.co.jp, 7% (5 requests) were made to C.evidon.com and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (432 ms) relates to the external source Tag.nrich.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 MB (65%)

Content Size

4.0 MB

After Optimization

1.4 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Gehealthcare.co.jp main page is 4.0 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. 65% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 220.7 kB

  • Original 281.5 kB
  • After minification 281.2 kB
  • After compression 60.9 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 220.7 kB or 78% of the original size.

JavaScript Optimization

-54%

Potential reduce by 1.4 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 1.2 MB

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 1.4 MB or 54% of the original size.

CSS Optimization

-86%

Potential reduce by 999.9 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 167.7 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. Gehealthcare.co.jp needs all CSS files to be minified and compressed as it can save up to 999.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (94%)

Requests Now

67

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.gehealthcare.co.jp

www.gehealthcare.co.jp

194 ms

ja-JP.css

ja-JP.css

242 ms

satelliteLib-3667d5ef0856da7c2ed922d9652da5d847ba357b.js

satelliteLib-3667d5ef0856da7c2ed922d9652da5d847ba357b.js

27 ms

3AE529289F87456A844E4566674C5D77

3AE529289F87456A844E4566674C5D77

21 ms

vendors~main.d09096eb.chunk.css

vendors~main.d09096eb.chunk.css

35 ms

main.f30d90d8.chunk.css

main.f30d90d8.chunk.css

37 ms

components-EdsStyleRendering.fd3e06e9.chunk.css

components-EdsStyleRendering.fd3e06e9.chunk.css

36 ms

Header.8416e587.chunk.css

Header.8416e587.chunk.css

27 ms

ClinicalImagingGallery~ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~~1acd71b7.df573b01.chunk.css

ClinicalImagingGallery~ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~~1acd71b7.df573b01.chunk.css

32 ms

ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~HighlightFeatureTiles~H~e7b74b40.118ed97b.chunk.css

ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~HighlightFeatureTiles~H~e7b74b40.118ed97b.chunk.css

36 ms

ProductContentModule.bc8feaa9.chunk.css

ProductContentModule.bc8feaa9.chunk.css

42 ms

FeatureHighlight.bb5a224e.chunk.css

FeatureHighlight.bb5a224e.chunk.css

43 ms

RelatedContent.675ac3f1.chunk.css

RelatedContent.675ac3f1.chunk.css

41 ms

ContactWidget.8f278d99.chunk.css

ContactWidget.8f278d99.chunk.css

42 ms

VeevaCompliance.fb5bda41.chunk.css

VeevaCompliance.fb5bda41.chunk.css

45 ms

js

js

56 ms

9B2A756BF6DB4A6EAC413543C0DCD1CC

9B2A756BF6DB4A6EAC413543C0DCD1CC

44 ms

addthis_widget.js

addthis_widget.js

198 ms

945216A6A7D541BDA2104468B8E5BA6C

945216A6A7D541BDA2104468B8E5BA6C

117 ms

runtime~main.02d30825.js

runtime~main.02d30825.js

53 ms

fontVendor.f695da2d.chunk.js

fontVendor.f695da2d.chunk.js

50 ms

iconSvgs.ba453261.chunk.js

iconSvgs.ba453261.chunk.js

51 ms

utilityVendor.448d791c.chunk.js

utilityVendor.448d791c.chunk.js

74 ms

vendors~main.6668ce6a.chunk.js

vendors~main.6668ce6a.chunk.js

76 ms

main.2e7f94bf.chunk.js

main.2e7f94bf.chunk.js

65 ms

components-EdsStyleRendering.5ab2660e.chunk.js

components-EdsStyleRendering.5ab2660e.chunk.js

92 ms

vendors~CybersecurityRegistrationForm~DashboardNavigation~Feature-Education-client-Renderings-Availa~f086c95b.461dedd7.chunk.js

vendors~CybersecurityRegistrationForm~DashboardNavigation~Feature-Education-client-Renderings-Availa~f086c95b.461dedd7.chunk.js

129 ms

vendors~CybersecurityRegistrationForm~DashboardNavigation~Feature-Education-client-Renderings-Availa~9c6742fd.dae39b07.chunk.js

vendors~CybersecurityRegistrationForm~DashboardNavigation~Feature-Education-client-Renderings-Availa~9c6742fd.dae39b07.chunk.js

118 ms

BookmarksLister~ErrorPageV2~Header~PageSearch~ProminentPageSearch.a21f92e9.chunk.js

BookmarksLister~ErrorPageV2~Header~PageSearch~ProminentPageSearch.a21f92e9.chunk.js

107 ms

Header.41004db6.chunk.js

Header.41004db6.chunk.js

99 ms

ClinicalImagingGallery~ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~~1acd71b7.4f9777c4.chunk.js

ClinicalImagingGallery~ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~~1acd71b7.4f9777c4.chunk.js

106 ms

ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~HighlightFeatureTiles~H~e7b74b40.4eb122c6.chunk.js

ComparativeMediaModule~EpisodeLister~FadeInVideo~FullWidthMediaVideoModuleV2~HighlightFeatureTiles~H~e7b74b40.4eb122c6.chunk.js

113 ms

HomepageHeroV2.b613ee0b.chunk.js

HomepageHeroV2.b613ee0b.chunk.js

115 ms

PickUpWhereWeLeftUI.f6ff79b8.chunk.js

PickUpWhereWeLeftUI.f6ff79b8.chunk.js

124 ms

FeaturedContent.25eda078.chunk.js

FeaturedContent.25eda078.chunk.js

128 ms

HighlightsV2Module.02b3394c.chunk.js

HighlightsV2Module.02b3394c.chunk.js

123 ms

ProductContentModule.92c89f70.chunk.js

ProductContentModule.92c89f70.chunk.js

136 ms

ProductFamily.1d7e269c.chunk.js

ProductFamily.1d7e269c.chunk.js

131 ms

vendors~FeatureHighlight~HeroImage~SeriesHero.5b2fd313.chunk.js

vendors~FeatureHighlight~HeroImage~SeriesHero.5b2fd313.chunk.js

144 ms

FeatureHighlight~HeroImage~SeriesHero.1ff961f2.chunk.js

FeatureHighlight~HeroImage~SeriesHero.1ff961f2.chunk.js

134 ms

FeatureHighlight.6997d2f1.chunk.js

FeatureHighlight.6997d2f1.chunk.js

127 ms

RelatedContent.518dafc2.chunk.js

RelatedContent.518dafc2.chunk.js

127 ms

ArticleNewsletter~CampaignHero~CategoryHero~ContactWidget~FeatureCards~GatekeeperMarketoForm~Marketo~bd5e1d36.d939ff0c.chunk.js

ArticleNewsletter~CampaignHero~CategoryHero~ContactWidget~FeatureCards~GatekeeperMarketoForm~Marketo~bd5e1d36.d939ff0c.chunk.js

120 ms

CampaignHero~CategoryHero~ContactUsForm~ContactWidget~FeatureCards~MarketoForm~NewsletterSignUp~PDXM~1e476943.1185f2e6.chunk.js

CampaignHero~CategoryHero~ContactUsForm~ContactWidget~FeatureCards~MarketoForm~NewsletterSignUp~PDXM~1e476943.1185f2e6.chunk.js

124 ms

CampaignHero~CategoryHero~ContactUsForm~ContactWidget~FeatureCards~JiffleNowForm~NewsletterSignUp~PD~78e4688f.7a286769.chunk.js

CampaignHero~CategoryHero~ContactUsForm~ContactWidget~FeatureCards~JiffleNowForm~NewsletterSignUp~PD~78e4688f.7a286769.chunk.js

126 ms

AuthenticationModal~CampaignHero~CategoryHero~ContactUsForm~ContactWidget~FeatureCards~Gatekeeper~Ne~bd2fc3d8.565f0af3.chunk.js

AuthenticationModal~CampaignHero~CategoryHero~ContactUsForm~ContactWidget~FeatureCards~Gatekeeper~Ne~bd2fc3d8.565f0af3.chunk.js

122 ms

ContactWidget.f160f7d2.chunk.js

ContactWidget.f160f7d2.chunk.js

123 ms

VeevaCompliance.67295537.chunk.js

VeevaCompliance.67295537.chunk.js

125 ms

Error-404

Error-404

82 ms

error-404

error-404

292 ms

gtm.js

gtm.js

52 ms

evidon-sitenotice-tag.js

evidon-sitenotice-tag.js

120 ms

country.js

country.js

124 ms

snthemes.js

snthemes.js

125 ms

cdx-variables.css

cdx-variables.css

129 ms

eds-color-pallete.css

eds-color-pallete.css

72 ms

eds-variables.css

eds-variables.css

73 ms

_fonts.css

_fonts.css

70 ms

settingsV2.js

settingsV2.js

4 ms

logo.svg

logo.svg

76 ms

gtm.js

gtm.js

78 ms

gtm.js

gtm.js

78 ms

tracker.js

tracker.js

341 ms

SVeNZClU.min.js

SVeNZClU.min.js

71 ms

munchkin.js

munchkin.js

81 ms

en-183685.js

en-183685.js

52 ms

qualified.js

qualified.js

143 ms

ip.json

ip.json

77 ms

munchkin.js

munchkin.js

15 ms

visitWebPage

visitWebPage

374 ms

demandbase

demandbase

4 ms

log

log

22 ms

validateCookie

validateCookie

5 ms

291feabf-995b-4bcf-b4bf-dc58118b8bcf

291feabf-995b-4bcf-b4bf-dc58118b8bcf

85 ms

432 ms

Accessibility Review

gehealthcare.co.jp accessibility score

90

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

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

Best Practices

gehealthcare.co.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

gehealthcare.co.jp SEO score

99

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

gehealthcare.co.jp

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