Tools & Wizards About Us

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

fae.es

Soluciones OEM Y AFTERMARKET automoción - FAE

Page Load Speed

4.7 sec in total

First Response

377 ms

Resources Loaded

3.3 sec

Page Rendered

1 sec

About Website

Welcome to fae.es homepage info - get ready to check FAE best content for Algeria right away, or after learning these important things about fae.es

FAE - Francisco Albero S.A.U. es un fabricante europeo que diseña y fabrica productos eléctricos y electrónicos para automóvil desde 1952.

Visit fae.es

Key Findings

We analyzed Fae.es page load time and found that the first response time was 377 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

fae.es performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value700 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

fae.es

377 ms

www.fae.es

1516 ms

dashicons.min.css

202 ms

extra.min.css

238 ms

style.min.css

317 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 70% of them (69 requests) were addressed to the original Fae.es, 28% (27 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fae.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.0 kB (22%)

Content Size

929.4 kB

After Optimization

721.4 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Fae.es main page is 929.4 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. 70% of websites need less resources to load. Images take 563.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 205.1 kB

  • Original 235.2 kB
  • After minification 227.6 kB
  • After compression 30.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 205.1 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 563.0 kB
  • After minification 561.7 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. FAE images are well optimized though.

CSS Optimization

-1%

Potential reduce by 1.5 kB

  • Original 131.1 kB
  • After minification 130.9 kB
  • After compression 129.6 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. Fae.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (77%)

Requests Now

64

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

fae.es accessibility score

90

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-*] attributes do not match their roles

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.

Best Practices

fae.es 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

SEO Factors

fae.es SEO score

90

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

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fae.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Fae.es 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 data is detected on the main page of FAE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: