Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

geha.com

Home | GEHA

Page Load Speed

2.7 sec in total

First Response

103 ms

Resources Loaded

2.4 sec

Page Rendered

238 ms

geha.com screenshot

About Website

Welcome to geha.com homepage info - get ready to check GEHA best content for United States right away, or after learning these important things about geha.com

GEHA is the second-largest national health plan and the second-largest national dental plan serving federal employees, federal retirees, and their families. GEHA provides health and dental plans to mo...

Visit geha.com

Key Findings

We analyzed Geha.com page load time and found that the first response time was 103 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

geha.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value1,700 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

geha.com

103 ms

geha.com

346 ms

site.css

104 ms

modernizr.js

139 ms

conversion.js

28 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 42% of them (44 requests) were addressed to the original Geha.com, 18% (19 requests) were made to Um.simpli.fi and 3% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (868 ms) belongs to the original domain Geha.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 656.0 kB (42%)

Content Size

1.6 MB

After Optimization

912.1 kB

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

HTML Optimization

-75%

Potential reduce by 100.9 kB

  • Original 134.7 kB
  • After minification 115.2 kB
  • After compression 33.8 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. This page needs HTML code to be minified as it can gain 19.5 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 100.9 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 39.4 kB

  • Original 523.9 kB
  • After minification 484.5 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. GEHA images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 515.7 kB

  • Original 830.7 kB
  • After minification 818.3 kB
  • After compression 315.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 515.7 kB or 62% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 78.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.

Requests Breakdown

Number of requests can be reduced by 40 (53%)

Requests Now

76

After Optimization

36

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

Accessibility Review

geha.com accessibility score

86

Accessibility Issues

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.

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 IDs are not unique

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

Best Practices

geha.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

geha.com SEO score

78

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 Geha.com 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 Geha.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

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