Tools & Wizards About Us
pgnfc.com screenshot

Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

pgnfc.com

PGNFC

Page Load Speed

1.1 sec in total

First Response

190 ms

Resources Loaded

663 ms

Page Rendered

227 ms

pgnfc.com screenshot

About Website

Click here to check amazing PGNFC content. Otherwise, check out these important facts you probably never knew about pgnfc.com

Prince George Native Friendship Center

Visit pgnfc.com

Key Findings

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

Performance Metrics

pgnfc.com performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value3.2 s

91/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

pgnfc.com

190 ms

site_global.css

41 ms

index.css

51 ms

count.js

270 ms

jquery-1.6.4.min.js

61 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 94% of them (44 requests) were addressed to the original Pgnfc.com, 4% (2 requests) were made to Count.carrierzone.com and 2% (1 request) were made to Musecdn.businesscatalyst.com. The less responsive or slowest element that took the longest time to load (412 ms) belongs to the original domain Pgnfc.com.

Page Optimization Overview & Recommendations

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

Content Size

815.6 kB

After Optimization

665.3 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Pgnfc.com main page is 815.6 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. 20% of websites need less resources to load. Images take 733.0 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 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. This web page is already compressed.

Image Optimization

-16%

Potential reduce by 117.2 kB

  • Original 733.0 kB
  • After minification 615.8 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, PGNFC needs image optimization as it can save up to 117.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 32.3 kB

  • Original 77.7 kB
  • After minification 65.5 kB
  • After compression 45.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 32.3 kB or 42% of the original size.

CSS Optimization

-16%

Potential reduce by 767 B

  • Original 4.9 kB
  • After minification 4.9 kB
  • After compression 4.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. Pgnfc.com needs all CSS files to be minified and compressed as it can save up to 767 B or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (73%)

Requests Now

44

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pgnfc.com

pgnfc.com

190 ms

site_global.css

site_global.css

41 ms

index.css

index.css

51 ms

count.js

count.js

270 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

61 ms

sprydomutils.js

sprydomutils.js

80 ms

museutils.js

museutils.js

80 ms

jquery.musemenu.js

jquery.musemenu.js

79 ms

backgrd5.png

backgrd5.png

249 ms

sh_proofofvaccine_notice.png

sh_proofofvaccine_notice.png

31 ms

index_page_sprite.png

index_page_sprite.png

35 ms

banner8.png

banner8.png

281 ms

master_u3948_full.png

master_u3948_full.png

33 ms

master_u3948_r_sprite.png

master_u3948_r_sprite.png

47 ms

master_u3948_m_sprite.png

master_u3948_m_sprite.png

47 ms

master_u3948_a_sprite.png

master_u3948_a_sprite.png

49 ms

master_u3918_full.png

master_u3918_full.png

55 ms

master_u3918_r_sprite.png

master_u3918_r_sprite.png

70 ms

master_u3918_m_sprite.png

master_u3918_m_sprite.png

71 ms

master_u3918_a_sprite.png

master_u3918_a_sprite.png

71 ms

master_u3925_full.png

master_u3925_full.png

75 ms

master_u3925_r_sprite.png

master_u3925_r_sprite.png

89 ms

master_u3925_m_sprite.png

master_u3925_m_sprite.png

90 ms

master_u3925_a_sprite.png

master_u3925_a_sprite.png

92 ms

master_u3953_full.png

master_u3953_full.png

94 ms

master_u3953_r_sprite.png

master_u3953_r_sprite.png

118 ms

master_u3953_m_sprite.png

master_u3953_m_sprite.png

118 ms

master_u3953_a_sprite.png

master_u3953_a_sprite.png

118 ms

master_u3974_full.png

master_u3974_full.png

118 ms

master_u3974_r_sprite.png

master_u3974_r_sprite.png

139 ms

master_u3974_m_sprite.png

master_u3974_m_sprite.png

141 ms

master_u3974_a_sprite.png

master_u3974_a_sprite.png

142 ms

master_u4416_full.png

master_u4416_full.png

142 ms

master_u4416_r_sprite.png

master_u4416_r_sprite.png

162 ms

master_u4416_m_sprite.png

master_u4416_m_sprite.png

166 ms

master_u4416_a_sprite.png

master_u4416_a_sprite.png

164 ms

mask02.jpg

mask02.jpg

166 ms

mask07.jpg

mask07.jpg

198 ms

mask05.jpg

mask05.jpg

199 ms

pgnfc-teepee1.png

pgnfc-teepee1.png

209 ms

AGM%20Poster%20November%206%202024.png

AGM%20Poster%20November%206%202024.png

412 ms

ctin.php

ctin.php

132 ms

index_u2999_fr.png

index_u2999_fr.png

24 ms

index_u3000_fr.png

index_u3000_fr.png

28 ms

index_u3001_fr.png

index_u3001_fr.png

28 ms

index_u3002_fr.png

index_u3002_fr.png

49 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

69 ms

Accessibility Review

pgnfc.com accessibility score

86

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

pgnfc.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

pgnfc.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pgnfc.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 Pgnfc.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

pgnfc.com

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