Tools & Wizards About Us
cpnp.org screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

cpnp.org

American Association of Psychiatric Pharmacists (AAPP) | aapp.org

Page Load Speed

544 ms in total

First Response

14 ms

Resources Loaded

349 ms

Page Rendered

181 ms

cpnp.org screenshot

About Website

Click here to check amazing Cpnp content for United States. Otherwise, check out these important facts you probably never knew about cpnp.org

Visit cpnp.org

Key Findings

We analyzed Cpnp.org page load time and found that the first response time was 14 ms and then it took 530 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

cpnp.org performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.161

72/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

cpnp.org

14 ms

cpnp.org

45 ms

c15.css

81 ms

landing_front03_c15.css

93 ms

cpnp_300x210.jpg

98 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 19% of them (4 requests) were addressed to the original Cpnp.org, 57% (12 requests) were made to S.cpnp.net and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (200 ms) relates to the external source S.cpnp.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.5 kB (26%)

Content Size

947.4 kB

After Optimization

703.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cpnp.org main page is 947.4 kB. 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 602.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 19.3 kB

  • Original 25.6 kB
  • After minification 25.2 kB
  • After compression 6.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. 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 19.3 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 602.4 kB
  • After minification 602.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. Cpnp images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 102.6 kB

  • Original 172.8 kB
  • After minification 172.8 kB
  • After compression 70.2 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 102.6 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 121.6 kB

  • Original 146.5 kB
  • After minification 146.5 kB
  • After compression 24.9 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. Cpnp.org needs all CSS files to be minified and compressed as it can save up to 121.6 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

17

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cpnp.org

cpnp.org

14 ms

cpnp.org

cpnp.org

45 ms

c15.css

c15.css

81 ms

landing_front03_c15.css

landing_front03_c15.css

93 ms

cpnp_300x210.jpg

cpnp_300x210.jpg

98 ms

c15.js

c15.js

114 ms

landing_front03.js

landing_front03.js

113 ms

panel01-617x347.jpg

panel01-617x347.jpg

199 ms

panel01-617x347.jpg

panel01-617x347.jpg

200 ms

617x347.jpg

617x347.jpg

200 ms

300x250.jpg

300x250.jpg

198 ms

300x250.jpg

300x250.jpg

196 ms

300x250.jpg

300x250.jpg

194 ms

logo_100x100.jpg

logo_100x100.jpg

6 ms

education.jpg

education.jpg

8 ms

analytics.js

analytics.js

78 ms

86 ms

tr

tr

73 ms

cpnp-icons.woff

cpnp-icons.woff

24 ms

collect

collect

16 ms

30 ms

Accessibility Review

cpnp.org accessibility score

62

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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

cpnp.org best practices score

83

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

SEO Factors

cpnp.org SEO score

80

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

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

cpnp.org

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