4.2 sec in total
267 ms
3.7 sec
283 ms
Visit princegeorge.ca now to see the best up-to-date Prince George content for Canada and also check out these interesting facts you probably never knew about princegeorge.ca
Visit princegeorge.caWe analyzed Princegeorge.ca page load time and found that the first response time was 267 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Princegeorge.ca rating and web reputation
princegeorge.ca performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value15.9 s
0/100
25%
Value11.5 s
5/100
10%
Value440 ms
64/100
30%
Value0.383
27/100
15%
Value17.7 s
4/100
10%
267 ms
1407 ms
554 ms
361 ms
362 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 90% of them (77 requests) were addressed to the original Princegeorge.ca, 5% (4 requests) were made to Translate.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Princegeorge.ca.
Page size can be reduced by 1.3 MB (41%)
3.1 MB
1.8 MB
In fact, the total size of Princegeorge.ca main page is 3.1 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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 143.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 143.4 kB or 80% of the original size.
Potential reduce by 121.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. Prince George images are well optimized though.
Potential reduce by 636.5 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 636.5 kB or 66% of the original size.
Potential reduce by 356.4 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. Princegeorge.ca needs all CSS files to be minified and compressed as it can save up to 356.4 kB or 86% of the original size.
Number of requests can be reduced by 46 (56%)
82
36
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prince George. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
princegeorge.ca
267 ms
default.aspx
1407 ms
jquery-1.11.1.min.js
554 ms
cpg.js
361 ms
OneColumn.js
362 ms
new.js
241 ms
corev15.css
527 ms
pagelayouts15.css
324 ms
searchv15.css
395 ms
webparts.css
405 ms
CPG2015.css
521 ms
init.js
904 ms
ScriptResource.axd
632 ms
blank.js
486 ms
ScriptResource.axd
647 ms
sp.init.js
756 ms
clientrenderer.js
616 ms
ScriptResx.ashx
638 ms
search.clientcontrols.js
1053 ms
WebResource.axd
486 ms
element.js
32 ms
notification.js
623 ms
spcommon.png
111 ms
cpg.png
113 ms
city.jpg
1020 ms
larrow.png
110 ms
rarrow.png
110 ms
freedom.jpg
193 ms
agendas.png
167 ms
council.png
168 ms
jobpostings.png
169 ms
Bylaws.png
174 ms
calculator.png
254 ms
pgmap.png
253 ms
register.png
254 ms
garbage.png
257 ms
activeliving.png
308 ms
Pay.png
330 ms
MyCity_28x11.jpg
333 ms
HomeOwnerGrant.png
333 ms
AirQuality.png
337 ms
pothole.png
373 ms
snow-shovel.png
413 ms
Graffiti-18x17.png
415 ms
rightarrow.png
413 ms
snowgone.jpg
418 ms
rightarrow.png
463 ms
notifybanner.png
495 ms
LoginButton.gif
495 ms
CreateButton.gif
496 ms
numberone.jpg
501 ms
PGVolunteerCity_Logo.jpg
557 ms
pg_web_buttons_light.jpg
575 ms
welcomepg.jpg
573 ms
vpg_2014.jpg
577 ms
Tourism_pg_logo.png
584 ms
facebook.png
649 ms
NotifyLogo.png
643 ms
new.aspx
556 ms
youtube.png
557 ms
twitter.png
563 ms
inst.png
635 ms
translateelement.css
57 ms
main.js
69 ms
li.png
580 ms
legacy.jpg
806 ms
SearchBackground.png
585 ms
cpggrad.png
582 ms
undefined
654 ms
analytics.js
20 ms
element_main.js
37 ms
collect
11 ms
control_searchbox_compact.js
591 ms
control_searchbox.js
580 ms
CityofPG_2015%20Corporate%20Plan%20(Web)%20City%20Homepage.jpg
734 ms
TLQuarterThreeConcentricCircles.png
659 ms
translate_24dp.png
29 ms
l
45 ms
googlelogo_color_42x16dp.png
22 ms
centrebrand.png
712 ms
initstrings.js
591 ms
box-10-shade.png
666 ms
boxbackground.gif
670 ms
BlankPage.aspx
396 ms
searchresultui.png
230 ms
strings.js
313 ms
princegeorge.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
princegeorge.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
princegeorge.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Princegeorge.ca 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 Princegeorge.ca 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.
princegeorge.ca
Open Graph description is not detected on the main page of Prince George. 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: