Tools & Wizards About Us
krames.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

krames.com

Krames: Patient Education, Marketing & Clinical Workflow Solutions

Page Load Speed

1.5 sec in total

First Response

47 ms

Resources Loaded

1.1 sec

Page Rendered

284 ms

krames.com screenshot

About Website

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

Krames activates health with empowering content, engaging education and marketing, & integrated clinical workflow solutions. Discover our solutions today.

Visit krames.com

Key Findings

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

Performance Metrics

krames.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value2,490 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value27.1 s

0/100

10%

Network Requests Diagram

krames.com

47 ms

www.krames.com

68 ms

webmdignite.com

142 ms

css2

41 ms

css_8lV2fS7QK3G4zSicL8c-5phNTGhUK-PPzpHGkdY8XXc.css

20 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Krames.com, 59% (26 requests) were made to Webmdignite.com and 11% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (231 ms) relates to the external source Webmdignite.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.5 kB (18%)

Content Size

1.2 MB

After Optimization

977.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Krames.com main page is 1.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. Only a small number of websites need less resources to load. Javascripts take 909.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 45.1 kB

  • Original 53.5 kB
  • After minification 35.5 kB
  • After compression 8.4 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 18.0 kB, which is 34% 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 45.1 kB or 84% of the original size.

Image Optimization

-17%

Potential reduce by 6.5 kB

  • Original 37.4 kB
  • After minification 30.9 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. Obviously, Krames needs image optimization as it can save up to 6.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 130.1 kB

  • Original 909.4 kB
  • After minification 909.2 kB
  • After compression 779.4 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 130.1 kB or 14% of the original size.

CSS Optimization

-14%

Potential reduce by 26.8 kB

  • Original 185.7 kB
  • After minification 185.7 kB
  • After compression 158.8 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. Krames.com needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (79%)

Requests Now

33

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

krames.com

krames.com

47 ms

www.krames.com

www.krames.com

68 ms

webmdignite.com

webmdignite.com

142 ms

css2

css2

41 ms

css_8lV2fS7QK3G4zSicL8c-5phNTGhUK-PPzpHGkdY8XXc.css

css_8lV2fS7QK3G4zSicL8c-5phNTGhUK-PPzpHGkdY8XXc.css

20 ms

css_kmmjuuJgNEO9x1yvPZIAYvJVZg5PVBiimikdS5nZwFY.css

css_kmmjuuJgNEO9x1yvPZIAYvJVZg5PVBiimikdS5nZwFY.css

22 ms

css2

css2

58 ms

css_r-zo3Ek4NfoMrVE9LtYMx7JjpsPzs-Vmw7N_6LD5yq0.css

css_r-zo3Ek4NfoMrVE9LtYMx7JjpsPzs-Vmw7N_6LD5yq0.css

33 ms

jquery.min.js

jquery.min.js

32 ms

once.min.js

once.min.js

28 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

28 ms

drupal.js

drupal.js

35 ms

drupal.init.js

drupal.init.js

32 ms

gainsight.js

gainsight.js

34 ms

app.js

app.js

36 ms

app.js

app.js

43 ms

site_search.js

site_search.js

41 ms

admin_toolbar.js

admin_toolbar.js

45 ms

brand_palette.js

brand_palette.js

54 ms

admin_autocomplete_search.js

admin_autocomplete_search.js

47 ms

geolocation-api.js

geolocation-api.js

46 ms

geolocation-google-maps-api.js

geolocation-google-maps-api.js

54 ms

js

js

150 ms

image_captions.js

image_captions.js

51 ms

GT-Super-Display-Bold.woff2

GT-Super-Display-Bold.woff2

48 ms

gtm.js

gtm.js

139 ms

lO03EfihEVw

lO03EfihEVw

142 ms

privacyoptions29x14.png

privacyoptions29x14.png

71 ms

WebMD-Ignite-Horizontal-Logo_full-color.png

WebMD-Ignite-Horizontal-Logo_full-color.png

9 ms

www-player.css

www-player.css

33 ms

www-embed-player.js

www-embed-player.js

51 ms

base.js

base.js

106 ms

fa-regular-400.ttf

fa-regular-400.ttf

75 ms

fa-light-300.ttf

fa-light-300.ttf

231 ms

fa-thin-100.ttf

fa-thin-100.ttf

230 ms

fa-solid-900.ttf

fa-solid-900.ttf

59 ms

fa-brands-400.ttf

fa-brands-400.ttf

45 ms

ad_status.js

ad_status.js

175 ms

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

115 ms

embed.js

embed.js

35 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

134 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

134 ms

id

id

28 ms

Create

Create

102 ms

Accessibility Review

krames.com accessibility score

87

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

krames.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

krames.com SEO score

79

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

High

Image elements do not have [alt] attributes

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

krames.com

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