2 sec in total
79 ms
1.6 sec
295 ms
Welcome to fccq.ca homepage info - get ready to check FCCQ best content for Canada right away, or after learning these important things about fccq.ca
Du réseau d'affaire aux programmes d'aides, subventions, activités et ressources, la FCCQ porte les entreprises du Québec vers le succès
Visit fccq.caWe analyzed Fccq.ca page load time and found that the first response time was 79 ms and then it took 1.9 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.
fccq.ca performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value14.3 s
0/100
25%
Value11.5 s
5/100
10%
Value820 ms
35/100
30%
Value0.551
13/100
15%
Value14.1 s
10/100
10%
79 ms
387 ms
118 ms
138 ms
87 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 44% of them (54 requests) were addressed to the original Fccq.ca, 18% (22 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (387 ms) belongs to the original domain Fccq.ca.
Page size can be reduced by 153.9 kB (18%)
853.6 kB
699.7 kB
In fact, the total size of Fccq.ca main page is 853.6 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. 70% of websites need less resources to load. Images take 646.5 kB which makes up the majority of the site volume.
Potential reduce by 41.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 12.3 kB, which is 24% 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 41.9 kB or 81% of the original size.
Potential reduce by 16.4 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. FCCQ images are well optimized though.
Potential reduce by 67.4 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 67.4 kB or 55% of the original size.
Potential reduce by 28.1 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. Fccq.ca needs all CSS files to be minified and compressed as it can save up to 28.1 kB or 88% of the original size.
Number of requests can be reduced by 54 (47%)
116
62
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FCCQ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fccq.ca
79 ms
www.fccq.ca
387 ms
style.css
118 ms
swapImage.js
138 ms
mm_css_menu.js
87 ms
jquery-latest.min.js
7 ms
jquery.js
94 ms
jquery.cycle.all.min.js
99 ms
menu-refonte.css
96 ms
swfobject_modified.js
167 ms
SpryTooltip.js
170 ms
SpryTooltip.css
168 ms
all.js
13 ms
px
39 ms
gtm.js
48 ms
bkg-wave2.jpg
207 ms
btn_rechercheA-refonte.png
157 ms
spacer.gif
157 ms
header-fccq.png
157 ms
btn_menu1A.jpg
156 ms
btn_menu2A.jpg
158 ms
btn_menu3A.jpg
221 ms
btn_menu4A.jpg
212 ms
btn_menu5A.jpg
221 ms
btn_menu6A.jpg
221 ms
btn_menu7A.jpg
222 ms
btn_menu8A.jpg
271 ms
shadow_menu.jpg
269 ms
CES.jpg
271 ms
mercuriades-2016-reservation-places.jpg
275 ms
logos-fccq-header.gif
269 ms
dotes.jpg
261 ms
eCertify.jpg
329 ms
reso-sociaux.jpg
307 ms
acclogo.png
328 ms
RECYC-QUEBEC-.jpg
312 ms
widgets.js
148 ms
ga.js
30 ms
173 ms
xd_arbiter.php
83 ms
xd_arbiter.php
170 ms
conversion_async.js
100 ms
analytics.js
59 ms
fbds.js
66 ms
js.cfm
187 ms
fbevents.js
96 ms
__utm.gif
98 ms
collect
100 ms
collect
50 ms
70 ms
75 ms
83 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
126 ms
66 ms
28 ms
like_box.php
319 ms
38 ms
collect
18 ms
38 ms
collect
11 ms
syndication
96 ms
541980649855668224
207 ms
kyEKgjk51ZE.css
55 ms
xgj7bXhJNEH.css
48 ms
Czh0gDTFcBt.css
54 ms
N-k91nHCZS2.css
64 ms
ZeuPykSxSED.css
55 ms
q68gy-v_YMF.js
63 ms
8w-1WQE8wsO.js
86 ms
0wM5s1Khldu.js
85 ms
1bNoFZUdlYZ.js
85 ms
njO1TPvGzoR.js
97 ms
1QuX41zDRrx.js
99 ms
Oagsvfb4VWi.js
100 ms
LTv6ZK-5zxz.js
104 ms
1FCa-btixu2.js
101 ms
12669489_1102596163107118_4345205670769002143_n.jpg
109 ms
safe_image.php
206 ms
14687_928988180467918_80660234570728392_n.png
39 ms
1384230_1129934307039970_4240978013249009131_n.jpg
40 ms
1914736_1127661753933892_7238334069057742548_n.jpg
38 ms
wL6VQj7Ab77.png
37 ms
s7jcwEQH7Sx.png
35 ms
QDwYpIaRyfG.png
36 ms
bNvHN6v1NeH.png
35 ms
b53Ajb4ihCP.gif
36 ms
K00K-UgnsKu.png
36 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
105 ms
ce40e648b09ef52ed63ff05b32bd3006_normal.png
99 ms
OSOFSZaG_normal.png
102 ms
Cdmh9jvXEAAipDb.jpg:small
103 ms
Ccd4873XEAA1cEG.jpg:small
101 ms
Cb3FxIzVIAAuQ7t.jpg:small
102 ms
Ca9QkEOWEAA_sSR.jpg:small
103 ms
Ca4B60nWIAEZVuR.jpg:small
107 ms
I6-MnjEovm5.js
27 ms
pQrUxxo5oQp.js
27 ms
btn_menu1B.jpg
67 ms
23 ms
btn_menu2B.jpg
54 ms
btn_menu3B.jpg
49 ms
btn_menu4B.jpg
72 ms
btn_menu5B.jpg
71 ms
btn_menu6B.jpg
50 ms
btn_menu7B.jpg
92 ms
btn_menu8B.jpg
98 ms
btn_rechercheB.jpg
94 ms
fccq_blogueB.jpg
104 ms
fccq_corusB.jpg
111 ms
fccq_qeaB.jpg
107 ms
fccq_corridorsB.jpg
148 ms
fccq_mercuriadesB.jpg
160 ms
fccq_100B.jpg
135 ms
fccq_maxB.jpg
144 ms
fccq_mapB.jpg
148 ms
btn_nouvellesB.jpg
156 ms
btn_GD1B.jpg
179 ms
btn_GD2B.jpg
186 ms
btn_GD3B.jpg
192 ms
btn_GD4B.jpg
187 ms
13 ms
fccq.ca 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
fccq.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
fccq.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
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fccq.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fccq.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.
fccq.ca
Open Graph description is not detected on the main page of FCCQ. 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: