3.4 sec in total
690 ms
2.6 sec
109 ms
Click here to check amazing High Park content for Canada. Otherwise, check out these important facts you probably never knew about highpark.org
Attractions, maps, events, and more! HighPark.org is managed by the Grenadier Group working in partnership with the High Park Resource Group.
Visit highpark.orgWe analyzed Highpark.org page load time and found that the first response time was 690 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
highpark.org performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value5.4 s
19/100
25%
Value5.2 s
59/100
10%
Value40 ms
100/100
30%
Value0.106
88/100
15%
Value4.5 s
82/100
10%
690 ms
1388 ms
75 ms
118 ms
298 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 69% of them (22 requests) were addressed to the original Highpark.org, 9% (3 requests) were made to Fonts.gstatic.com and 6% (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 Highpark.org.
Page size can be reduced by 355.0 kB (42%)
838.7 kB
483.7 kB
In fact, the total size of Highpark.org main page is 838.7 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. 25% of websites need less resources to load. HTML takes 409.5 kB which makes up the majority of the site volume.
Potential reduce by 269.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. 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 269.7 kB or 66% of the original size.
Potential reduce by 21.7 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. High Park images are well optimized though.
Potential reduce by 61.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 61.5 kB or 39% of the original size.
Potential reduce by 2.2 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. Highpark.org needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 33% of the original size.
Number of requests can be reduced by 12 (46%)
26
14
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of High Park. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
highpark.org
690 ms
www.highpark.org
1388 ms
guestlist-embed.js
75 ms
style.css
118 ms
wprmenu.css
298 ms
css
23 ms
styles.css
67 ms
jquery.js
316 ms
jquery-migrate.min.js
303 ms
jquery.transit.min.js
98 ms
jquery.sidr.js
125 ms
wprmenu.js
434 ms
guestlist-embed.js
73 ms
jquery.min.js
8 ms
main.js
27 ms
cont-shadow2.png
37 ms
HighPark.org-Banner1-e1375888836455.png
454 ms
facebook-icon.png
80 ms
search-icon.png
59 ms
photo-0171e-321x209.jpg
186 ms
7208-e-321x209.jpg
193 ms
march-break-321x209.jpg
91 ms
0228e-321x209.jpg
281 ms
IMG_0425e-321x209.jpg
234 ms
JANUARY-e-321x209.jpg
161 ms
torontocutsmall.png
185 ms
ga.js
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
16 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
15 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
16 ms
__utm.gif
12 ms
update.js
32 ms
highpark.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
highpark.org 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
highpark.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Highpark.org 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 Highpark.org 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.
highpark.org
Open Graph description is not detected on the main page of High Park. 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: