4.9 sec in total
757 ms
3.8 sec
427 ms
Click here to check amazing Cpr content for Canada. Otherwise, check out these important facts you probably never knew about cpr.ca
CPKC is the first and only single-line rail network connecting a continent - Canada, the United States and Mexico.
Visit cpr.caWe analyzed Cpr.ca page load time and found that the first response time was 757 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cpr.ca performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value26.0 s
0/100
25%
Value10.8 s
6/100
10%
Value1,000 ms
27/100
30%
Value0.003
100/100
15%
Value18.1 s
3/100
10%
757 ms
52 ms
134 ms
241 ms
355 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 91% of them (51 requests) were addressed to the original Cpr.ca, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (915 ms) belongs to the original domain Cpr.ca.
Page size can be reduced by 1.1 MB (59%)
1.8 MB
738.9 kB
In fact, the total size of Cpr.ca main page is 1.8 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. 50% of websites need less resources to load. Javascripts take 796.3 kB which makes up the majority of the site volume.
Potential reduce by 67.3 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 67.3 kB or 74% of the original size.
Potential reduce by 4.0 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. Cpr images are well optimized though.
Potential reduce by 547.6 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 547.6 kB or 69% of the original size.
Potential reduce by 437.0 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. Cpr.ca needs all CSS files to be minified and compressed as it can save up to 437.0 kB or 85% of the original size.
Number of requests can be reduced by 38 (75%)
51
13
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cpr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
en
757 ms
jquery.min.js
52 ms
ScriptResx.ashx
134 ms
jquery_mobile.min.js
241 ms
modernizr.min.js
355 ms
corev15.css
634 ms
searchv15.css
265 ms
init.js
682 ms
handlebars.js
477 ms
moment.min.js
374 ms
page_util.js
397 ms
core.js
477 ms
scooch.js
508 ms
hcf.carousel.js
528 ms
jquery_cookie.min.js
597 ms
jquery_placeholder.js
598 ms
ScriptResource.axd
638 ms
blank.js
659 ms
ScriptResource.axd
718 ms
sp.init.js
719 ms
clientrenderer.js
762 ms
ScriptResx.ashx
772 ms
search.clientcontrols.js
915 ms
search.cbs.js
819 ms
item_factcarousel.js
840 ms
group_content.js
842 ms
control_carousel.js
893 ms
Hcf.DomTools.js
837 ms
fonts.css
852 ms
wcm.css
848 ms
style.css
849 ms
WebResource.axd
913 ms
base.js
797 ms
zone_configuration.js
808 ms
Hcf.Analytics.js
843 ms
Hcf.Profiler.js
180 ms
Hcf.ResponsiveImages.js
135 ms
Hcf.MobileNavigation.js
133 ms
harvey.js
134 ms
analytics.js
32 ms
logo-print.png
129 ms
collect
14 ms
collect
57 ms
cp-sprite.png
186 ms
canada-club-2.jpg
759 ms
3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff
275 ms
9aa32a81-1124-4c43-b3db-15bfb1f7aed2.woff
254 ms
f1f95a55-f0c6-4fb5-8939-b93160b7a751.woff
235 ms
CnktrROKwiyfzKhdzGQutYulVDeqF9WL7Q8IlGIdAAC4Af+FsAGNAEuwCFBYsQEBjlmxRgYrWCGwEFlLsBRSWCGwgFkdsAYrXFhZsBQrAAAAAVOJGzwAAA==
124 ms
control_searchbox_compact.js
136 ms
intermodal-delta.jpg
238 ms
owen-cardio-awards-2.jpg
311 ms
x-trail.png
223 ms
speedometer.png
254 ms
pie-chart.png
259 ms
searchresultui.png
304 ms
cpr.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cpr.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cpr.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cpr.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Cpr.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.
cpr.ca
Open Graph description is not detected on the main page of Cpr. 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: