Tools & Wizards About Us
ppnb.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

ppnb.com

Colorado Springs Community Bank - Pikes Peak National Bank

Page Load Speed

3.4 sec in total

First Response

264 ms

Resources Loaded

2.8 sec

Page Rendered

320 ms

ppnb.com screenshot

About Website

Click here to check amazing Ppnb content for United States. Otherwise, check out these important facts you probably never knew about ppnb.com

Pikes Peak National Bank is a Colorado Springs Community Bank Offering Personal and Business Banking and Checking Services. Start Banking With Us Today.

Visit ppnb.com

Key Findings

We analyzed Ppnb.com page load time and found that the first response time was 264 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ppnb.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

ppnb.com

264 ms

style2.css

118 ms

plusone.js

110 ms

layout.css

56 ms

gplus-32.png

24 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 85% of them (17 requests) were addressed to the original Ppnb.com, 10% (2 requests) were made to Apis.google.com and 5% (1 request) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ppnb.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.8 kB (4%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Ppnb.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 10% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 7.6 kB

  • Original 10.3 kB
  • After minification 8.3 kB
  • After compression 2.7 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 2.0 kB, which is 19% 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 7.6 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 39.7 kB

  • Original 1.1 MB
  • After minification 1.1 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. Ppnb images are well optimized though.

CSS Optimization

-73%

Potential reduce by 1.6 kB

  • Original 2.2 kB
  • After minification 1.7 kB
  • After compression 591 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. Ppnb.com needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ppnb.com

ppnb.com

264 ms

style2.css

style2.css

118 ms

plusone.js

plusone.js

110 ms

layout.css

layout.css

56 ms

gplus-32.png

gplus-32.png

24 ms

ppnblogo312.gif

ppnblogo312.gif

83 ms

20110729member_fdic2_82Wx45H.gif

20110729member_fdic2_82Wx45H.gif

78 ms

20110729EqualHousingLender_45Wx44H.gif

20110729EqualHousingLender_45Wx44H.gif

113 ms

buttonC6.gif

buttonC6.gif

106 ms

pikes-peak-co.jpg

pikes-peak-co.jpg

810 ms

RXP.png

RXP.png

2404 ms

Main%20Branch%200811.1.jpg

Main%20Branch%200811.1.jpg

2387 ms

Academy%20Branch%200811.0.jpg

Academy%20Branch%200811.0.jpg

1137 ms

Valley%20Branch%200811.0.jpg

Valley%20Branch%200811.0.jpg

2241 ms

FacebookLogo.jpg

FacebookLogo.jpg

194 ms

TwitterLogo.gif

TwitterLogo.gif

349 ms

linkedin.png

linkedin.png

943 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

buttonC7.gif

buttonC7.gif

55 ms

buttonC8.gif

buttonC8.gif

54 ms

Accessibility Review

ppnb.com accessibility score

84

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

Links do not have a discernible name

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

ppnb.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ppnb.com SEO score

96

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ppnb.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ppnb.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

ppnb.com

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