1.3 sec in total
72 ms
1.2 sec
84 ms
Click here to check amazing Xfacto content. Otherwise, check out these important facts you probably never knew about xfacto.ca
Digital media and medical education provider for Canadian healthcare and pharmaceutical organizations: eLearning, training, independent meeting reports and web-based learning.
Visit xfacto.caWe analyzed Xfacto.ca page load time and found that the first response time was 72 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.
xfacto.ca performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value9.3 s
1/100
25%
Value22.6 s
0/100
10%
Value32,430 ms
0/100
30%
Value0.297
40/100
15%
Value45.8 s
0/100
10%
72 ms
91 ms
220 ms
46 ms
248 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 86% of them (50 requests) were addressed to the original Xfacto.ca, 3% (2 requests) were made to Fast.wistia.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (446 ms) belongs to the original domain Xfacto.ca.
Page size can be reduced by 712.4 kB (18%)
4.1 MB
3.3 MB
In fact, the total size of Xfacto.ca main page is 4.1 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 3.0 MB which makes up the majority of the site volume.
Potential reduce by 24.0 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.9 kB, which is 22% 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 24.0 kB or 76% of the original size.
Potential reduce by 91.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. Xfacto images are well optimized though.
Potential reduce by 292.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 292.9 kB or 40% of the original size.
Potential reduce by 303.5 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. Xfacto.ca needs all CSS files to be minified and compressed as it can save up to 303.5 kB or 87% of the original size.
Number of requests can be reduced by 28 (50%)
56
28
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xfacto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
xfacto.ca
72 ms
91 ms
global-style.css
220 ms
fractionslider.css
46 ms
jwv1eln.js
248 ms
jquery.js
110 ms
bootstrap.min.js
99 ms
modernizr.custom.93679.js
127 ms
jquery.mousewheel-3.0.6.pack.js
102 ms
jquery.cookie.js
103 ms
jquery.easing.js
124 ms
bootstrap-hover-dropdown.min.js
128 ms
jquery.ui.totop.min.js
128 ms
jquery.mixitup.js
134 ms
jquery.mixitup.init.js
150 ms
jquery.wp.custom.js
151 ms
jquery.fractionslider.js
181 ms
jquery.fractionslider.init.js
153 ms
heartcode-canvasloader-min.js
160 ms
jwplayer.js
306 ms
iframe-api-v1.js
90 ms
script.js
176 ms
css
62 ms
bootstrap.min.css
82 ms
jquery.fancybox.css
29 ms
font-awesome.css
55 ms
animate.css
87 ms
easypiechart.css
29 ms
timeline.css
57 ms
analytics.js
117 ms
xfacto.png
110 ms
fs-spinner.gif
110 ms
Lignes.png
259 ms
LogoMEDX.png
111 ms
Laptop.png
194 ms
DVDcase.png
109 ms
iPad.png
111 ms
iMac.png
125 ms
enveloppe.png
263 ms
micro.png
203 ms
book.png
258 ms
crayon.png
179 ms
livre_ferme.png
257 ms
Ipad.png
258 ms
Laptop.png
318 ms
2014_Xfacto_Promo_Video_en.jpg
270 ms
hypertension_en.png
446 ms
diabete_en.png
367 ms
instructions.png
272 ms
fontawesome-webfont.woff
233 ms
iframe_shim
102 ms
elearning.png
194 ms
meeting.png
197 ms
expert.png
209 ms
web.png
222 ms
collect
15 ms
E-v1.js
22 ms
nr-885.min.js
100 ms
xfacto.ca accessibility score
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
Links do not have a discernible name
xfacto.ca 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
Page has valid source maps
xfacto.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xfacto.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 Xfacto.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.
xfacto.ca
Open Graph description is not detected on the main page of Xfacto. 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: