2.5 sec in total
299 ms
2 sec
234 ms
Click here to check amazing Tdb F E Post content for Canada. Otherwise, check out these important facts you probably never knew about tdb-f.epost.ca
Organize your bills and statements online with epost™. Get statements from companies, employers and municipalities and pay bills through your bank.
Visit tdb-f.epost.caWe analyzed Tdb-f.epost.ca page load time and found that the first response time was 299 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
tdb-f.epost.ca performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value12.0 s
0/100
25%
Value11.0 s
6/100
10%
Value2,840 ms
3/100
30%
Value0
100/100
15%
Value18.3 s
3/100
10%
299 ms
60 ms
89 ms
138 ms
174 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tdb-f.epost.ca, 3% (4 requests) were made to Tpc.googlesyndication.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (535 ms) relates to the external source Epost.ca.
Page size can be reduced by 715.8 kB (36%)
2.0 MB
1.3 MB
In fact, the total size of Tdb-f.epost.ca main page is 2.0 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 29.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 29.1 kB or 77% of the original size.
Potential reduce by 90.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. Tdb F E Post images are well optimized though.
Potential reduce by 561.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 561.7 kB or 67% of the original size.
Potential reduce by 34.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. Tdb-f.epost.ca needs all CSS files to be minified and compressed as it can save up to 34.0 kB or 76% of the original size.
Number of requests can be reduced by 19 (17%)
110
91
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tdb F E Post. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
landingPage.a
299 ms
css
60 ms
13104.css
89 ms
product.css
138 ms
vault-move.css
174 ms
jquery.js
301 ms
jquery-ui.js
299 ms
numeral.js
171 ms
numeral-fr-ca.js
206 ms
main.js
535 ms
vault-move.js
243 ms
magnific-popup.css
239 ms
jquery.magnific-popup.min.js
324 ms
gpt.js
63 ms
gtm.js
204 ms
top-background-1px.jpg
134 ms
Epost-Logo-en.png
163 ms
CPC-Logo-en.png
207 ms
hero-generic-en.jpg
430 ms
icon-question-mark.png
206 ms
step_1.png
207 ms
step_2.png
224 ms
step_3.png
269 ms
Left-Image-test-en.png
428 ms
Yellow-Star.png
241 ms
Right-Image-test-en.png
522 ms
FB.png
311 ms
TW.png
311 ms
LI.png
413 ms
send.png
412 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
159 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
170 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
203 ms
Canada-Logo.png
427 ms
pubads_impl_81.js
42 ms
ads
117 ms
container.html
77 ms
activityi;src=3743252;type=remar762;cat=canad819;ord=9184276312589.645
139 ms
imgad
24 ms
imgad
27 ms
imgad
63 ms
osd.js
74 ms
conversion.js
143 ms
j.gif
300 ms
i.cid
499 ms
lb
93 ms
drncpo_6Sept2012CanadaPostReMsgLandingEN_1
167 ms
queryProviders.a
158 ms
providersContent.a
125 ms
amc.js
188 ms
pixel
44 ms
31 ms
65 ms
Grey-Arrow-Left.png
62 ms
h36_en.png
63 ms
h36_en.png
64 ms
h36_en.png
66 ms
h36_en.png
61 ms
h36_en.png
63 ms
h36_en.png
107 ms
h36_en.png
108 ms
h36_en.png
110 ms
h36_en.png
113 ms
h36_en.png
111 ms
h36_en.png
149 ms
h36_en.png
166 ms
h36_en.png
153 ms
h36_en.png
167 ms
h36_en.png
165 ms
h36_en.png
167 ms
h36_en.png
193 ms
h36_en.png
205 ms
h36_en.png
215 ms
h36_en.png
212 ms
h36_en.png
211 ms
h36_en.png
212 ms
h36_en.png
243 ms
h36_en.png
251 ms
h36_en.png
261 ms
h36_en.png
259 ms
h36_en.png
262 ms
h36_en.png
260 ms
h36_en.png
297 ms
h36_en.png
298 ms
h36_en.png
307 ms
h36_en.png
309 ms
h36_en.png
312 ms
h36_en.png
310 ms
h36_en.png
338 ms
blank.gif
14 ms
epost.js
60 ms
h36_en.png
288 ms
h36_en.png
300 ms
h36_en.png
302 ms
h36_en.png
300 ms
h36_en.png
302 ms
h36_en.png
328 ms
h36_en.png
299 ms
h36_en.png
304 ms
h36_en.png
303 ms
h36_en.png
305 ms
h36_en.png
278 ms
h36_en.png
291 ms
h36_en.png
307 ms
h36_en.png
290 ms
h36_en.png
292 ms
h36_en.png
295 ms
h36_en.png
296 ms
s92870937706902
11 ms
h36_en.png
291 ms
h36_en.png
297 ms
h36_en.png
300 ms
h36_en.png
294 ms
h36_en.png
301 ms
h36_en.png
301 ms
Grey-Arrow-Right.png
287 ms
pixel
38 ms
i.match
401 ms
tdb-f.epost.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
tdb-f.epost.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
Missing source maps for large first-party JavaScript
tdb-f.epost.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
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tdb-f.epost.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 Tdb-f.epost.ca main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
tdb-f.epost.ca
Open Graph description is not detected on the main page of Tdb F E Post. 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: