884 ms in total
48 ms
487 ms
349 ms
Welcome to hpl.ca homepage info - get ready to check HPL best content for Canada right away, or after learning these important things about hpl.ca
Visit hpl.caWe analyzed Hpl.ca page load time and found that the first response time was 48 ms and then it took 836 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
hpl.ca performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value9.6 s
0/100
25%
Value6.2 s
43/100
10%
Value3,260 ms
2/100
30%
Value0.654
8/100
15%
Value24.8 s
0/100
10%
48 ms
47 ms
12 ms
48 ms
48 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 72% of them (43 requests) were addressed to the original Hpl.ca, 17% (10 requests) were made to Syndetics.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (273 ms) relates to the external source Fullstory.com.
Page size can be reduced by 876.4 kB (33%)
2.7 MB
1.8 MB
In fact, the total size of Hpl.ca main page is 2.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 62.6 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 62.6 kB or 80% of the original size.
Potential reduce by 347.5 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, HPL needs image optimization as it can save up to 347.5 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 270.0 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 270.0 kB or 72% of the original size.
Potential reduce by 196.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. Hpl.ca needs all CSS files to be minified and compressed as it can save up to 196.4 kB or 84% of the original size.
Number of requests can be reduced by 19 (33%)
57
38
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HPL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
hpl.ca
48 ms
www.hpl.ca
47 ms
font-awesome.min.css
12 ms
css
48 ms
css
48 ms
css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css
10 ms
css_wjSX1qQfaRjRrgBu9K1EFiSs7htgN_wB7HkU_txrxIo.css
15 ms
css_bAsNl07UIpBUYWvcGpmhFKs085z1WrZWc9rIFfZAUrs.css
18 ms
css_P-KNlGBFmrprR4li_89vkICXhh6ErR7M31AFah-ABRg.css
25 ms
js_BAhqE0nsQns6shJD8cBPNaX58HANh3tzWfxSlYIKGGs.js
42 ms
lightbox.js
24 ms
js_fbpeSppwfvdT1JsTJbaNJ_dH1boJ3Hb797ldLeXR4Kw.js
39 ms
js_I1fynoOhJouIIZf4AmlHdks6MrREUz2BKWs0hbEZuVo.js
22 ms
js_zMiPZrsdmI1U6uSllscMxR5WjJ1jakSi8FpDO9hZbr8.js
39 ms
js_z0iDd9MJh3lKiONP4pmE4UEdUvEyCHcShUoJBRG2ldw.js
37 ms
respond.min.js
38 ms
analytics.js
214 ms
fs.js
273 ms
marchBreak-16_carousel.jpg
205 ms
index.aspx
182 ms
trewsConcertInRound_carousel.jpg
68 ms
psychologyMonth_carousel.jpg
70 ms
100-books_carousel.png
69 ms
blackHistoryMonth-16_carousel_1.jpg
81 ms
whatsHappening_carousel%20spring%202016.jpg
78 ms
freedomToRead_carousel_0.jpg
93 ms
bg-search.png
67 ms
logo_header.png
74 ms
hamburger-white.png
73 ms
teens_primary_nav_top.png
75 ms
teens_primary_nav_bottom.png
79 ms
x-white.png
79 ms
log-in-button.jpg
80 ms
bookmark-primary.png
80 ms
icon_calendar.png
81 ms
kids-wavy-callout-sm.png
81 ms
teens-ripped-bottom.png
81 ms
icon_programs.png
81 ms
catalogue-arrow-left.png
82 ms
catalogue-arrow-right.png
84 ms
kids-wavy-callout.png
83 ms
icon_book.png
82 ms
icon_quick_links.png
83 ms
kids-wavy-foot.png
84 ms
blackHistory_webImg.jpg
86 ms
psychologyMonth_webImg.jpg
85 ms
left-chevron.png
86 ms
right-chevron.png
86 ms
index.aspx
61 ms
index.aspx
28 ms
index.aspx
32 ms
index.aspx
31 ms
index.aspx
68 ms
index.aspx
30 ms
index.aspx
67 ms
index.aspx
32 ms
index.aspx
66 ms
fontawesome-webfont.woff
26 ms
flexslider-icon.woff
84 ms
collect
43 ms
hpl.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.
hpl.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
hpl.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hpl.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 Hpl.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.
hpl.ca
Open Graph description is not detected on the main page of HPL. 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: