3 sec in total
175 ms
2.4 sec
512 ms
Welcome to laurelplace.ca homepage info - get ready to check Laurel Place best content right away, or after learning these important things about laurelplace.ca
Visit laurelplace.caWe analyzed Laurelplace.ca page load time and found that the first response time was 175 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
laurelplace.ca performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value10.9 s
0/100
25%
Value8.5 s
17/100
10%
Value6,070 ms
0/100
30%
Value0.027
100/100
15%
Value27.4 s
0/100
10%
175 ms
257 ms
157 ms
50 ms
69 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Laurelplace.ca, 54% (60 requests) were made to Parkplaceseniorsliving.com and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (955 ms) relates to the external source Parkplaceseniorsliving.com.
Page size can be reduced by 92.2 kB (4%)
2.1 MB
2.0 MB
In fact, the total size of Laurelplace.ca main page is 2.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. 80% 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 81.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 81.6 kB or 80% of the original size.
Potential reduce by 3.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. Laurel Place images are well optimized though.
Potential reduce by 5.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Laurelplace.ca has all CSS files already compressed.
Number of requests can be reduced by 63 (64%)
98
35
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Laurel Place. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
laurelplace.ca
175 ms
laurelplace.ca
257 ms
157 ms
css
50 ms
font-awesome.min.css
69 ms
hti8h.css
59 ms
jquery-ui.css
75 ms
hti8h.css
96 ms
font-awesome.min.css
87 ms
hti8h.css
98 ms
hti8h.css
100 ms
hti8h.css
125 ms
hti8h.css
94 ms
hti8h.css
96 ms
hti8h.css
132 ms
hti8h.css
123 ms
hti8h.css
132 ms
hti8h.css
123 ms
hti8h.css
122 ms
page.js
86 ms
jquery.min.js
166 ms
jquery-migrate.min.js
142 ms
addtoany.min.js
140 ms
wpgmza_data.js
141 ms
core.min.js
144 ms
decision_tree.js
143 ms
owl.carousel.js
160 ms
script.js
162 ms
js
148 ms
123456807165
451 ms
hti8h.css
161 ms
jquery.scrollUp.min.js
161 ms
animations.min.js
287 ms
skip-link-focus-fix.min.js
288 ms
custom-scripts.min.js
288 ms
owl-settings.min.js
288 ms
pum-site-scripts.js
376 ms
jquery.validate.min.js
288 ms
jquery.inputmask.min.js
289 ms
mailcheck.min.js
376 ms
punycode.min.js
393 ms
utils.min.js
375 ms
wpforms.min.js
375 ms
api.js
90 ms
css
25 ms
eso.Ep5bSEmr.js
20 ms
gtm.js
229 ms
gtm.js
339 ms
hotjar-3322472.js
377 ms
_EgK1WO8cY4
405 ms
embed
421 ms
icon-arrow-down-primary.png
230 ms
Park-Place-Logo-2018-MOBILE.svg
228 ms
Park-Place-Logo-2018.svg
231 ms
Laurel-Place-Seniors-Header-Image.jpg
340 ms
Laurel-Place-Logo.png
227 ms
laurel-place-site-leader-liezel-hippsley.jpg
230 ms
Laurel-Place-Gallery-1.jpg
319 ms
Laurel-Place-Gallery-2.png
406 ms
Laurel-Place-Gallery-4.jpg
338 ms
Laurel-Place-Gallery-3.jpg
319 ms
Laurel-Place-Gallery-5.jpg
319 ms
Laurel-Place-Gallery-6.jpg
384 ms
Laurel-Place-Gallery-7.jpg
402 ms
Laurel-Place-Gallery-8.jpg
406 ms
Laurel-Place-Gallery-9.jpg
406 ms
Laurel-Place-Gallery-10.jpg
559 ms
Laurel-Place-Gallery-11.jpg
596 ms
Laurel-Place-Gallery-12.jpg
559 ms
Laurel-Place-Gallery-13.jpg
559 ms
Laurel-Place-Gallery-14.jpg
584 ms
Laurel-Place-Gallery-15.jpg
589 ms
Laurel-Place-Gallery-16.jpg
599 ms
Laurel-Place-Gallery-17.jpg
596 ms
submit-spin.svg
596 ms
Leaf-Icon-Mobile-ParkPlace.png
553 ms
js
155 ms
analytics.js
255 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
253 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
253 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
298 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqs.woff
344 ms
fontawesome-webfont.woff
955 ms
fontawesome-webfont.woff
146 ms
fontawesome-webfont.woff
148 ms
sm.25.html
144 ms
123456807165
820 ms
fbevents.js
175 ms
destination
228 ms
www-player.css
67 ms
modules.84f80a92c39bbd76564a.js
244 ms
collect
128 ms
www-embed-player.js
138 ms
base.js
245 ms
js
638 ms
collect
525 ms
asyncPixelSync
414 ms
ad_status.js
490 ms
yHiuAayzh7ZXFXvbIOrPkyv85wwmgA2suXoAI6Ktxww.js
207 ms
embed.js
137 ms
ga-audiences
304 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
196 ms
KFOmCnqEu92Fr1Mu4mxM.woff
200 ms
demconf.jpg
188 ms
fdec3fd1321b8743
312 ms
id
21 ms
qmap
23 ms
Create
28 ms
pixel.gif
156 ms
check
105 ms
1000.gif
35 ms
GenerateIT
17 ms
laurelplace.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
laurelplace.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
laurelplace.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Laurelplace.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 Laurelplace.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.
laurelplace.ca
Open Graph description is not detected on the main page of Laurel Place. 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: