Tools & Wizards About Us
novocare.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

novocare.com

Cost & Coverage for Novo Nordisk Medicines | NovoCare®

Page Load Speed

1.7 sec in total

First Response

96 ms

Resources Loaded

1.4 sec

Page Rendered

212 ms

novocare.com screenshot

About Website

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

At Novo Nordisk, we remain committed to helping patients access and afford their medications. Find savings, coverage, and support for your medications.

Visit novocare.com

Key Findings

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

Performance Metrics

novocare.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

novocare.com

96 ms

www.novocare.com

209 ms

jquery.min.js

100 ms

clientlib-dependencies.min.js

135 ms

clientlib-target.min.js

114 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 93% of them (55 requests) were addressed to the original Novocare.com, 2% (1 request) were made to Assets.adobedtm.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (605 ms) belongs to the original domain Novocare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (32%)

Content Size

4.7 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Novocare.com main page is 4.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. 55% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 199.3 kB

  • Original 219.5 kB
  • After minification 193.6 kB
  • After compression 20.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. This page needs HTML code to be minified as it can gain 25.9 kB, which is 12% 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 199.3 kB or 91% of the original size.

Image Optimization

-39%

Potential reduce by 1.0 MB

  • Original 2.6 MB
  • After minification 1.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. Obviously, Novo Care needs image optimization as it can save up to 1.0 MB or 39% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 249.6 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 1.4 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 249.6 kB or 15% of the original size.

CSS Optimization

-3%

Potential reduce by 7.6 kB

  • Original 237.1 kB
  • After minification 236.5 kB
  • After compression 229.5 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. Novocare.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (75%)

Requests Now

48

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

novocare.com

novocare.com

96 ms

www.novocare.com

www.novocare.com

209 ms

jquery.min.js

jquery.min.js

100 ms

clientlib-dependencies.min.js

clientlib-dependencies.min.js

135 ms

clientlib-target.min.js

clientlib-target.min.js

114 ms

clientlib-site.min.css

clientlib-site.min.css

210 ms

clientlib-webpack.min.css

clientlib-webpack.min.css

114 ms

clientlib-site.min.css

clientlib-site.min.css

260 ms

clientlib-es-site-style.min.css

clientlib-es-site-style.min.css

132 ms

clientlib-custom-grid.min.css

clientlib-custom-grid.min.css

132 ms

clientlibs-mobile.min.css

clientlibs-mobile.min.css

149 ms

clientlib-es-site.min.js

clientlib-es-site.min.js

165 ms

clientlib-site.min.js

clientlib-site.min.js

271 ms

clientlib-webpack.min.js

clientlib-webpack.min.js

332 ms

clientlib-site.min.js

clientlib-site.min.js

301 ms

clientlibs-mobile.min.js

clientlibs-mobile.min.js

465 ms

home.themestyles-h-tags.css

home.themestyles-h-tags.css

257 ms

home.themestyles.css

home.themestyles.css

281 ms

home.themestyles-btn-templates.css

home.themestyles-btn-templates.css

291 ms

home.themestyles-btn.css

home.themestyles-btn.css

302 ms

home.themestyles-btn-bg.css

home.themestyles-btn-bg.css

315 ms

launch-c5ed7c25a38e.min.js

launch-c5ed7c25a38e.min.js

20 ms

clientlibs.min.css

clientlibs.min.css

333 ms

globalnavigation.min.css

globalnavigation.min.css

334 ms

clientlib-vendor.min.js

clientlib-vendor.min.js

347 ms

clientlibs.min.js

clientlibs.min.js

354 ms

site.min.css

site.min.css

362 ms

styles.css

styles.css

366 ms

cvi-fix.css

cvi-fix.css

366 ms

isi-styles.css

isi-styles.css

379 ms

site.min.js

site.min.js

384 ms

clientlibs.min.css

clientlibs.min.css

392 ms

clientlibs.min.js

clientlibs.min.js

397 ms

clientlibs.min.css

clientlibs.min.css

397 ms

clientlibs.min.js

clientlibs.min.js

411 ms

img.min.css

img.min.css

396 ms

img.min.js

img.min.js

401 ms

token.json

token.json

302 ms

home.themestyles-h-tags.css

home.themestyles-h-tags.css

180 ms

home.themestyles.css

home.themestyles.css

170 ms

home.themestyles-btn-templates.css

home.themestyles-btn-templates.css

163 ms

home.themestyles-btn.css

home.themestyles-btn.css

161 ms

home.themestyles-btn-bg.css

home.themestyles-btn-bg.css

155 ms

gtm.js

gtm.js

292 ms

NNI-Bull_2x.png

NNI-Bull_2x.png

281 ms

NovoCare-Logo_2x.png

NovoCare-Logo_2x.png

280 ms

Savings-badge-icon_LG_2x.png

Savings-badge-icon_LG_2x.png

280 ms

NovoCare_DE_Logo.png

NovoCare_DE_Logo.png

280 ms

Help-with-insulin-costs-icon_2x.png

Help-with-insulin-costs-icon_2x.png

280 ms

hcp-resources-image-lg-2x.png

hcp-resources-image-lg-2x.png

605 ms

hcp-resources-image-lg-2x.png

hcp-resources-image-lg-2x.png

602 ms

close-icon.png

close-icon.png

284 ms

novo_nordisk_logo_white.png

novo_nordisk_logo_white.png

283 ms

mmn2sxm.css

mmn2sxm.css

253 ms

ApisWeb-Regular.woff

ApisWeb-Regular.woff

341 ms

ApisWeb-Bold.woff

ApisWeb-Bold.woff

105 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

59 ms

p.css

p.css

27 ms

ApisWeb-Medium.woff

ApisWeb-Medium.woff

66 ms

Accessibility Review

novocare.com accessibility score

82

Accessibility Issues

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

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

novocare.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

novocare.com SEO score

86

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

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 Novocare.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 Novocare.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

novocare.com

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