3 sec in total
836 ms
1.8 sec
334 ms
Visit faq-qnw.org now to see the best up-to-date Faq Qnw content and also check out these interesting facts you probably never knew about faq-qnw.org
Visit faq-qnw.orgWe analyzed Faq-qnw.org page load time and found that the first response time was 836 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
faq-qnw.org performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value16.3 s
0/100
25%
Value8.3 s
20/100
10%
Value490 ms
58/100
30%
Value1.127
1/100
15%
Value13.4 s
11/100
10%
836 ms
47 ms
65 ms
65 ms
66 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 95% of them (61 requests) were addressed to the original Faq-qnw.org, 3% (2 requests) were made to Paypalobjects.com and 2% (1 request) were made to Api.twitter.com. The less responsive or slowest element that took the longest time to load (836 ms) belongs to the original domain Faq-qnw.org.
Page size can be reduced by 550.5 kB (46%)
1.2 MB
650.7 kB
In fact, the total size of Faq-qnw.org main page is 1.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. 30% of websites need less resources to load. Javascripts take 582.5 kB which makes up the majority of the site volume.
Potential reduce by 35.4 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 35.4 kB or 80% of the original size.
Potential reduce by 53.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. Obviously, Faq Qnw needs image optimization as it can save up to 53.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 397.0 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 397.0 kB or 68% of the original size.
Potential reduce by 64.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. Faq-qnw.org needs all CSS files to be minified and compressed as it can save up to 64.4 kB or 82% of the original size.
Number of requests can be reduced by 37 (60%)
62
25
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faq Qnw. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
faq-qnw.org
836 ms
node.css
47 ms
defaults.css
65 ms
system.css
65 ms
system-menus.css
66 ms
user.css
66 ms
content-module.css
69 ms
ckeditor.css
70 ms
ctools.css
93 ms
date.css
94 ms
filefield.css
94 ms
views.css
94 ms
views_cycle.css
109 ms
views_cycle_sidelist_right.css
96 ms
qnw-layout.css
146 ms
jquery.tweet.css
124 ms
jquery-1.6.4.min.js
204 ms
drupal.js
157 ms
cufon-yui.js
125 ms
Arial_Narrow_400-Arial_Narrow_700-Arial_Narrow_italic_400-Arial_Narrow_italic_700.font.js
236 ms
Helvetica_400.font.js
154 ms
Monaco_400.font.js
154 ms
Helvetica_700.font.js
248 ms
augment.min.js
184 ms
qnw-print.js
183 ms
qnw-menu.js
185 ms
qnw.js
232 ms
jquery.easing.1.3.js
232 ms
jquery.tweet.js
233 ms
raphael.js
262 ms
world.js
298 ms
cufon-drupal.js
267 ms
jquery.cycle.all.min.js
266 ms
views_cycle.js
256 ms
social_intro.png
192 ms
btn_donateCC_LG.gif
89 ms
social_paypal.png
187 ms
social_vimeo.png
189 ms
social_blogger.png
601 ms
header_bg.png
405 ms
logo_qnw.png
204 ms
secondary_navig_separator.png
85 ms
menu_bg.png
173 ms
header_image.png
312 ms
aga2015en.jpg
84 ms
12418040_10156451616865023_3945582031542286211_n_0.jpg
106 ms
devenez_membre_en.png
109 ms
social_twitter.png
187 ms
aga2015en_0.jpg
183 ms
12376173_929157813826645_2593714873471781821_n_1.jpg
203 ms
8mars2014.jpg
215 ms
pr_-_high_school_history.jpg
249 ms
pr_-_canadian_tribunal_aboriginal_children.jpg
259 ms
12376173_929157813826645_2593714873471781821_n.jpg
242 ms
inquiry_mmiw.png
610 ms
midwife_toolkit_0.jpg
273 ms
ecole.jpg
278 ms
pixel.gif
85 ms
bc_home.png
287 ms
bc_sep.png
305 ms
bc_sep_last.png
304 ms
user_timeline.json
39 ms
slideshow_dots.png
254 ms
print.css
29 ms
faq-qnw.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
faq-qnw.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
faq-qnw.org SEO score
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
Tap targets are not sized appropriately
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faq-qnw.org can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Faq-qnw.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.
faq-qnw.org
Open Graph description is not detected on the main page of Faq Qnw. 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: