1.9 sec in total
167 ms
1.1 sec
602 ms
Welcome to fct.ca homepage info - get ready to check FCT best content for Canada right away, or after learning these important things about fct.ca
At FCT we offer innovative processing solutions and title insurance for every stage of the real estate lifecycle. Learn more about what we can do for you.
Visit fct.caWe analyzed Fct.ca page load time and found that the first response time was 167 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
fct.ca performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value3.9 s
53/100
25%
Value5.1 s
61/100
10%
Value1,220 ms
20/100
30%
Value0.3
39/100
15%
Value17.1 s
4/100
10%
167 ms
45 ms
66 ms
62 ms
72 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 81% of them (43 requests) were addressed to the original Fct.ca, 4% (2 requests) were made to Static.hsappstatic.net and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (673 ms) belongs to the original domain Fct.ca.
Page size can be reduced by 249.6 kB (10%)
2.4 MB
2.1 MB
In fact, the total size of Fct.ca main page is 2.4 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 164.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. This page needs HTML code to be minified as it can gain 56.0 kB, which is 30% 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 164.4 kB or 89% of the original size.
Potential reduce by 62.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. FCT images are well optimized though.
Potential reduce by 7.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 15.0 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. Fct.ca needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 30% of the original size.
Number of requests can be reduced by 24 (50%)
48
24
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FCT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
fct.ca
167 ms
main.css
45 ms
theme-overrides.min.css
66 ms
module_154703552045_hd-page-navigation.min.css
62 ms
module_145307533174_hd-mega-menu.min.css
72 ms
LanguageSwitcher.css
60 ms
hd-resource-centre-listing.min.css
68 ms
module_148879947026_hd-resource-centre-featured.min.css
86 ms
module_145904564854_hd-switchback.min.css
135 ms
module_149444706141_hd-card-v4.min.css
93 ms
js
73 ms
jquery-1.7.1.js
92 ms
embed.js
51 ms
project.js
112 ms
module_154703552045_hd-page-navigation.min.js
104 ms
main.min.js
250 ms
module_145307533174_hd-mega-menu.min.js
125 ms
module_148879947026_hd-resource-centre-featured.min.js
123 ms
1875170.js
404 ms
index.js
279 ms
hotjar-4956158.js
285 ms
globe.png
256 ms
fct-logo.svg
203 ms
Glob.svg
208 ms
arrow-down.svg
210 ms
mega-menu-card-image.png
205 ms
mega-menu-services-card.jpg
201 ms
Le%20guide%20indispensable%20de%20l%E2%80%99assurance%20titres%20pour%20les%20propri%C3%A9taires.png
285 ms
Tanya-Fowler.jpg
211 ms
Hero-Image-Hompage-min-dark.jpg
409 ms
fct.ca
213 ms
Icon2.jpg
215 ms
icon3.jpg
213 ms
icon1.jpg
280 ms
shutterstock_93795685.jpg
284 ms
Title%20fraud%20--two%20females%20discussing.jpg
281 ms
shutterstock_1354795205.jpg
294 ms
Male%20writing.jpg
284 ms
Female%20on%20computer.jpg
673 ms
women-analysing-data.jpg
348 ms
verification-de-lidentite-numerique-comment-connaitre-son-client-tw-1.png
358 ms
Teammates%20working.jpg
546 ms
male%20on%20computer.jpg
348 ms
regular.woff
354 ms
500.woff
561 ms
600.woff
397 ms
700.woff
592 ms
web-interactives-embed.js
121 ms
fb.js
89 ms
collectedforms.js
96 ms
1875170.js
83 ms
banner.js
93 ms
modules.d7e8b7276297041c77dc.js
69 ms
fct.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-*] attributes are not valid or misspelled
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
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
fct.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fct.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Fct.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 Fct.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.
fct.ca
Open Graph data is detected on the main page of FCT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: