Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

zapprx.com

Specialty Medications: Expedite Fulfillment | Veradigm AccelRx™

Page Load Speed

812 ms in total

First Response

188 ms

Resources Loaded

486 ms

Page Rendered

138 ms

zapprx.com screenshot

About Website

Visit zapprx.com now to see the best up-to-date Zapp Rx content for United States and also check out these interesting facts you probably never knew about zapprx.com

Remove manual hurdles! Get Patients All Their Specialty Medications Faster and More Easily—And Get Your Focus Back Where it Belongs. Get Started Now.

Visit zapprx.com

Key Findings

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

Performance Metrics

zapprx.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

100/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

www.zapprx.com

188 ms

index.css

76 ms

VeradigmTM-logo.png

169 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Zapprx.com and no external sources were called. The less responsive or slowest element that took the longest time to load (188 ms) belongs to the original domain Zapprx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.9 kB (20%)

Content Size

159.9 kB

After Optimization

128.0 kB

In fact, the total size of Zapprx.com main page is 159.9 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. Images take 158.0 kB which makes up the majority of the site volume.

HTML Optimization

-53%

Potential reduce by 703 B

  • Original 1.3 kB
  • After minification 1.2 kB
  • After compression 621 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 703 B or 53% of the original size.

Image Optimization

-20%

Potential reduce by 30.9 kB

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

CSS Optimization

-61%

Potential reduce by 370 B

  • Original 604 B
  • After minification 419 B
  • After compression 234 B

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. Zapprx.com needs all CSS files to be minified and compressed as it can save up to 370 B or 61% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zapp Rx. According to our analytics all requests are already optimized.

Accessibility Review

zapprx.com accessibility score

54

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

zapprx.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

zapprx.com SEO score

54

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

Image elements do not have [alt] attributes

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 Zapprx.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 Zapprx.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 Zapp Rx. 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: