Access fersay.com. Tienda de repuestos para electrodomésticos

42

Performance

Renders faster than
61% of other websites
64

Accessibility

Visual factors better than
that of 30% of websites
67

Best Practices

More advanced features
available than in
24% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

1.1 sec

Resources Loaded

10.1 sec

Page Rendered

251 ms

About Website

Welcome to fersay.com homepage info - get ready to check Fersay best content for Spain right away, or after learning these important things about fersay.com

Tienda online especializada en accesorios y repuestos para electrodomésticos y electrónica del hogar. Piezas y recambios de todas las marcas en Fersay

Visit fersay.com

Key Findings

We analyzed Fersay.com page load time and found that the first response time was 1.1 sec and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

28/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

fersay.com

1092 ms

www.fersay.com

2099 ms

ico_bandera_es.gif

232 ms

ico_bandera_en.gif

232 ms

ico_bandera_fr.gif

233 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that all of those requests were addressed to Fersay.com and no external sources were called. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Fersay.com.

Content Size

5.4 MB

After Optimization

4.0 MB

In fact, the total size of Fersay.com main page is 5.4 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 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 214.1 kB

Original 247.3 kB
After minification 184.8 kB
After compression 33.2 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 62.5 kB, which is 25% 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 214.1 kB or 87% of the original size.

Image Optimization

-10%

Potential reduce by 404.9 kB

Original 4.1 MB
After minification 3.7 MB

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. Fersay images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 498.2 kB

Original 679.5 kB
After minification 670.9 kB
After compression 181.3 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 498.2 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 331.3 kB

Original 389.2 kB
After minification 366.3 kB
After compression 57.9 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. Fersay.com needs all CSS files to be minified and compressed as it can save up to 331.3 kB or 85% of the original size.

Requests Now

109

After Optimization

109

The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fersay. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ES
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fersay.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fersay.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

fersay.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Tienda de repuestos para electrodomésticos - Fersay

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)