872 ms in total
37 ms
493 ms
342 ms
Visit boycefuneralhome.ca now to see the best up-to-date Boyce Funeral Home content for Canada and also check out these interesting facts you probably never knew about boycefuneralhome.ca
As a family owned funeral home built on a tradition of caring, we are committed to serving the needs of our community. We invite you to browse throu
Visit boycefuneralhome.caWe analyzed Boycefuneralhome.ca page load time and found that the first response time was 37 ms and then it took 835 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.
boycefuneralhome.ca performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value12.5 s
0/100
25%
Value10.2 s
9/100
10%
Value5,540 ms
0/100
30%
Value0.819
4/100
15%
Value27.3 s
0/100
10%
37 ms
36 ms
44 ms
52 ms
53 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 92% of them (56 requests) were addressed to the original Boycefuneralhome.ca, 7% (4 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (114 ms) belongs to the original domain Boycefuneralhome.ca.
Page size can be reduced by 44.0 kB (85%)
51.5 kB
7.6 kB
In fact, the total size of Boycefuneralhome.ca main page is 51.5 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. 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. HTML takes 51.5 kB which makes up the majority of the site volume.
Potential reduce by 44.0 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. This page needs HTML code to be minified as it can gain 18.9 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 44.0 kB or 85% of the original size.
Number of requests can be reduced by 26 (45%)
58
32
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Boyce Funeral Home. 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 13 to 1 for CSS and as a result speed up the page load time.
boycefuneralhome.ca
37 ms
css
36 ms
css
44 ms
css
52 ms
css
53 ms
standard-styles.css
8 ms
normalize.min.css
23 ms
layout-styles.css
28 ms
skin.css
19 ms
responsive.css
29 ms
brown-red.css
22 ms
yui-min.js
29 ms
js
43 ms
YuiConfig.js
29 ms
respond.min.js
27 ms
combo.html
4 ms
pattern3.jpg
53 ms
obit-bg.jpg
55 ms
nav-icon.png
53 ms
Boyce_monogram4-1-.png
58 ms
pattern.jpg
53 ms
slide-shadow.png
54 ms
slide3.jpg
57 ms
slide1.jpg
73 ms
slide5.jpg
59 ms
Boyce-Text-Logo.png
60 ms
golden-frame.png
53 ms
main-bg.png
63 ms
100-years-logo-very-small.png
57 ms
gold-border.png
114 ms
tabs-inactive.png
59 ms
Elli-Rossol.jpg
60 ms
Ronald-Delwo.jpg
58 ms
Marlene-Hube.jpg
60 ms
Erwin-Stewart.jpg
61 ms
Leslie-Goddard.jpg
61 ms
Helen-Scheels.jpg
62 ms
Gwendoline-O-Brien.jpg
62 ms
Bruce-Armsden.jpg
62 ms
Theresa-Mosseau.jpg
63 ms
pattern2.jpg
64 ms
Obits.jpg
62 ms
Pre-Arrange-Online.jpg
64 ms
Services2.jpg
65 ms
footer.jpg
64 ms
bullet.png
64 ms
combo.html
34 ms
javascript-combo.html
34 ms
merriweather-regular-webfont.woff
42 ms
belgrano-regular-webfont.woff
42 ms
javascript-combo.html
12 ms
facebook_32.png
35 ms
twitter_32.png
35 ms
linkedin_32.png
35 ms
combo.html
6 ms
combo.html
6 ms
combo.html
3 ms
combo.html
9 ms
javascript-combo.html
9 ms
arrow.png
8 ms
arrow-180.png
8 ms
boycefuneralhome.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
boycefuneralhome.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
boycefuneralhome.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Boycefuneralhome.ca 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 Boycefuneralhome.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.
boycefuneralhome.ca
Open Graph description is not detected on the main page of Boyce Funeral Home. 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: