Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

ecatalog-na.fst.com

Product Catalog | Freudenberg FST

Page Load Speed

28.5 sec in total

First Response

266 ms

Resources Loaded

24.6 sec

Page Rendered

3.6 sec

ecatalog-na.fst.com screenshot

About Website

Visit ecatalog-na.fst.com now to see the best up-to-date E Catalog Na FST content for United States and also check out these interesting facts you probably never knew about ecatalog-na.fst.com

Visit ecatalog-na.fst.com

Key Findings

We analyzed Ecatalog-na.fst.com page load time and found that the first response time was 266 ms and then it took 28.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ecatalog-na.fst.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value30,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value56.4 s

0/100

10%

Network Requests Diagram

ecatalog-na.fst.com

266 ms

en

2093 ms

polyfill.min.js

817 ms

outdatedbrowserpopup.js

20464 ms

d33c249.js

20116 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ecatalog-na.fst.com, 63% (19 requests) were made to Products.fst.com and 23% (7 requests) were made to Api.fst.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Products.fst.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (59%)

Content Size

4.1 MB

After Optimization

1.7 MB

In fact, the total size of Ecatalog-na.fst.com 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. HTML takes 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 2.3 MB

  • Original 3.1 MB
  • After minification 3.1 MB
  • After compression 756.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. 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 2.3 MB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 90.2 kB

  • Original 1.0 MB
  • After minification 912.3 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. E Catalog Na FST images are well optimized though.

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 E Catalog Na FST. 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

ecatalog-na.fst.com accessibility score

95

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

ecatalog-na.fst.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ecatalog-na.fst.com SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecatalog-na.fst.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Ecatalog-na.fst.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 E Catalog Na FST. 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: