33.7 sec in total
144 ms
30.9 sec
2.7 sec
Visit findaperson.canada411.ca now to see the best up-to-date Findaperson Canada411 content for Canada and also check out these interesting facts you probably never knew about findaperson.canada411.ca
Find any persons across Canada on Canada 411 thanks to Canada411.ca™, Canada’s People Directory. Get maps, direction search, area or postal codes or even perform a reverse search with an address or ph...
Visit findaperson.canada411.caWe analyzed Findaperson.canada411.ca page load time and found that the first response time was 144 ms and then it took 33.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
findaperson.canada411.ca performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value4.9 s
29/100
25%
Value10.0 s
9/100
10%
Value2,030 ms
7/100
30%
Value0.123
83/100
15%
Value27.2 s
0/100
10%
144 ms
356 ms
423 ms
780 ms
588 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Findaperson.canada411.ca, 14% (21 requests) were made to Static.yellowpages.ca and 11% (17 requests) were made to Router.infolinks.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Cdn.districtm.ca.
Page size can be reduced by 129.5 kB (16%)
817.9 kB
688.4 kB
In fact, the total size of Findaperson.canada411.ca main page is 817.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 580.0 kB which makes up the majority of the site volume.
Potential reduce by 103.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 16.4 kB, which is 12% 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 103.0 kB or 75% of the original size.
Potential reduce by 8.8 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. Findaperson Canada411 images are well optimized though.
Potential reduce by 17.7 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 72 B
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. Findaperson.canada411.ca has all CSS files already compressed.
Number of requests can be reduced by 75 (62%)
121
46
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Findaperson Canada411. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
findaperson.canada411.ca
144 ms
www.canada411.ca
356 ms
gtm.js
423 ms
js
780 ms
c411.css
588 ms
c411Home.css
586 ms
mediative_en.js
587 ms
yellowMapsModule_osm.css
701 ms
c411.js
758 ms
c411Home.js
679 ms
utag.js
757 ms
js
584 ms
185248-78466117002985.js
783 ms
merge.v4.2.103128.js
19959 ms
gpt.js
1095 ms
cc.js
1276 ms
uv9enbd29.js
1196 ms
logo-en.svg
158 ms
logo-en.svg
77 ms
logo-en.svg
140 ms
logo--bw.svg
509 ms
yp-app-en.jpg
139 ms
appstore--en.svg
116 ms
playstore--en.svg
356 ms
logo.svg
398 ms
YPLocalWeb-Book.woff
535 ms
YPLocalWeb-Medium.woff
505 ms
YPLocalWeb-Bold.woff
504 ms
ypca-icons.woff
505 ms
analytics.js
1461 ms
rid
1242 ms
telcos-sprite.png
959 ms
YPLocalWeb-BookItalic.woff
991 ms
pubads_impl_2022082302.js
1401 ms
ppub_config
1334 ms
controltag.js.0631b7d64dbbd3656a8b7368ad227a04
633 ms
collect
1455 ms
collect
1390 ms
cygnus
1712 ms
cygnus
1650 ms
v1
1298 ms
cygnus
1742 ms
7e56b07b-c515-4a97-9034-79ce6b9ae380
1512 ms
collect
1513 ms
integrator.js
1234 ms
ads
439 ms
ads
452 ms
container.html
961 ms
ads
604 ms
ads
1221 ms
ads
754 ms
infolinks_main.js
353 ms
ga-audiences
275 ms
ice.js
101 ms
lcmanage
144 ms
gsd
163 ms
manage
163 ms
iqusync-1.17.min.js
35 ms
ImgSync
375 ms
2007 ms
cksync
2045 ms
doq.htm
2362 ms
pixel
1797 ms
sonobi-usync
1233 ms
usermatch
1919 ms
mnet-usync
1194 ms
zeta-usync
1190 ms
33a-usync
1215 ms
2140 ms
ca.png
2248 ms
apn-usync
1215 ms
in_search.js
1137 ms
ima3.js
2578 ms
pbice.js
1508 ms
imd-usync
639 ms
tplift
637 ms
VR-usync
769 ms
ox-usync
829 ms
ProfilesEngineServlet
1695 ms
outh-usync
942 ms
getads.htm
973 ms
pm_match
2329 ms
ix-usync
383 ms
RX-6950682c-20f2-4a32-920b-cc059a4139d5-005
2035 ms
usermatchredir
777 ms
rum
2754 ms
sovrn-usync
1378 ms
in-search-shadow.png
1180 ms
adsbygoogle.js
2016 ms
vidice.js
394 ms
zmn-usync
1095 ms
pixel
1081 ms
pixel
1025 ms
crum
990 ms
crum
1362 ms
user_sync.html
1683 ms
ur-usync
1292 ms
dcm
1293 ms
match
1616 ms
rum
551 ms
crum
240 ms
usync.html
527 ms
match
373 ms
PugMaster
284 ms
pubmatic
110 ms
match
59 ms
usync.js
353 ms
pixel
356 ms
3B302B3F-C5C2-4791-8F50-D5B2A6405517
2825 ms
usersync.aspx
3293 ms
sn.ashx
3640 ms
sync
3549 ms
pubmatic
3316 ms
match
612 ms
khaos.jpg
3237 ms
user_sync.html
502 ms
match
1606 ms
rum
1327 ms
match
591 ms
ImgSync
617 ms
Pug
1154 ms
i.match
1551 ms
Pug
834 ms
Pug
753 ms
apn
1599 ms
ecc
862 ms
pixel
686 ms
tap.php
1284 ms
tap.php
1246 ms
pbmtc.gif
554 ms
tap.php
1161 ms
sn.ashx
433 ms
ecc
1079 ms
ImgSync
471 ms
tap.php
680 ms
tap.php
523 ms
tap.php
521 ms
ImgSync
520 ms
ImgSync
519 ms
d1ba4609
698 ms
Pug
439 ms
tap.php
494 ms
v2
877 ms
d1ba4609
518 ms
d1ba4609
757 ms
tap.php
143 ms
nr-spa-1216.min.js
194 ms
sodar
251 ms
container-1.0.html
165 ms
d901b4dcbe
105 ms
sodar2.js
42 ms
findaperson.canada411.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.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
findaperson.canada411.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
Page has valid source maps
findaperson.canada411.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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Findaperson.canada411.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 Findaperson.canada411.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.
findaperson.canada411.ca
Open Graph data is detected on the main page of Findaperson Canada411. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: