Tools & Wizards About Us
onmemory.ca screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

onmemory.ca

Alzheimer's disease | Caregiver's Guide | onmemory.ca

Page Load Speed

1.7 sec in total

First Response

354 ms

Resources Loaded

1.2 sec

Page Rendered

119 ms

onmemory.ca screenshot

About Website

Visit onmemory.ca now to see the best up-to-date Onmemory content for France and also check out these interesting facts you probably never knew about onmemory.ca

Visit onmemory.ca

Key Findings

We analyzed Onmemory.ca page load time and found that the first response time was 354 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

onmemory.ca performance score

0

Network Requests Diagram

onmemory.ca

354 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

82 ms

css_A7L9lzYfi0Rrggkhtup9J-NajVb47KzW_dN58Wk1YRE.css

154 ms

css_S4Ry1Tkb0RHhWE8wsuM7JHGOFhLyjlpFrjglYzcPbvw.css

163 ms

css_iemR6ttWWadJvM0zdoZRDna0xo2GM5mEPN13GgBk93Q.css

164 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 91% of them (32 requests) were addressed to the original Onmemory.ca, 6% (2 requests) were made to Admin.brightcove.com and 3% (1 request) were made to Pfizer.122.2o7.net. The less responsive or slowest element that took the longest time to load (392 ms) belongs to the original domain Onmemory.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 428.0 kB (75%)

Content Size

569.1 kB

After Optimization

141.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onmemory.ca main page is 569.1 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. 35% of websites need less resources to load. Javascripts take 407.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 34.8 kB

  • Original 42.7 kB
  • After minification 36.2 kB
  • After compression 7.9 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 6.4 kB, which is 15% 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 34.8 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 223 B

  • Original 9.0 kB
  • After minification 8.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. Onmemory images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 306.0 kB

  • Original 407.6 kB
  • After minification 314.3 kB
  • After compression 101.6 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 306.0 kB or 75% of the original size.

CSS Optimization

-79%

Potential reduce by 87.0 kB

  • Original 109.8 kB
  • After minification 107.4 kB
  • After compression 22.8 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. Onmemory.ca needs all CSS files to be minified and compressed as it can save up to 87.0 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (50%)

Requests Now

34

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onmemory.ca

onmemory.ca

354 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

82 ms

css_A7L9lzYfi0Rrggkhtup9J-NajVb47KzW_dN58Wk1YRE.css

css_A7L9lzYfi0Rrggkhtup9J-NajVb47KzW_dN58Wk1YRE.css

154 ms

css_S4Ry1Tkb0RHhWE8wsuM7JHGOFhLyjlpFrjglYzcPbvw.css

css_S4Ry1Tkb0RHhWE8wsuM7JHGOFhLyjlpFrjglYzcPbvw.css

163 ms

css_iemR6ttWWadJvM0zdoZRDna0xo2GM5mEPN13GgBk93Q.css

css_iemR6ttWWadJvM0zdoZRDna0xo2GM5mEPN13GgBk93Q.css

164 ms

css_qAmQ7pf-kfbUOZjgYyIsZenb2JU9cTU3hC_Hv2naS8k.css

css_qAmQ7pf-kfbUOZjgYyIsZenb2JU9cTU3hC_Hv2naS8k.css

165 ms

js_cHTDrv1RJARNySmmMaqZ0RqoX9XDreZGQsLwrt-XG3k.js

js_cHTDrv1RJARNySmmMaqZ0RqoX9XDreZGQsLwrt-XG3k.js

244 ms

js_NrP74gzX4jtoA_ZMkXMsgBEfgKuFt2yMlQzdI08Vj4E.js

js_NrP74gzX4jtoA_ZMkXMsgBEfgKuFt2yMlQzdI08Vj4E.js

324 ms

js_umujIl0z4r-7VquEjCRjLZbb8bgTl7dtlIZMFceqbbw.js

js_umujIl0z4r-7VquEjCRjLZbb8bgTl7dtlIZMFceqbbw.js

228 ms

js_BPQspc_JoWPQuOYHatUw1jTLgWJEw_02l6nZnvCVyJA.js

js_BPQspc_JoWPQuOYHatUw1jTLgWJEw_02l6nZnvCVyJA.js

243 ms

js_gb5-zfguVW3epXOMkZ5C3a4M-3zM_n5NDttVPWcAMXg.js

js_gb5-zfguVW3epXOMkZ5C3a4M-3zM_n5NDttVPWcAMXg.js

252 ms

BrightcoveExperiences.js

BrightcoveExperiences.js

6 ms

js_0EFAeDQIG9kUe8iCSkBKVAc4H6k3MmO8SxLyb9x644E.js

js_0EFAeDQIG9kUe8iCSkBKVAc4H6k3MmO8SxLyb9x644E.js

253 ms

js_Kfc-IQrKZLF-nGmy787YYRXEzfDlSv1HvjRNbo3V9Bg.js

js_Kfc-IQrKZLF-nGmy787YYRXEzfDlSv1HvjRNbo3V9Bg.js

377 ms

masthead-new.gif

masthead-new.gif

111 ms

printheader-en.gif

printheader-en.gif

112 ms

transparent.gif

transparent.gif

112 ms

160x41_Get_Flash_Player.jpg

160x41_Get_Flash_Player.jpg

113 ms

printfooterbar-en.gif

printfooterbar-en.gif

113 ms

alzheimer_soc_img.gif

alzheimer_soc_img.gif

116 ms

primary_menu_bg.gif

primary_menu_bg.gif

231 ms

secondary_menu_bg.gif

secondary_menu_bg.gif

150 ms

home_content_bg.gif

home_content_bg.gif

152 ms

tertiary_menu_bg-en.gif

tertiary_menu_bg-en.gif

152 ms

arrow_action.gif

arrow_action.gif

153 ms

featuresdivider.gif

featuresdivider.gif

178 ms

home_go_buttons_EN_book_light.gif

home_go_buttons_EN_book_light.gif

392 ms

footerbar.gif

footerbar.gif

235 ms

homeflash.js.txt

homeflash.js.txt

145 ms

upgrade_flash_player2.gif

upgrade_flash_player2.gif

8 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

144 ms

ui-icons_222222_256x240.png

ui-icons_222222_256x240.png

162 ms

arrows.png

arrows.png

220 ms

s73481220444664

s73481220444664

38 ms

css_4b_7wUNDq89XK8SLH6zjipRjdH1CfVGNO3QiJ0FYcjU.css

css_4b_7wUNDq89XK8SLH6zjipRjdH1CfVGNO3QiJ0FYcjU.css

83 ms

SEO Factors

onmemory.ca SEO score

0

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 Onmemory.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 Onmemory.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

onmemory.ca

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