10 sec in total
3.8 sec
5.8 sec
517 ms
Welcome to fqu.ca homepage info - get ready to check Fqu best content right away, or after learning these important things about fqu.ca
Visit fqu.caWe analyzed Fqu.ca page load time and found that the first response time was 3.8 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fqu.ca performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value6.1 s
12/100
25%
Value6.9 s
33/100
10%
Value890 ms
32/100
30%
Value0.849
4/100
15%
Value15.8 s
6/100
10%
3776 ms
23 ms
224 ms
212 ms
217 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 62% of them (60 requests) were addressed to the original Fqu.ca, 6% (6 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to I2.wp.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Fqu.ca.
Page size can be reduced by 954.1 kB (34%)
2.8 MB
1.9 MB
In fact, the total size of Fqu.ca main page is 2.8 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 100.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 100.7 kB or 81% of the original size.
Potential reduce by 13.9 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. Fqu images are well optimized though.
Potential reduce by 480.9 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 480.9 kB or 67% of the original size.
Potential reduce by 358.7 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. Fqu.ca needs all CSS files to be minified and compressed as it can save up to 358.7 kB or 70% of the original size.
Number of requests can be reduced by 54 (61%)
89
35
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fqu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
fqu.ca
3776 ms
analytics.js
23 ms
wp-emoji-release.min.js
224 ms
bwg_frontend.css
212 ms
sumoselect.css
217 ms
font-awesome.css
266 ms
jquery.mCustomScrollbar.css
244 ms
polls-css.css
190 ms
css
38 ms
css
55 ms
bootstrap.min.css
382 ms
font-awesome.min.css
349 ms
style.css
465 ms
style.css
397 ms
jetpack.css
443 ms
addtoany.min.css
392 ms
jquery.js
615 ms
jquery-migrate.min.js
486 ms
bwg_frontend.js
487 ms
jquery.sumoselect.min.js
488 ms
jquery.mobile.js
532 ms
jquery.mCustomScrollbar.concat.min.js
534 ms
jquery.fullscreen-0.4.1.js
562 ms
bwg_gallery_box.js
563 ms
api.js
50 ms
plugin.css
661 ms
datatables.css
660 ms
collect
18 ms
collect
54 ms
jquery.cycle.js
610 ms
slideshow-shortcode.js
610 ms
photon.js
653 ms
polls-js.js
696 ms
devicepx-jetpack.js
6 ms
gprofiles.js
54 ms
wpgroho.js
721 ms
bootstrap.min.js
807 ms
jquery.knob.min.js
810 ms
smoothscroll.min.js
805 ms
scrollReveal.min.js
723 ms
parallax.js
812 ms
zerif.js
811 ms
wp-embed.min.js
816 ms
e-201611.js
9 ms
recaptcha__en.js
99 ms
Logo.jpg
79 ms
fqu_logo-logo-simple.png
490 ms
page.js
95 ms
received_993749824019442.jpeg
76 ms
AUG.jpg
94 ms
logo.jpg
78 ms
Tourn%C3%A9e-2016_FB2-e1452183845802.jpg
53 ms
LOGO_CQU4_OUT_2.png
53 ms
logoGala.png
56 ms
Naufrage-logo-300x240.jpg
56 ms
Joelletramblay.jpg
1313 ms
left-arrow.png
451 ms
right-arrow.png
450 ms
lines-dark.png
450 ms
AUM.jpg
450 ms
Ajjuqlogo.png
538 ms
logo_AUS.png
538 ms
FUL.jpg
539 ms
Ultimate-St-Jean.jpg
548 ms
USL.jpg
539 ms
URlogo.png
584 ms
AUG.jpg
585 ms
Atruf.png
599 ms
LOGO_CQU4_OUT-150x150.png
600 ms
LOGO_CQU5_OUT-150x150.png
609 ms
LOGO_CQU7_OUT-150x150.png
667 ms
LogoFQU145x132.jpeg
682 ms
Nicolas.jpg
681 ms
IMG_20140721_120845-259x300.jpg
920 ms
map25-redish.png
858 ms
envelope4-green.png
898 ms
telephone65-blue.png
882 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
36 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
37 ms
wkfQbvfT_02e2IWO3yYueQ.woff
37 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
37 ms
fontawesome-webfont.woff
1030 ms
fontawesome-webfont.woff
1137 ms
sm13.html
328 ms
icons.34.png
292 ms
hovercard.css
90 ms
services.css
139 ms
anchor
50 ms
g.gif
15 ms
ga.js
27 ms
styles__ltr.css
5 ms
-FHGegChvKELgmHNPF97Aj33qC9PBXl7UyexHItfpAU.js
24 ms
webworker.js
34 ms
logo_48.png
32 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
57 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
57 ms
recaptcha__en.js
7 ms
fqu.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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 IDs are not unique
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
No form fields have multiple labels
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
fqu.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fqu.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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fqu.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Fqu.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.
fqu.ca
Open Graph description is not detected on the main page of Fqu. 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: