Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

prevmed.org

PrevMED: The Heart of On-site Preventive Health Care

Page Load Speed

198 ms in total

First Response

36 ms

Resources Loaded

100 ms

Page Rendered

62 ms

prevmed.org screenshot

About Website

Visit prevmed.org now to see the best up-to-date PrevMED content and also check out these interesting facts you probably never knew about prevmed.org

PrevMED, a leader in the field of preventive on-site treatment for long-term care facilities, offers Dental, Audiology, Optometry, and Podiatry services.

Visit prevmed.org

Key Findings

We analyzed Prevmed.org page load time and found that the first response time was 36 ms and then it took 162 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

prevmed.org performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.254

49/100

15%

TTI (Time to Interactive)

Value6.2 s

63/100

10%

Network Requests Diagram

prevmed.org

36 ms

caf.js

41 ms

px.js

3 ms

px.js

19 ms

main.79d04fa7.js

32 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 50% of them (3 requests) were addressed to the original Prevmed.org, 33% (2 requests) were made to Img1.wsimg.com and 17% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (41 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 472.1 kB (67%)

Content Size

706.6 kB

After Optimization

234.5 kB

In fact, the total size of Prevmed.org main page is 706.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 695.3 kB which makes up the majority of the site volume.

HTML Optimization

-49%

Potential reduce by 777 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 805 B

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 777 B or 49% of the original size.

JavaScript Optimization

-67%

Potential reduce by 464.7 kB

  • Original 695.3 kB
  • After minification 695.1 kB
  • After compression 230.6 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 464.7 kB or 67% of the original size.

CSS Optimization

-68%

Potential reduce by 6.6 kB

  • Original 9.7 kB
  • After minification 9.6 kB
  • After compression 3.1 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. Prevmed.org needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (60%)

Requests Now

5

After Optimization

2

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

Accessibility Review

prevmed.org accessibility score

84

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

High

ARIA IDs are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Low

No form fields have multiple labels

Best Practices

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

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

SEO Factors

prevmed.org SEO score

91

Search Engine Optimization Advices

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 Prevmed.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 Prevmed.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 description is not detected on the main page of PrevMED. 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: