Tools & Wizards About Us
naturehouse.ca screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

naturehouse.ca

Nature Houses | Discover Parks

Page Load Speed

3.1 sec in total

First Response

57 ms

Resources Loaded

2.5 sec

Page Rendered

535 ms

naturehouse.ca screenshot

About Website

Welcome to naturehouse.ca homepage info - get ready to check Nature House best content right away, or after learning these important things about naturehouse.ca

Visit naturehouse.ca

Key Findings

We analyzed Naturehouse.ca page load time and found that the first response time was 57 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

naturehouse.ca performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

naturehouse.ca

57 ms

nature%20house

1699 ms

polyfills-c67a75d1b6f99dc8.js

35 ms

webpack-43386d87746722d3.js

110 ms

framework-d89b409eb2dda32d.js

69 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Naturehouse.ca, 84% (41 requests) were made to Discoverparks.ca and 8% (4 requests) were made to Admin.discoverparks.ca. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Discoverparks.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 287.4 kB (2%)

Content Size

12.2 MB

After Optimization

11.9 MB

  • HTML
  • Images

In fact, the total size of Naturehouse.ca main page is 12.2 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. 60% of websites need less resources to load. Images take 12.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 109.5 kB

  • Original 133.2 kB
  • After minification 133.1 kB
  • After compression 23.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 109.5 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 177.9 kB

  • Original 12.0 MB
  • After minification 11.8 MB

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. Nature House images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 13 (30%)

Requests Now

44

After Optimization

31

  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nature House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

naturehouse.ca

naturehouse.ca

57 ms

nature%20house

nature%20house

1699 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

35 ms

webpack-43386d87746722d3.js

webpack-43386d87746722d3.js

110 ms

framework-d89b409eb2dda32d.js

framework-d89b409eb2dda32d.js

69 ms

main-9e347c8c5d9ddff5.js

main-9e347c8c5d9ddff5.js

60 ms

_app-3bc33dfaecc8070d.js

_app-3bc33dfaecc8070d.js

80 ms

297-8faafe2d836f104a.js

297-8faafe2d836f104a.js

50 ms

8857-6f2d7314dc8e2a0d.js

8857-6f2d7314dc8e2a0d.js

48 ms

2102-ca16a076f7529f83.js

2102-ca16a076f7529f83.js

67 ms

%5Bslug%5D-f27c35f3442b2a83.js

%5Bslug%5D-f27c35f3442b2a83.js

67 ms

_buildManifest.js

_buildManifest.js

71 ms

_ssgManifest.js

_ssgManifest.js

79 ms

139dab41-736b-442c-b772-4af59cb23347

139dab41-736b-442c-b772-4af59cb23347

69 ms

bc4bc21c-f421-4f87-9b5e-d7504ddd94c3

bc4bc21c-f421-4f87-9b5e-d7504ddd94c3

72 ms

abd51d97-3406-43e6-a309-896b31fd98ca

abd51d97-3406-43e6-a309-896b31fd98ca

97 ms

921ae7fc-e2b6-48aa-a80d-73fc6a1c5168

921ae7fc-e2b6-48aa-a80d-73fc6a1c5168

98 ms

image

image

126 ms

image

image

204 ms

image

image

250 ms

image

image

297 ms

image

image

242 ms

image

image

260 ms

image

image

258 ms

image

image

320 ms

image

image

439 ms

image

image

386 ms

image

image

359 ms

image

image

450 ms

image

image

582 ms

image

image

460 ms

image

image

401 ms

image

image

430 ms

image

image

514 ms

image

image

486 ms

image

image

535 ms

image

image

527 ms

image

image

511 ms

image

image

556 ms

image

image

582 ms

image

image

589 ms

footer.png

footer.png

566 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

19 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

27 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

28 ms

ba698747c305a910.css

ba698747c305a910.css

69 ms

ba698747c305a910.css

ba698747c305a910.css

12 ms

ae4ed9c503fd1e33.css

ae4ed9c503fd1e33.css

14 ms

ae4ed9c503fd1e33.css

ae4ed9c503fd1e33.css

14 ms

Accessibility Review

naturehouse.ca accessibility score

85

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

naturehouse.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

naturehouse.ca SEO score

81

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naturehouse.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 Naturehouse.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.

Social Sharing Optimization

naturehouse.ca

Open Graph description is not detected on the main page of Nature House. 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: