4 sec in total
115 ms
1.1 sec
2.8 sec
Visit frq.gouv.qc.ca now to see the best up-to-date Frq Gouv content for Canada and also check out these interesting facts you probably never knew about frq.gouv.qc.ca
Les Fonds de recherche du Québec soutiennent l’excellence en recherche et la formation de la relève en recherche.
Visit frq.gouv.qc.caWe analyzed Frq.gouv.qc.ca page load time and found that the first response time was 115 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
frq.gouv.qc.ca performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value3.6 s
60/100
25%
Value6.3 s
41/100
10%
Value1,360 ms
16/100
30%
Value0.803
5/100
15%
Value13.5 s
11/100
10%
115 ms
63 ms
39 ms
38 ms
44 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 81% of them (39 requests) were addressed to the original Frq.gouv.qc.ca, 10% (5 requests) were made to Unpkg.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (280 ms) belongs to the original domain Frq.gouv.qc.ca.
Page size can be reduced by 149.1 kB (3%)
5.7 MB
5.6 MB
In fact, the total size of Frq.gouv.qc.ca main page is 5.7 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. 55% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.
Potential reduce by 125.1 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 125.1 kB or 84% of the original size.
Potential reduce by 24.0 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. Frq Gouv images are well optimized though.
Number of requests can be reduced by 8 (21%)
39
31
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frq Gouv. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
frq.gouv.qc.ca
115 ms
gtm.js
63 ms
core@2
39 ms
style.min.css
38 ms
css2
44 ms
image-renderer.css
54 ms
theme.css
116 ms
jquery-3.4.1.min.js
24 ms
lazyload.min.js
58 ms
8908b4a97bb53809d94201ff73d49cbf.js
223 ms
core@2.11.8
40 ms
tippy.js@6.3.7
23 ms
tippy-bundle.umd.min.js
15 ms
popper.min.js
16 ms
ajax-loading__icon.svg
167 ms
logo-qc.png
167 ms
page_accueil_2023-03-19_adobestock_545219730.jpeg.webp
170 ms
wave--mixed.svg
168 ms
bg-waves-lines--right.svg
179 ms
bg-waves-lines--left.svg
176 ms
fonds-ecran-propulsons.png.webp
167 ms
scientifique-en-chef_remi-quirion.png
232 ms
visuel-edi-1-1024x404.jpg.webp
166 ms
prix_publ_francais-1024x768.jpg.webp
193 ms
adobestock_717163380-1024x574.jpeg.webp
177 ms
914141_file_fr_CA_3.jpeg
194 ms
4419197_file_fr_CA_3.jpeg
209 ms
8544308_file_fr_CA_3.jpeg
245 ms
8327203_file_fr_CA_3.jpeg
226 ms
fond-de-recherche-quebec-2-1920x1281.jpg
251 ms
recherche-intersectorielle-1.png
264 ms
e.achouri_as_290263617-1024x476.jpeg.webp
222 ms
j.kildea_as_68160616_site_frq-1024x461.jpeg.webp
241 ms
s.koseki_as_363986072-1024x576.jpeg.webp
245 ms
s.tremblay_as_744786914_site_frq-1024x461.jpeg.webp
248 ms
e.kehayia_b.swaine_centre_commercial_as_277743052_site_frq-1024x461.jpeg.webp
259 ms
chaire_unesco_prevenir_radicalisation_as_400956440_site_frq-1024x461.jpeg.webp
263 ms
p.b.beauregard_as_431571246-1024x576.jpeg.webp
267 ms
s.del_rincon_as_458816151_editorial_use_only-1024x683.jpeg.webp
270 ms
v.lariviere_as_336484915-1024x411.jpeg.webp
270 ms
serrer_main_handshake-300x200.jpeg.webp
276 ms
visuel_politique_libre_acces_rvb_web_fond_blanc_vf-2-300x172.png.webp
280 ms
font
24 ms
fa-light-300.ttf
204 ms
fa-thin-100.ttf
203 ms
fa-regular-400.ttf
189 ms
fa-solid-900.ttf
203 ms
fa-brands-400.ttf
157 ms
frq.gouv.qc.ca accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
frq.gouv.qc.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
frq.gouv.qc.ca 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frq.gouv.qc.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 Frq.gouv.qc.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.
frq.gouv.qc.ca
Open Graph description is not detected on the main page of Frq Gouv. 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: