Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 0

    Best Practices

  • 77

    SEO

    Google-friendlier than
    36% of websites

Page Load Speed

1.4 sec in total

First Response

140 ms

Resources Loaded

967 ms

Page Rendered

250 ms

About Website

Click here to check amazing FEF Td content for Canada. Otherwise, check out these important facts you probably never knew about fef.td.com

Visit fef.td.com

Key Findings

We analyzed Fef.td.com page load time and found that the first response time was 140 ms and then it took 1.2 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.

Performance Metrics

fef.td.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value4,110 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.2

62/100

15%

TTI (Time to Interactive)

Value32.6 s

0/100

10%

Network Requests Diagram

140 ms

fef

34 ms

otSDKStub.js

93 ms

launch-cfc5a69df492.min.js

44 ms

clientlib-base.lc-1719539860248-lc.min.css

120 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fef.td.com, 11% (3 requests) were made to Cdn.cookielaw.org and 4% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (355 ms) relates to the external source Geolocation.onetrust.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 561.9 kB (35%)

Content Size

1.6 MB

After Optimization

1.1 MB

In fact, the total size of Fef.td.com main page is 1.6 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. 45% of websites need less resources to load. Images take 764.1 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 111.0 kB

  • Original 125.9 kB
  • After minification 92.4 kB
  • After compression 14.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 33.5 kB, which is 27% 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 111.0 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 764.1 kB
  • After minification 764.1 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. FEF Td images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 450.9 kB

  • Original 728.4 kB
  • After minification 728.4 kB
  • After compression 277.5 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 450.9 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (33%)

Requests Now

21

After Optimization

14

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEF Td. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

fef.td.com accessibility score

98

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

SEO Factors

fef.td.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fef.td.com 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 Fef.td.com 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of FEF Td. 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: