Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

pregnancy.org

Optum - Health Services Innovation Company

Page Load Speed

1.5 sec in total

First Response

214 ms

Resources Loaded

1.2 sec

Page Rendered

110 ms

About Website

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

Optum is committed to making health care work better, leading the way to better experiences, better health, and lower costs for you.

Visit pregnancy.org

Key Findings

We analyzed Pregnancy.org page load time and found that the first response time was 214 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

pregnancy.org performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value10,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.476

18/100

15%

TTI (Time to Interactive)

Value39.5 s

0/100

10%

Network Requests Diagram

pregnancy.org

214 ms

www.optum.com

58 ms

108 ms

clientlib-base.lc-70267407c54bfd3d524dbb8e5bf56862-lc.min.css

16 ms

contexthub.kernel.js

27 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pregnancy.org, 78% (29 requests) were made to Optum.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (425 ms) relates to the external source Optum.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 585.2 kB (35%)

Content Size

1.7 MB

After Optimization

1.1 MB

In fact, the total size of Pregnancy.org main page is 1.7 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. 50% of websites need less resources to load. Images take 906.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 60.6 kB

  • Original 72.7 kB
  • After minification 60.3 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 12.4 kB, which is 17% 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 60.6 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 6.6 kB

  • Original 906.0 kB
  • After minification 899.4 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. Pregnancy images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 518.0 kB

  • Original 717.1 kB
  • After minification 717.1 kB
  • After compression 199.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 518.0 kB or 72% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

18

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

Accessibility Review

pregnancy.org accessibility score

100

Accessibility Issues

Best Practices

pregnancy.org best practices score

75

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pregnancy.org SEO score

93

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

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

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 Pregnancy.org 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 Pregnancy.org 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 data is detected on the main page of Pregnancy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: