Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

epicard.com

Epicard SA

Page Load Speed

1.3 sec in total

First Response

573 ms

Resources Loaded

576 ms

Page Rendered

115 ms

epicard.com screenshot

About Website

Visit epicard.com now to see the best up-to-date Epicard content for United States and also check out these interesting facts you probably never knew about epicard.com

Présentation de EPICARD SA

Visit epicard.com

Key Findings

We analyzed Epicard.com page load time and found that the first response time was 573 ms and then it took 691 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

epicard.com performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

epicard.com

573 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 54 B (27%)

Content Size

200 B

After Optimization

146 B

In fact, the total size of Epicard.com main page is 200 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 200 B which makes up the majority of the site volume.

HTML Optimization

-27%

Potential reduce by 54 B

  • Original 200 B
  • After minification 177 B
  • After compression 146 B

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 23 B, which is 12% 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 54 B or 27% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

epicard.com accessibility score

100

Accessibility Issues

Best Practices

epicard.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

epicard.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epicard.com can be misinterpreted by Google and other search engines. Our service has detected that French 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 Epicard.com main page’s claimed encoding is . 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.

Social Sharing Optimization

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